andrew wong wrote: > When I change to user 'mud1', then: > > mud1#ping 143.89.14.15 > PING 143.89.14.15 (143.89.14.15) 56(84) bytes of data. > 64 bytes from 143.89.14.15: icmp_seq=1 ttl=248 time=23.4 ms > 64 bytes from 143.89.14.15: icmp_seq=2 ttl=248 time=25.5 ms > > However: > mud1#ping www.ust.hk > (no response) > mud1#telnet www.ust.hk 80 > (no response) > mud1#ssh -l solarkid uststu1.ust.hk > (no response) > > Thanks aaaaa lot!!~~~ > > Andrew I really shouldn't reply because I don't have an answer for you. I had a similar problem when I set up my multipath routing but I don't recall how I fixed it :< You should know: 1) You MUST install Julian's combined patch for your kernel version: http://www.ssi.bg/~ja/ 2) You should read nano.txt there also. 3) The LARTC HOWTO is wrong. Worse, it is unmaintained so it is not likely to get fixed any time soon. 4) Have a look at http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking 5) I strongly advise that you read Martin Brown's documentation: http://linux-ip.net/ 6) Use the latest iproute2 at http://developer.osdl.org/dev/iproute2/download/iproute2-ss050607.tar.gz 7) Don't use 'ifconfig' or 'route'. Use iproute2's 'ip' instead. 8) Troubleshoot with 'arp -n' and 'ping -I $IFACE' (and maybe tcpdump) starting on the Debian box. My hunch is that your reply packets are getting lost, otherwise you would have said there is an error message when you ping from mud1...? HTH, Gypsy _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
