Keep alive disabled by default ?

mprotic

Guys, is keep alive disabled by default ? I've noticed unreliable linphone notifications behind certain wifi routers.

cat /proc/sys/net/ipv4/tcp_keepalive_time

returns: 7200

My guess is that some of these routers break open connections after certain time. Am I missing something here ? How does disabled keepalive work with notifications, wasn't the phone supposed to hold open connection for the notifications (or linphone, or whatever).

How about setting it to something more reasonable like 60 sec ?

flohack

Well its a implementation detail of linphone´s core API I suppose. Keepalive is a TCP socket option the App has to set, and not smth that the OS takes care of for every connection. Also most of the Apps do not run in the background, so even with keepalive they might get disconnected since they cannot respond to the incoming packets.

Please talk with the Linphone guys about it, but as I understood there should be a working keepalive been set. Its just very likely that your NAT router ignores it maybe.

BR

CiberSheep

@mprotic said in Keep alive disabled by default ?:

Guys, is keep alive disabled by default ? I've noticed unreliable linphone notifications behind certain wifi routers.

Hello. Could you explain a little bit more what is the problems you have? What notifications are you having problems with (as Linphone app doesn't have notifications in the system)?
Also, a log could might be handy.
Feel free to open an issue to the project: https://gitlab.com/ubports-linphone/linphone-simple/issues

Thank you

mprotic

Nevermind about the linphone, it could be (and probably is) related to something else, it just came to my mind that maybe keepalive shoud be enabled generally. But now I see that application can override system keepalive settings on socket level.

dobey

The value you see from /proc/ is the default value, and it is 7200 seconds. Setting it to a much lower value would not solve whatever issue it is you're having. More than likely, the router (or DHCP server rather) is renewing the IP lease, which is probably resulting in a new IP address or other disruption to any active connections. Or there is some other problem.