You are here

Wireguard Supernode does not connect to a 2nd Node as a Server

8 posts / 0 new
Last post
AA3JC
Wireguard Supernode does not connect to a 2nd Node as a Server
Hi All,

I have an AC3 setup as a Supernode running 20240405-0dba266 firmware. Currently I have 3 active Tunnels configured,  2 as a Server (1 standard, 1 Wireguard), and 1 Tunnel Client.  All working correctly with blue cloud indicated.  Problem is, when I try to add another Wireguard entry in the Tunnel Server, it will not connect to the new entry at 172.30.64.xxx:6527  

MAIN ROUTER CONFIGURATION:
1.  My internet router has ports 6526-6535 UDP, & port 5526 TCP all forwarded to 192.168.10.211 that is my AA3JC-HAPAC3-SUPERNODE, with DHCP reserved address reservation.

2. I currently have an active Wireguard connection on port 6526, so I know my port forwarding is working. I also checked my internet router's port forwarding  & port trigger settings for overlapping or conflicting port assignments, and none were found.

MY TUNNEL SERVER CONFIGURATION:
Tunnel Server Network:  172.30.63.xxx
Wireguard Server Network:  172.30.64.xxx

Current Tunnel::  One standard Tunnel connected on the 172.30.63.xxx node (blue cloud present). 

Wireguard Server:   One Wireguard connection 172.30.64.xxx:6526 that is working (blue cloud present).

Tunnel Client:  
                            Tunnel Client:  Setup to one Node 172.30.2.xxx:6529
K6CCC
K6CCC's picture
You typed port 65xx.  Do you
You typed port 65xx.  Do you really mean ports 65xx as opposed to the standard AREDN WG tunnels starting at 5525?
AA3JC
Wireguard on a Supernode
Wireguard tunnel server uses 6526 udp and as you add more wireguard nodes increments up by 1.
AA3JC
Issue resolved
It seems my finger & eye coordination is lacking.  In my main router port forwarding I had added a port forwarding rule for ports 6526 to port 6535, but typed in 6526;6535 instead of 6526:6535.  Using a semicolon instead of a colon broke the port rule for all but the very first port of 6526.  Lesson learned, be  careful what you type!

 
k1ky
k1ky's picture
Wireguard 55xx or 65xx Port clarification?
All of my WG Tunnel Servers start with 5525 and increment by 1 from there.  Where is this 6525+ port assignment coming from and is it configurable?
nc8q
nc8q's picture
Wireguard 55xx or 65xx Port clarification?:
All of my WG Tunnel Servers start with 6526 and increment by 1 from there.
 
Image Attachments: 
w6bi
w6bi's picture
Wireguard tunnels
Tom, ports 5525 and up are used for Wireguard tunnels between normal nodes; ports 6525 & up are used between Supernodes.

Orv W6BI
 
K6CCC
K6CCC's picture
SuperNode vs traditional nodes
Looks like SuperNodes use different port numbers than traditional nodes for WireGuard tunnels.
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer