jayjay Posted February 16, 2021 Report Share Posted February 16, 2021 I have to come back to a previous issue (Resilio Sync not listening to port 3838 on Ubuntu 20.04) which hasn't been solved. In many case LAN search is not working for the Resilio Sync client on my Ubuntu 20.04 server as Resilio Sync is not listening to multicast on port 3838, which is required to LAN search. This happens often after a reboot and if a do a service restart of the resilio sync process it is always the case. If everything is fine netstat -npl |grep rslsync showstcp 0 0 192.168.1.2:40935 0.0.0.0:* LISTEN 2448/rslsynctcp6 0 0 :::40935 :::* LISTEN 2448/rslsyncudp 0 0 0.0.0.0:3838 0.0.0.0:* 2448/rslsyncudp 0 0 192.168.1.2:53082 0.0.0.0:* 2448/rslsyncudp 0 0 192.168.1.2:40935 0.0.0.0:* 2448/rslsyncudp6 0 0 :::3838 :::* 2448/rslsyncudp6 0 0 :::40935 :::* 2448/rslsync In case it is not working it showstcp 0 0 0.0.0.0:40935 0.0.0.0:* LISTEN 1870/rslsynctcp6 0 0 :::40935 :::* LISTEN 1870/rslsyncudp 0 0 0.0.0.0:40935 0.0.0.0:* 1870/rslsyncudp6 0 0 :::40935 :::* 1870/rslsync Previously triggering a network restart using "netplan apply" solved the problem as resilio started to listen to port 3838 after the restart. However this is no longer the case. A network restart doesn't change anything. Previously resilio detected the network restart and reloaded its network configuration (logged in sync.log), but seems to be no longer the case. Any idea why Resilio is not binding to port 3838? For the detail configuration files see my previous issue report mentioned above. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.