I was having the same problem of "both your device and browser chose to use connect's relay".
I have a local firewall configured on my RPI 4.
The configuration was:Note: 192.168.0.11 is my windows desktop and the RPI 4 is 192.168.0.30.
I disabled the firewall and peer-to-peer worked.
Alternatively I added a ufw rule giving my windows desktop full access on all sockets.
Again peer-to-peer worked.
Based on that, it seems rpi-connect peer-to-peer uses one or more sockets that my original firewall config did not have.
I googled and I could not find the sockets used between peers published anywhere.
For security reasons I would prefer to not allow unlimited access from my windows desktop.
I have a local firewall configured on my RPI 4.
The configuration was:
Code:
root@picompute:/home/picompute# ufw statusStatus: activeTo Action From-- ------ ----22/tcp ALLOW 192.168.1.0/24 # ssh5900/tcp ALLOW 192.168.0.11 # VNC22/tcp ALLOW 192.168.0.0/24 # ssh5201/tcp ALLOW 192.168.1.0/24 # iperf35201/tcp ALLOW 192.168.0.0/24 # iperf3I disabled the firewall
Code:
ufw disableAlternatively I added a ufw rule giving my windows desktop full access on all sockets
Code:
ufw allow from 192.168.0.11Again peer-to-peer worked.
Based on that, it seems rpi-connect peer-to-peer uses one or more sockets that my original firewall config did not have.
I googled and I could not find the sockets used between peers published anywhere.
For security reasons I would prefer to not allow unlimited access from my windows desktop.
Statistics: Posted by cpottle9 — Tue Dec 24, 2024 10:45 pm