Morning Krishna,
Question:
- Can some router might be misbehaving in the path? If yes how
to discover it, as traceroute -n also does not print IP after certain limit. If ttl of 255 is causing a problem then why does nsdl.co.in works and why not other sites?
[snip]
Some of the routers configured are ****** up while the rest are plain ol sweeties.
- Same setup works in Bombay with Tatatele cable connection.
[snip]
great.
- What next thing to check or do?
[snip]
Use a laptop/desktop with a dialup connection and let us know if there is a replication of the problem.
Please any pointers, what am I missing?
[snip]
Internal/external DNS???. Are they working perfecto..???.
Trevor
-Krishna
[1] routing -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 eth0 202.162.224.0 172.16.200.1 255.255.255.0 UG 0 eth1 210.210.19.0 172.16.200.1 255.255.255.0 UG 0 eth1 172.16.0.0 0.0.0.0 255.255.0.0 U eth1 0.0.0.0 172.16.200.1 0.0.0.0 UG eth1
(192.168.1* is local network)
[2] ipchains -L Chain input (policy ACCEPT): Chain forward (policy ACCEPT): target prot opt source destination ports MASQ tcp ------ 192.168.1.0/24 0.0.0.0/0 * -> * MASQ udp ------ 192.168.1.0/24 0.0.0.0/0 * -> * MASQ icmp ------ 192.168.1.0/24 0.0.0.0/0 * -> * Chain output (policy ACCEPT):