heiher/hev-socks5-tunnel

can't get FULL CONE NAT

Closed this issue · 5 comments

lvlynn commented
  1. use udp over udp , nintendo switch get F
  2. use udp over tcp, nintendo switch get B
  3. use udp over udp , use pystun test show NAT Type: Blocked （https://github.com/jtriley/pystun）
heiher commented

The NAT type depends on server side.

lvlynn commented

My server has public IP ， and I open ALL INPUT、OUTPUT rule。 I use other socks client test NAT function. Pystun show Full Cone， like below picture:
1679915450364

lvlynn commented

I've already tried "hev-socks5-server" and 3proxy project. The result is

  1. use udp over udp , nintendo switch get F
  2. use udp over tcp, nintendo switch get B
  3. use udp over udp , use pystun test show NAT Type: Blocked
    I think the issue arises in "hev-socks5-tunnel" client.
heiher commented

On my side:

  • socks5 server: hev-socks5-server
  • socks5 client: hev-socks5-tunnel (global routing + udp in tcp mode)
  • NAT type checker: Natter
# python3 natter.py -t 3456
[INFO] - Getting STUN server IP...
[INFO] - Checking NAT Type for UDP...
[INFO] - NAT Type for UDP: [ Full cone (NAT 1) ]
[INFO] - Checking NAT Type for TCP...
[INFO] - NAT Type for TCP: [ Symmetric ]
[ERROR] - You cannot perform TCP hole punching in a symmetric NAT network.