"No route to host" seems kinda weird, but since you can ping I don't think theres anything wrong with your hardware. Anyway, I like it when people RTFM, maybe I can be of some help.
loki:/etc# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 204.145.251.52 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 204.145.251.52 0.0.0.0 UG 0 0 0 ppp0 (I also don't like the double lo appearance in the other machines routing) I'm missing an important piece of info: was your ppp0 interface up when trying to ftp between your two boxes and does it work ok, do you have Internet connectivity? It looks like the ppp is wrong. With a 0.0.0.0 netmask you don't set any network bits for the interface, this might explain why your ping -b did something (also note the longer ping time when pinging themselves) Do you want to ping broadcast? Then -b ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PING 192.168.1.0 (192.168.1.0) from 192.168.1.2 : 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=0.5 ms 64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=0.4 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=0.4 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=0.4 ms Note that .1 doesnt respond (it should also, al least mine does with a "DUP!" note). Does your /etc/host.conf have order bind,hosts (should be hosts,bind unless you're really doing exotic things on purpose) in it? Are you running bind yourself? (don't) Anyway, you should be using params like these: .1 has an eth .1, no default gateway, the ppp interface should have its gateway set to its Internet IP address (dynamically if needed) or (better) to one of your ISP's router IPs. It should have the .2 box in its /etc/hosts file and it should have your ISPs DNS numbers in its /etc/resolv.conf. Ask them for the netmask you should use and then use it (or x.x.255.255 or so if you have no further info) on the ppp interface. Use the default entries for the lo device on both boxes, also leave the IP spoofing part in place in /etc/init.d/networking. Make sure /etc/host.allow and .deny are set up the way you want it, enable .2 to do stuff and keep the rest out. Now .2 might want to have .1 as its gateway, that way (if you enable ip forwarding and masquerading on .1) you can use .1's Internet connection (I presume this is the final goal?). Don't use .1's Internet IP number anywhere in your setup, instead for .2, the Internet connectivity should be provided by .1 You can (and should unless your .1 runs bind) enter your ISP's nameservers in /etc/resolv.conf Don't change the /etc/init.d/networking script too easily, instead use /etc/network/interfaces and the like, and restart the daemon everytime by # /etc/init.d/networking stop # /etc/init.d/networking start (I rather not use reload). If you'll do ipchains rules for your local net, /etc/init.d/networking might be a good place for that. I think it's easier to check the setups once again than to find the exact problem from diagnostic output. I don't believe you have a hardware problem and certainly not an IRQ problem!! The networking HOWTO will likely be needed. Good luck, -- Danny Pansters [EMAIL PROTECTED] www.ricin.com
