On Sat, 16 Oct 2004, Benjamin Goedeke wrote: > There's an wrong routing entry: > > 134.102.0.0/16 0.0.0.0 UG 0 0 0 eth1
It is not wrong, it is just dangerous. You *have* a 134.102.0.0/16 network there, don't you? Or is the netmask wrong? You can fix the issue right by increasing your arp cache size, or you can pass it to someone else (maybe hurting YOUR performance while at it, if they cannot deal with it either) by setting that interface up with the wrong netmask on purpose. Suppose the gw is of ip 134.102.0.1. Set the interface up as 134.102.0.1 netmask 255.255.255.255 and it will work on most "we are nice" gateway forwarding setups, I think. But now the 134.102.0.1 machine will have to deal with all the packets and ARP resolution that YOU should be doing, and if it doesn't deal with it well... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
