Archer Axe5400 wireguard not properly listening on port
I am trying to create Wireguard VPN server for my devices when Im out of country, but the problem is that no matter what port I set for it to listen to they all dont work
I'm using 2 routers setup:
- IPS router that acts as modem, is connected directly to fiber and has public IP and this
- Axe5400 router which gets dynamic IP from IPS
I properly port forwarded everything, so idk what could be the problem, I also tried using https://canyouseeme.org/ but it gives me error too
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @RVeir ,
Here are some important points and troubleshooting steps to ensure port forwarding works correctly:
1. Ensure your server is accessible from the internal network. Before testing from outside, make sure your WireGuard server is running and reachable from devices connected to your local network.
2. Check your WAN IP address. Your router must have a public WAN IP address for port forwarding to work. If your router receives a private IP address (such as those in the 100.64.0.0 to 100.127.255.255 range, known as CGNAT), port forwarding will not function. You may need to set your ISP router to bridge mode or request a public IP from your ISP.
3. Firewall settings. Make sure the firewall on your VPN server device allows incoming traffic on the WireGuard port you configured.
4. Port Forwarding/DMZ Priority. If you are using both port forwarding and DMZ, note that port forwarding rules take priority over DMZ settings.
5. Double NAT scenario. Since you have two routers, ensure that port forwarding is set up on both the ISP router (to forward to your Wi-Fi Router) and on your Wi-Fi Router (to forward to the WireGuard server). This is a common issue in double-router setups.
For detailed instructions on configuring port forwarding and more troubleshooting tips, please refer to this FAQs:
how to set up virtual server on TP-Link wireless router?
Why port forwarding feature is not working on my Wi-Fi router?
- Copy Link
- Report Inappropriate Content
Hi,
Is the public IP address that is shown inside your ISP router identical to the IP address shown by canyouseeme.org ?
Have you also tested the OpenVPN server of the AXE5400 ?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Ok, that's good.
Can you please share a screenshot that shows how you've set up the port forwardings for WireGuard and/or OpenVPN on the ISP router?
- Copy Link
- Report Inappropriate Content
Hello @RVeir ,
Here are some important points and troubleshooting steps to ensure port forwarding works correctly:
1. Ensure your server is accessible from the internal network. Before testing from outside, make sure your WireGuard server is running and reachable from devices connected to your local network.
2. Check your WAN IP address. Your router must have a public WAN IP address for port forwarding to work. If your router receives a private IP address (such as those in the 100.64.0.0 to 100.127.255.255 range, known as CGNAT), port forwarding will not function. You may need to set your ISP router to bridge mode or request a public IP from your ISP.
3. Firewall settings. Make sure the firewall on your VPN server device allows incoming traffic on the WireGuard port you configured.
4. Port Forwarding/DMZ Priority. If you are using both port forwarding and DMZ, note that port forwarding rules take priority over DMZ settings.
5. Double NAT scenario. Since you have two routers, ensure that port forwarding is set up on both the ISP router (to forward to your Wi-Fi Router) and on your Wi-Fi Router (to forward to the WireGuard server). This is a common issue in double-router setups.
For detailed instructions on configuring port forwarding and more troubleshooting tips, please refer to this FAQs:
how to set up virtual server on TP-Link wireless router?
Why port forwarding feature is not working on my Wi-Fi router?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 190
Replies: 4
Voters 0
No one has voted for it yet.