> >> I don't see how arping or not can be a driver problem, the driver > >> just sends packets queued by the stack, there exists NO > mechanism to > >> communicate that kind of thing down into the driver, -arp is > >> something that must be negotiated in the stack somewhere, > as for it > >> working with broadcom... > >> <shrugs> > >> > >> > > except for the system management stuff.
On the bce(9) driver does it display the "MFW" flag during driver load? That would indicate whether NC-SI style management firmware is running which would be unexpected on a NIC card. If the Intel LOM is connected to a baseboard management controller or service processor then the BMC or SP are likely generating the ARP. What's the source MAC address of the ARP? Does it match the LOM's MAC address or the MAC address of any BMC or SP? The latter would generally be printed on a tag on the system or perhaps in a BMC setup screen visible during POST. Dave _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
