Re: bridging lan > vpn
From: Kristofer Andersson (kaatpocodotse.ihatespamandIwillstalkspammers_at_aol.com)
Date: Tue, 27 Apr 2004 17:32:48 -0400
> When you added what route in RRAS?
Under routing interfaces:
a demand dial vpn connection
Under Static Route:
Interface: name of the vpn connection
Gateway: grayed out when I selected the vpn interface
Use this route to initiate demand-dial connections: checked
> > > 5. Network settings of the clients sending the packet or receiving the
> > > packet is not correct.
> Forget pinging or tracing across it. Can a client ping the closest
> interface of the router?...in other words, just *to* it and not across it?
It can ping the win2k server that acts as a router on my side. It can not
ping the win2k server that is the vpn server on the other side.
> To tell you the truth, there is just too much "fog" surrounding the design
> and configuration of this network for me to do anything with it.
Let me try to clarify what we have:
1) a DSL connection to the internet. This one has a SOHO firewall device.
This is the default gateway for all PCs. IP 192.168.112.1
Has a route for 10.10.1.0 to gateway 192.168.112.253
2) a T1 connection to another company with a Cisco router. IP
routes traffic for 10.10.0.0 to external network but has an exception route
for 10.10.5.0 to go through 192.168.112.6
3) a win2k server 192.168.112.6 configured as a router and to route all
traffic for 10.10.5.x through a VPN connection to a Win2k VPN server on the
other side of the planet
4) a bunch of PCs with IPs in the 192.168.112.50-192.168.112.252 range, mask
255.255.255.0, default gateway 192.168.112.1