Note for those running Linux kernel 6.9 or newer. It appears that a regression has been introduced that NBPReply packets are being duplicated and sent out with a source address of
0.0
whenever netatalk replies to NBP Requests. These packets will crash TashRouter and leave it running in an unrecoverable state since it can't currently handle packets when an origin of
0.0
. I have submitted a pull request that fixes this here:
https://github.com/lampmerchant/tashrouter/pull/9
The patch simply drops these packets since an address of
0.0
is not valid on an extended network.