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
natmap was used for TCP / UDP hole punching under a NAT1 environment.
For communication, user should:
Listen to a port bind by natmap, or
Add port forwarding (DNAT) rules to firewall, or
Use build-in forward method.
After some tries, seems only the first method can co-operate with udp2raw.
No data can be received by udp2raw server using port forwarding provided by firewall, and udp2raw client and server cannot establish connection using natmap's build-in forward feature.
#201 talked about add SO_REUSEPORT for performance purpose. But seems SO_REUSEPORT is still not enabled at current.
natmap's solution for bind same port requires Linux kernel 5.6 or newer, though there's a number of routers using kernel older than 5.6.
I've compiled an udp2raw binary with SO_REUSEPORT enabled and it just works, so any plans for adding it as an option?
The text was updated successfully, but these errors were encountered:
natmap was used for TCP / UDP hole punching under a NAT1 environment.
For communication, user should:
After some tries, seems only the first method can co-operate with udp2raw.
No data can be received by udp2raw server using port forwarding provided by firewall, and udp2raw client and server cannot establish connection using natmap's build-in forward feature.
#201 talked about add SO_REUSEPORT for performance purpose. But seems SO_REUSEPORT is still not enabled at current.
natmap's solution for bind same port requires Linux kernel 5.6 or newer, though there's a number of routers using kernel older than 5.6.
I've compiled an udp2raw binary with SO_REUSEPORT enabled and it just works, so any plans for adding it as an option?
The text was updated successfully, but these errors were encountered: