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
If I add an ACCEPT rule for port 4096 - instead of DROP, the client reaches the client_ready state - the connection appears to be successful. But then I cannot start Wireguard on the client because the port is already being used (by udp2raw).
If I don't add any rule for udp2raw, I get the same output I pasted in the client section above ([INFO](re)sent tcp syn echoing forever). It seems the DROP rules are not working as expected.
The text was updated successfully, but these errors were encountered:
If I add an ACCEPT rule for port 4096 - instead of DROP, the client reaches the client_ready state - the connection appears to be successful. But then I cannot start Wireguard on the client because the port is already being used (by udp2raw).
"Wireguard port being used" is not relevant to iptables or nftables rules or udp2raw can connect or not.
If it says port occupied there must be some problem in otherwhere.
Check your settings of wireguard, and see if you specific some source port to use. Remove the source port or change to another source port.
On the client side it's typically not necessary to specify a source port.
I commented out the ListenPort in the wireguard client config, so it picks a random port on startup. After bringing wireguard up, I take note of the port number and pass it to the udp2raw client command: -l0.0.0.0:<random_port>. But sadly it's still not working.
It's not completing the handshake. It's like client and server are not agreeing on something. I even see "new packet from 127.0.0.1:55820".
I'm about to give up trying to run udp2raw on OpenWrt. I've used it successfully before on a Raspberry Pi. I just wonder if it's possible to keep wireguard on the router, and run udp2raw somewhere else in the LAN.
Client
System info:
udp2raw_amd64
Server
System info:
udp2raw_mips24kc_le
/etc/config/firewall
/etc/udp2raw.nft
/etc/init.d/udp2raw
[INFO](re)sent tcp syn
echoing forever). It seems the DROP rules are not working as expected.The text was updated successfully, but these errors were encountered: