I have a novell 6.0sp3 server with bordermanager 3.8 installed.
Everything
working ok except access through vpn tunnel. Seems to be some routing
issue
with the vpn tunnel. I was able to duplicate the problem in a simple
test
lab environment, so it has to be something that I am overlooking.

Here is the scenario in my test lab. Public ip 172.16.50.15/16
Private ip
192.168.1.10/24
Tunnel ip
10.0.0.10/8
VPN ip pool
192.168.0.100/24 - 200
Test vpn pc on
same net
as public ip 172.16.50.25.16
Test pc on same
net as
private ip 192.168.1.65/24
nat and filters disabled can ping from pc to server's private ip
address
and internal pc
I then reload ipflt and establish my vpn connection after successful
authentication, I am assigned ip address 192.168.0.100 and see that my

traffic policies are set to allow any traffic to any source. VPN
monitor
shows client connected but no ip packets sent or received. Cannot ping

anything. If I unload ipflt and then retry, I can ping and login but
it must
be going through the public interface because I still see no traffic
being
sent or received through the vpn connection. Any ideas what must be
done
ether on the client side or server side to get the vpn traffic to
route
properly. Also does same thing with nat enabled and a static nat on
the
public interface with the private ip address natting to it self.

Mike