On Fri, Feb 27, 2004 at 12:59:12PM +0100, Joost De Cock wrote: > On Friday 27 February 2004 12:58, Brian Brazil shoved this is my mailbox: ^^ Hmmmm... > > On Thu, Feb 26, 2004 at 10:25:52PM +0100, Joey Macao wrote: > ... > > > eth0 Link encap:Ethernet HWaddr 00:05:02:C9:BA:CC > > > inet addr:192.168.1.3 Bcast:192.168.0.255 Mask:255.255.255.0 > > > eth1 Link encap:Ethernet HWaddr 00:50:BA:B3:1D:31 > > > inet addr:192.168.1.8 Bcast:192.168.0.255 Mask:255.255.255.0 > ... > > > however pinging to 192.168.1.8 gives me: "Destination Host Unreachable" > > > > This is a routing issue. Could you do a 'route -n' and post the results? > .. > > Also just noticed your broadcast address is wrong. Should be > > 192.168.1.255 for that subnet/netmask. > > Brian is right, your broadcast address is incorrect, so probably the ARP > request never reaches the other network card.
My understanding is that ARP request goes out on FF:FF:FF:FF:FF:FF thereby staying on the link layer (ignoring the fact that its getting IP information). See output of 'arp' Also the packet should never leave the box - it should be handled entirely via the INPUT and OUTPUT iptables chains(if you were using iptables). Now if you were to send out an 192.168.{1,0}.255 broadcast on that network from another system there's a good chance you'll cause a broadcast storm - especially if any of the machines are set up to forward packets. I've never seen one of these beasts though. My reference is O'Reillys NIS & NFS - there's a lot of detail in there but I read it a good while back though. Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]