On Fri, 2003-09-05 at 23:32, Robins Tharakan wrote: > sorry if i am very stupid but, > have you routed the packets correctly? > > it might just be that your default packet route after restarting > iptables is eth1 rather than the original eth0. > > the easiest way to find out is whether traceroute 12.12.12.12, or any > other ip address not on your eth0.
Sorry for the delay in response. Route command gets stuck as it is unable to resolve the host names As you can see the default route is still added to eth0.Ping on 192.168.1.10 at this state is ok. <output of "route -n"> [EMAIL PROTECTED] root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.10 0.0.0.0 UG 0 0 0 eth0 </output of "route -n"> Any other ideas? -- Arindam Dey The mind is not a vessel to be filled but a fire to be kindled. GPG FPR: B8E3 219E F129 F970 F4A7 BC50 9636 504A BEDF 5739 _______________________________________________ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd