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
when i reconnect my wifi, after about 260 seconds, another irc client see goirc deamon timeout.
but the goirc daemon emit disconnect event after about 15 minutes.
want to known is this normal?
The text was updated successfully, but these errors were encountered:
It's hard to be sure given the information you have provided.
What OS are you using?
What state are all clients in before you disconnect the wifi?
How is the wifi being disconnected?
How long is the wifi disconnected for?
When you reconnect the wifi do you reconnect the other client to the server manually?
When you reconnect the wifi does it get a different IP address via DHCP?
Where is the server in relation to the clients? On a local network? Freenode?
What timeouts and ping frequency are configured on the IRC server?
If I had to take a guess at what is happening here, I'd say:
Disconnecting/reconnecting your wifi probably involves a reset of the wireless network interface and thus all state associated with the currently active TCP connections being dropped. The server will be pinging your goirc client regularly; when the connection drops the client will no longer respond to pings and after 260 seconds (I'm guessing this is the server's timeout setting) in this state the server will forcibly drop the client connection.
The goirc client will by default ping the server every 3 minutes, so what I think ought to happen is that those writes also fail because the TCP connection no longer exists. But that doesn't seem to be happening. I'm not sure why, you are going to need to provide more information for me to help further.
when i reconnect my wifi, after about 260 seconds, another irc client see goirc deamon timeout.
but the goirc daemon emit disconnect event after about 15 minutes.
want to known is this normal?
The text was updated successfully, but these errors were encountered: