1
Virtual private networks / Troubles getting WireGuard to work
« on: August 29, 2021, 08:59:10 pm »
Hello together!
I would highly appreciate some help since I have troubles to get my wireguard to work. I am fairly new to networking.
Here is my current homenetwork setup:
INTERNET <------> Huawei LTE Router <----BRIDGE MODUS without firewall ----> OPNense APU4d4 Router <---- > Homenetwork
If I connect from my Phone in the same network WLAN to Wireguard it works without problems as long as I connect to the WAN IP shown belown. As soon as I try to use my phones lte network or if I try to use my public facing IP it doesn't connect anymore. I tried to monitor all traffic on my opnsense with the wireguard port 51820, however if I try to connect to the public facing IP or the the WAN via LTE i don't see a single packet.
My WAN IP is: 10.45.XX.XX
And my public facing IP is: 194.230.XXX.XXX
I setup all necessary NAT and Firewall rules as shown in the guides in the official docs. I have no clue what I am doing wrong. A few months ago I tried to setup openVPN where I ran in a very similar problem.
I would highly appreciate some help since I have troubles to get my wireguard to work. I am fairly new to networking.
Here is my current homenetwork setup:
INTERNET <------> Huawei LTE Router <----BRIDGE MODUS without firewall ----> OPNense APU4d4 Router <---- > Homenetwork
If I connect from my Phone in the same network WLAN to Wireguard it works without problems as long as I connect to the WAN IP shown belown. As soon as I try to use my phones lte network or if I try to use my public facing IP it doesn't connect anymore. I tried to monitor all traffic on my opnsense with the wireguard port 51820, however if I try to connect to the public facing IP or the the WAN via LTE i don't see a single packet.
My WAN IP is: 10.45.XX.XX
And my public facing IP is: 194.230.XXX.XXX
I setup all necessary NAT and Firewall rules as shown in the guides in the official docs. I have no clue what I am doing wrong. A few months ago I tried to setup openVPN where I ran in a very similar problem.