Package: bootp Version: 2.4.3-13 I can affirm the diagnostics of Christoph Kiechle!
We switched from SuSE to Debian yesterday and now have the same repoted problems with the bootpd.
With one of three printers everthing works fine: the boot reply is send to the dedicated IP and the ethernet MAC address from which the boot request came.
In contrast the boot replies to the boot requests of the other two printers are send to the bootpd servers IP address (same as source IP) and thus has all ehternet MAC addresses set to 00:00:00:00:00:00 (as captured on lo with ethereal).
Shouldn't be the destination IP address irrelevant (which causes to be send to lo) and a raw ethernet package to the source address of the request be built?
Kind regards Jürgen Nagler-Ihlein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
