search

linuxmint / warpinator

Share files across the LAN
GNU General Public License v3.0
1.17k stars 80 forks source link

Firewall issues with despite open ports 42000 and 42001 #129

Closed levi-jcbs closed 2 years ago

levi-jcbs commented 2 years ago

Dear developers,

I want to use Warpinator on two openSUSE Tumbleweed Devices, but they don't connect to each other, so they're not listed. Firewall Ports 42000 and 42001 are open. Warpinator is installed via Flatpak.

These are the two scenarios I noticed till now:

Scenario 1, Device A (hanna-laptop):

2022-05-16 10:02:34,709::warpinator: Initializing Warpinator
2022-05-16 10:02:34,710::warpinator::DEBUG: UI: Creating window and status icon -- warpinator.py (line 1030)
2022-05-16 10:02:34,962::warpinator::DEBUG: Starting network monitor -- networkmonitor.py (line 52)
2022-05-16 10:02:34,963::warpinator::DEBUG: Network state changed: online = True -- networkmonitor.py (line 144)
2022-05-16 10:02:34,963::warpinator::DEBUG: New server requested for 'wlp2s0' (10.254.0.35) -- warpinator.py (line 1082)
2022-05-16 10:02:34,965::warpinator::DEBUG: Auth: Creating server credentials -- auth.py (line 214)
2022-05-16 10:02:35,083::warpinator::DEBUG: Server: starting server on 10.254.0.35 (wlp2s0) -- server.py (line 278)
2022-05-16 10:02:35,083::warpinator: Using api version 2
2022-05-16 10:02:35,083::warpinator: Our uuid: HANNA-LAPTOP-42B6B6E79D6A3A930F71
2022-05-16 10:02:35,083::warpinator::DEBUG: Starting v1 registration server (10.254.0.35) with port 42000 -- remote_registration.py (line 59)
2022-05-16 10:02:35,084::warpinator::DEBUG: Starting v2 registration server (10.254.0.35) with auth port 42001 -- remote_registration.py (line 61)
2022-05-16 10:02:35,093::warpinator: Using system zeroconf v0.29.0
2022-05-16 10:02:42,962::warpinator: Server: ACTIVE
2022-05-16 10:02:42,965::warpinator::DEBUG: UI: start discovery timer (no remotes) -- warpinator.py (line 784)
2022-05-16 10:02:46,167::warpinator::DEBUG: UI: Discovery timed out (no remotes) -- warpinator.py (line 800)
2022-05-16 10:03:32,948::warpinator::DEBUG: >>> Discovery: received flush service info (ignoring): thinkpad-x1 (10.254.0.25:42000) -- server.py (line 177)
2022-05-16 10:03:36,324::warpinator::DEBUG: >>> Discovery: unknown service ident (THINKPAD-X1-D6B22C334D0F3F1EFBBA) reported as gone by zc. -- server.py (line 148)
2022-05-16 10:04:32,217::warpinator::DEBUG: >>> Discovery: new remote: thinkpad-x1 (10.254.0.25:42000) -- server.py (line 246)
2022-05-16 10:04:32,217::warpinator: Registering with thinkpad-x1 (10.254.0.25:42001) - api version 2
2022-05-16 10:04:32,217::warpinator::DEBUG: remote-registration-thread-thinkpad-x1-10.254.0.25:42001-THINKPAD-X1-D6B22C334D0F3F1EFBBA -- remote_registration.py (line 240)
2022-05-16 10:04:32,217::warpinator::DEBUG: Remote: Attempting to register thinkpad-x1 (10.254.0.25) -- remote_registration.py (line 258)
2022-05-16 10:04:32,539::warpinator::DEBUG: Remote: Attempting to connect to thinkpad-x1 (10.254.0.25) - api version 2 -- remote.py (line 197)
2022-05-16 10:04:32,724::warpinator::DEBUG: Remote: waiting for duplex from 'thinkpad-x1' -- remote.py (line 349)
2022-05-16 10:04:32,814::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.AWAITING_DUPLEX **** -- remote.py (line 312)
exception
2022-05-16 10:04:37,790::warpinator::CRITICAL: Problem while awaiting duplex response - api version 2: StatusCode.DEADLINE_EXCEEDED - Server timed out while waiting for his corresponding remote to connect back to you. -- remote.py (line 257)
2022-05-16 10:04:37,790::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.UNREACHABLE **** -- remote.py (line 312)

Scenario 1, Device B (thinkpad-x1):

2022-05-16 10:02:37,576::warpinator: Initializing Warpinator
2022-05-16 10:02:37,577::warpinator::DEBUG: UI: Creating window and status icon -- warpinator.py (line 1030)
2022-05-16 10:02:37,840::warpinator::DEBUG: Starting network monitor -- networkmonitor.py (line 52)
2022-05-16 10:02:37,841::warpinator::DEBUG: Network state changed: online = True -- networkmonitor.py (line 144)
2022-05-16 10:02:37,842::warpinator::DEBUG: New server requested for 'wlp0s20f3' (10.254.0.25) -- warpinator.py (line 1082)
2022-05-16 10:02:37,844::warpinator::DEBUG: Auth: Creating server credentials -- auth.py (line 214)
2022-05-16 10:02:37,976::warpinator::DEBUG: Server: starting server on 10.254.0.25 (wlp0s20f3) -- server.py (line 278)
2022-05-16 10:02:37,988::warpinator: Using api version 2
2022-05-16 10:02:37,988::warpinator: Our uuid: THINKPAD-X1-D6B22C334D0F3F1EFBBA
2022-05-16 10:02:37,988::warpinator::DEBUG: Starting v1 registration server (10.254.0.25) with port 42000 -- remote_registration.py (line 59)
2022-05-16 10:02:37,989::warpinator::DEBUG: Starting v2 registration server (10.254.0.25) with auth port 42001 -- remote_registration.py (line 61)
2022-05-16 10:02:38,000::warpinator: Using system zeroconf v0.29.0
2022-05-16 10:02:45,865::warpinator: Server: ACTIVE
2022-05-16 10:02:45,867::warpinator::DEBUG: UI: start discovery timer (no remotes) -- warpinator.py (line 784)
2022-05-16 10:02:49,131::warpinator::DEBUG: UI: Discovery timed out (no remotes) -- warpinator.py (line 800)

Scenario 2, Device A (hanna-laptop):

2022-05-16 10:04:32,217::warpinator::DEBUG: >>> Discovery: new remote: thinkpad-x1 (10.254.0.25:42000) -- server.py (line 246)
2022-05-16 10:04:32,217::warpinator: Registering with thinkpad-x1 (10.254.0.25:42001) - api version 2
2022-05-16 10:04:32,217::warpinator::DEBUG: remote-registration-thread-thinkpad-x1-10.254.0.25:42001-THINKPAD-X1-D6B22C334D0F3F1EFBBA -- remote_registration.py (line 240)
2022-05-16 10:04:32,217::warpinator::DEBUG: Remote: Attempting to register thinkpad-x1 (10.254.0.25) -- remote_registration.py (line 258)
2022-05-16 10:04:32,539::warpinator::DEBUG: Remote: Attempting to connect to thinkpad-x1 (10.254.0.25) - api version 2 -- remote.py (line 197)
2022-05-16 10:04:32,724::warpinator::DEBUG: Remote: waiting for duplex from 'thinkpad-x1' -- remote.py (line 349)
2022-05-16 10:04:32,814::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.AWAITING_DUPLEX **** -- remote.py (line 312)
exception
2022-05-16 10:04:37,790::warpinator::CRITICAL: Problem while awaiting duplex response - api version 2: StatusCode.DEADLINE_EXCEEDED - Server timed out while waiting for his corresponding remote to connect back to you. -- remote.py (line 257)
2022-05-16 10:04:37,790::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.UNREACHABLE **** -- remote.py (line 312)
2022-05-16 10:04:48,124::warpinator::DEBUG: Remote: waiting for duplex from 'thinkpad-x1' -- remote.py (line 349)
2022-05-16 10:04:48,125::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.AWAITING_DUPLEX **** -- remote.py (line 312)
exception
2022-05-16 10:04:54,081::warpinator::CRITICAL: Problem while awaiting duplex response - api version 2: StatusCode.DEADLINE_EXCEEDED - Server timed out while waiting for his corresponding remote to connect back to you. -- remote.py (line 257)
2022-05-16 10:04:54,081::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.UNREACHABLE **** -- remote.py (line 312)
2022-05-16 10:05:04,310::warpinator::DEBUG: Remote: waiting for duplex from 'thinkpad-x1' -- remote.py (line 349)
2022-05-16 10:05:04,316::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.AWAITING_DUPLEX **** -- remote.py (line 312)
exception
2022-05-16 10:05:09,119::warpinator::CRITICAL: Problem while awaiting duplex response - api version 2: StatusCode.DEADLINE_EXCEEDED - Server timed out while waiting for his corresponding remote to connect back to you. -- remote.py (line 257)
2022-05-16 10:05:09,119::warpinator::DEBUG: Remote: thinkpad-x1 is now RemoteStatus.UNREACHABLE **** -- remote.py (line 312)

Scenario 2, Device B (thinkpad-x1):

2022-05-16 10:04:32,344::warpinator::DEBUG: Registration Server RPC: RequestCertificate from hanna-laptop '10.254.0.25' -- remote_registration.py (line 305)
2022-05-16 10:04:32,730::warpinator::DEBUG: Server RPC: WaitingForDuplex from 'hanna-laptop' (api v2) -- server.py (line 404)
2022-05-16 10:04:34,129::warpinator::DEBUG: UI: Discovery timed out (no remotes) -- warpinator.py (line 800)
2022-05-16 10:04:48,234::warpinator::DEBUG: Server RPC: WaitingForDuplex from 'hanna-laptop' (api v2) -- server.py (line 404)
2022-05-16 10:05:04,319::warpinator::DEBUG: Server RPC: WaitingForDuplex from 'hanna-laptop' (api v2) -- server.py (line 404)

It looks like a timeout, but why - I don't know. Can you help me?

levi-jcbs commented 2 years ago

Maybe similar to #99

levi-jcbs commented 2 years ago

In addition to opening ports 42000 and 42001, it is also necessary to open the zeroconf port 5353/udp and then restart the app. Note that the app normally runs in the background when closing the window. It must therefore be really closed via the task manager or killall warpinator.

After that it works for me.