derek martin writes: re pblm 1: > Oh yeah! Seen that problem! I think we saw it on several occasions with > two distinct causes... The one that I remember was that the machine did > not have the routing set up properly. The other was a mystery and I'm not > sure how we solved it... I think it was one of those magical problems that > just go away on their own. :) ugh! > What is the IP address of netgear? 192.168.0.1 (the local box, defined as netgear.moylan.com in hosts) > Does this machine have 2 nics? yes, machine 1 has 2 nics, only one of which seems to be recognized in dmesg, and of course that's the one i'm using. the other is idling (perhaps i should take it out?). > re pblm 2: > This is probably just that telnet is commented out of inetd.conf on > machine 1. oddly enough, there was no inetd.conf in machine 1's /etc (and why not you might ask?). perhaps that indicates something i'm missing. i copied over the inetd.conf from machine 2, which did have a valid telnet entry but that changed nothing. ######################################################################### jerry feldman writes: > I run a very similar setup using a Linksys BEFSR41. > First, the RT314 is a 4 port switch, so communications between the > systems cabled to the switch have nothing to do externally, so it > comes down to configuration of the systems themselves. yup. > On your telnet problem, check /etc/inetd.conf to make sure that telnet > is allowed. done. > I am wondering if your double entry in your routing table may be > indicative of a problem. Not sure. Mine looks like this: > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt Iface > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 took an extra (obviously unneeded) route command from my eth0 enabling script and now have this. it's the same on both machines. Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default netgear.moylan. 0.0.0.0 UG 0 0 0 eth0 situation remains the same. ymhaos, dan ######################################################################### "dan moylan" wrote: > i have two machines running through a netgear rt-314 cable router, > to a us robotics cmx cable modem, to rcn cable. both machines run > rh6.2, in very similar, though obviously not identical setups. > > problem 1: pinging between the local stuff is ok at 1ms or so. > pinging remote stuff looks ok at 10-15ms or so on machine 2 > but from machine 1, the pinging times go up in arithmetic > progression. e.g.: > > PING 207.172.3.8 (207.172.3.8) from 192.168.0.3 : 56(84) bytes of data. > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=0 ttl=252 time=11.6 ms > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=1 ttl=252 time=5022.1 ms > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=2 ttl=252 time=10023.1 ms > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=3 ttl=252 time=15022.8 ms > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=4 ttl=252 time=20019.5 ms > 64 bytes from ns1.dns.rcn.net (207.172.3.8): icmp_seq=5 ttl=252 time=25023.2 ms > > --- 207.172.3.8 ping statistics --- > 37 packets transmitted, 7 packets received, 81% packet loss > round-trip min/avg/max = 11.6/15020.4/30020.9 ms > > problem 2: machine 1 can telnet to machine 2 ok, but telnetting to machine > 1 from machine 2 produces error: > > Trying 192.168.0.3 > telnet: Unable to connect to remote host: Connection refused > > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt Ifac > e > 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 > 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 * 255.0.0.0 U 0 0 0 lo > default netgear.moylan. 0.0.0.0 UG 0 0 0 eth0 > > hosts, .xhosts, .rhosts all identical, and include both machines > > any ideas as to what is different (i.e. screwed up)? > > tia, > > dan