TashRouter: An AppleTalk Router

shirsch

Well-known member
I'm running Tashrouter on an RPi under Debian Bullseye. What is the best approach for making it start automatically at boot?
 

shirsch

Well-known member
Ack - nevermind. I found a suggested systemd unit file in an earlier post. That seems to have done the trick..

Heh - we crossed in the wires. That is working - thanks.
 

NJRoadfan

Well-known member
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.
 

slipperygrey

Well-known member
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.
Have you escalated this to the kernel devs?
 

NJRoadfan

Well-known member
I did post a note on the patch author's gist regarding the issue. I am trying to determine the source of the problem first before escalating.
 

NJRoadfan

Well-known member
This maybe a bug in Netatalk. I "unpatched" the kernel module and looked at the logs. Netatalk sends out duplicate NBP Reply packets even with the unpatched module, the difference is that the origin address in the DDP header is all the same. Its sending out one for each interface on the machine, including the loopback which has an address of `0.0`.
 
Top