[clug] routing advice needed
michael at catman.homelinux.org
Wed Dec 3 09:25:10 GMT 2003
I don't understand why you would want to route a packet destined for
your VPN back out to the internet. Most times you would not be using
internet routable IP's in your VPN subnet anyway (unless you had one
real IP that was owned by the VPN server). Wouldn't you want the packet
addressed to the VPN (22.214.171.124/24) to be routed somewhere in the VPN
Are you trying to establish some sort of VPN (using GRE IP tunneling?)
that is using a real world IP?
I am may be a little confused as to the outcomes you are trying achieve.
Could you elaborate a bit?
On Wed, 2003-12-03 at 20:02, Kim Holburn wrote:
> For you router guys out there I need some advice.
> I have a machine with 3 interfaces.
> eth0 -> 126.96.36.199/26 -> 188.8.131.52 -> internet
> eth1 -> 184.108.40.206/24 -> 220.127.116.11/24
> -> 18.104.22.168 -> VPN to 22.214.171.124/24
> eth2 -> 126.96.36.199/24 -> internal net
> default route is -> eth0 188.8.131.52
> if I have a packet from eth2 to the special subnet 184.108.40.206/24 I want to it to go via a gateway on eth1 220.127.116.11 (say a VPN) but
> if I have a packet from eth1 to 18.104.22.168/24 I want it to go via the default route (eth0).
> I use the command:
> ip route 22.214.171.124/24 via 126.96.36.199 from 188.8.131.52/24
> but what I get is the same as if I ran:
> ip route 184.108.40.206/24 via 220.127.116.11
> Anyone have an idea how to do that?
Red Hat Certified Engineer
Email: michael at catman.homelinux.org
More information about the linux