You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This affects Netatalk 3.x and main branches. The server should be sending tickles over DSI every 30 seconds to a client so that the client knows the server is still up. Netatalk 2.x is not affected and sends out tickles every 30 seconds over DSI.
To reproduce:
-Install Netatalk 3.x or main branch.
-Monitor your network connection. You should see tickles from the client every minute or so, but none from the server.
-Connect to Netatalk using MacOS 8.x-9.x via TCP/IP. After 4 minutes, the client will time out and disconnect.
MacOS X clients don't seem to be adversely affected by this. They support client sleep/reconnect and can recover somewhat gracefully from the lack of server tickles. There is a function called alarm_handler() in afp_dsi.c that handles the periodic tickle transmissions. Somewhere along the line, it broke.
The text was updated successfully, but these errors were encountered:
This affects Netatalk 3.x and main branches. The server should be sending tickles over DSI every 30 seconds to a client so that the client knows the server is still up. Netatalk 2.x is not affected and sends out tickles every 30 seconds over DSI.
To reproduce:
-Install Netatalk 3.x or main branch.
-Monitor your network connection. You should see tickles from the client every minute or so, but none from the server.
-Connect to Netatalk using MacOS 8.x-9.x via TCP/IP. After 4 minutes, the client will time out and disconnect.
MacOS X clients don't seem to be adversely affected by this. They support client sleep/reconnect and can recover somewhat gracefully from the lack of server tickles. There is a function called
alarm_handler()
inafp_dsi.c
that handles the periodic tickle transmissions. Somewhere along the line, it broke.The text was updated successfully, but these errors were encountered: