Trying to open up a port through the WireGuard VPN tunnel with this command:
Fails out of the box:
This worked flawlessly on my old RT-AX86U. I then noticed a route on the old
router was missing on the new one (RT-BE86U).
So I ran this command to fix the issue:
Now NAT PMP responses are working again.
Shouldn't VPN Director be adding the above route automatically?
Is this a firmware bug @RMerlin? I'm running the latest version (3006.102.7).
This router isn't that popular as I understand it, but it's clearly more responsive
than my old RT-AX86U because of the CPU. The GUI feels more snappy and I get
much higher throughput through the WG tunnel.
Code:
natpmpc -g 10.2.1.1 -a 1 0 udp 60Fails out of the box:
Code:
Thu Feb 26 15:03:04 CET 2026
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.2.1.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -100 (TRY AGAIN)This worked flawlessly on my old RT-AX86U. I then noticed a route on the old
router was missing on the new one (RT-BE86U).
So I ran this command to fix the issue:
Code:
ip route add 10.2.1.1/32 dev wgc1Now NAT PMP responses are working again.
Shouldn't VPN Director be adding the above route automatically?
Is this a firmware bug @RMerlin? I'm running the latest version (3006.102.7).
This router isn't that popular as I understand it, but it's clearly more responsive
than my old RT-AX86U because of the CPU. The GUI feels more snappy and I get
much higher throughput through the WG tunnel.
