need help with route command

  • Thread starter Thread starter car nut
  • Start date Start date
C

car nut

Hi, I've recently set up a VPN connection (from laptop with remote ISP to my
linksys wrv54G) and want to route PARTIAL web and POP/SMTP traffic through
the VPN; with all other Internet traffic going through their normal routes.

I've tested using different route commands but none will hold (always get
error). Can someone help me with the command I need to route partial
Internet traffic through my VPN (which then go onto the Internet, out the
VPN network)?

I ask because many times I'm using a network or wireless hotspot I don't
trust and would rather some of my non-SSL surfing go through a VPN tunnel to
my home, then to the Internet from the home connection.
 
IP routing is concerned with IP addresses. A route command specifies
what traffic is routed depending on its address. It cannot decide where to
send traffic based on the type of data which is being sent.

If you are using the Microsoft VPN client, the default behavior is to
send all traffic over the VPN. If you clear the "use default gateway.." box
in the advanced TCP/IP properties, this changes. The existing default
gateway stays active (ie to the ISP) and only traffic for the RRAS server's
subnet is sent across the link. See KB 254231 .
 
Hi Bill, it's not that I'm trying to route certain protocols; I want to
route certain IP addresses through the VPN connection.

So if my smtp/pop server is at 24.23.1.2 then I want any connection made out
to that IP via the VPN; be it http, pop, etc.. Anything else should go
through the directly-connected ISP.
 
That's a bit tricky, because that is a registered public IP address.
Where is that machine in relation to your VPN server?

If you clear the "use default gateway.." box, it will automatically
route traffic for the VPN subnet to the server (through the tunnel) and
everything else to the ISP. If the 24.13 address is on a subnet behind the
VPN server you will have to add a static route to the client to route this
through the tunnel as well. You need to use the "received" IP as the next
hop address (as explained in the KB article).
 
Back
Top