On 2007-Apr-17 13:36:43 +1000, Alan Garfield <[EMAIL PROTECTED]> wrote: >I've got a little driver that communicates via a small buffer on the >motherboard of a Sun Fire V20z to a built-in "service processor" which >is running Linux. The driver on both sides makes the buffer look like a >Ethernet interface.
I'd be interested in using this. >arplookup 169.254.101.2 failed: could not allocate llinfo >arpresolve: can't allocate route for 169.254.101.2 > >The Linux driver I'm porting simply grabbed any outgoing arp requests, >made up an appropriate response with the pre-defined fake MAC's, put it >into the input queue and ate the request packet. A quick-and-dirty work-around would seem to be arp -s 169.254.101.2 Fa:ke:ma:cA:dd:re:ss Otherwise, I think you would need to fiddle with the transmit packet code in your driver. -- Peter Jeremy
pgp1DSC38AW7a.pgp
Description: PGP signature
