Wireguard Lan - Lan bridge working but does not allow ports through
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
The setup is
My PCs Windows 11, 8.1 and Mac OS connected to my TP Link ER7412-M2, the Omada Software Controller is running in Docker on my Synology NAS
The router is connected to the Fiber Modem of the "Deutsche Telekom" and I have a own public iPv4 address.
The other end has a FritzBox 7590AX and there is backup NAS and a remote PC
The FritzBox and the TP Link ER7412-M2 are connected over the internet with Wireguard, but I noticed following issue I can access the devices on the remote network but only without ports, so if I want to access my remote NAS [on port 443 or any other port] or the remote PC with RD, the connection fails.
When I had before at my own a FritzBox and both were connected with Wireguard it also passed ports from the remote network through.
Weirdly for a single device/ the device that establishes the connection you can ping it with all ports, so e.g. from my Laptop I can access over Wireguard my PC on all ports, same for the FritzBox on the other end I can ping it on all ports.
Something else I noticed if I allow NetBios names in the FritzBox at the remote end they are also not passed through.
Just wanted to say that for now, if I'm doing something wrong, please let me know
Here is a screenshot where I tried to ping my NAS on the other end (the NAS Firewall is fully disabled)
Just sayin' I disabled for both Networks iPv6 since I still get a "own" public iPv4 without CGNAT or CGN) and if it matters the network here is 172.16.250.0/24 and the remote network 192.168.188.0/24.
Maybe it is also not yet implented, as I saw in the forum some topics that they will ACL and that for Wireguard somewhen with firmware updates.
Hi @Julian2111
Thanks for posting in our business forum.
You really sure that ping:80 is the proper syntax for this line?
I have tested that WG works well with accessing a web service in another LAN. That does not require anything special if your routing is correct.
Hi @Julian2111
Thanks for posting in our business forum.
You really sure that ping:80 is the proper syntax for this line?
I have tested that WG works well with accessing a web service in another LAN. That does not require anything special if your routing is correct.