You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Supplying routing information using DHCP:

#4 Re: Supplying routing information using DHCP Posted by TokenGoth (193.195.xx.xx) on Wed 6 Dec 2006 at 12:03 Not in my experience... and thats the way my network here is setup. Our Windows machines learn the routes to networks when they try to reach the hosts as the routers send back redirects... and I'm pretty sure our Linux boxes get the same info, infact a quick test: nephthys:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.12 0.0.0.0 UG 0 0 0 eth0 nephthys:~# traceroute bes traceroute to bes (192.168.20.204), 30 hops max, 38 byte packets 1 rt (192.168.1.12) 0.909 ms 0.888 ms 0.884 ms 2 rt-vpn-policy (192.168.1.224) 2.113 ms 1.584 ms 1.618 ms 3 bes (192.168.20.204) 32.685 ms 36.053 ms 32.565 ms nephthys:~# traceroute bes traceroute to bes (192.168.20.204), 30 hops max, 38 byte packets 1 rt-vpn-policy (192.168.1.224) 0.846 ms 0.773 ms 0.757 ms 2 bes (192.168.20.204) 32.460 ms 33.175 ms 35.103 ms Yup, its learned to bypass the default gw.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account