hking0036

Hey all, I use Mullvad; I set up wg2 as a tunnel successfully and I have a few containers running in it, however I'm trying to port forward thru mullvad. In the CLI for a container, I can verify that I am connected to the VPN, however when I check the port it tells me it is not forwarded. Is this a limitation of the feature currently, or a misconfiguration on my end, and if so, how can I address it? Thanks! ed. I'm a dunce... Same issue here as Purely8120 above, but I've not attempted to set an iptables rule. ed2; Tried setting those IPTables rules under [Interfaces], import it, and reboot, and I'm still getting a bad response unfortunately. ed3; I've tried hitting my head against the wall in a number of ways; I have read up on what exactly the iptables is setting and it seems to make sense; I've tried replacing -I with -A (no reason why append would work differently but insert, but whatever), no dice, tried even changing the peer endpoint to the now opened port, no dice. I've gone back to a container with the wireguard support built-in, and it is working fine now, I just would love for the built-in feature to work so as not to use so many slots. If anyone has some wisdom to add to the equation, please let me know.

Ah, yeah, they are both on the same subnet. Maybe it would be less of a fight if I was to make a distinction on that front; I'll try and configure that some more when I get the opportunity.

Hey all. I have a wireguard tunnel set up on my server, and I have the port forwarded already, as well as two peers. On my phone (first peer), the traffic is routed as expected, and I can access everything. On my laptop (second peer), the traffic is routed through the tunnel, and I can still access the internet, but whenever I attempt to connect to my server on the remote LAN (192.168.1.xxx), I am instead accessing the actual local net where I am. Since the traffic is going through, I assume that this is a configuration error on my end, but looking at the wireguard peer settings, I can't tell what is different between my phone and my laptop peer that is causing this issue. I have read that you need to have the allowed IPs set to 0.0.0.0/0 in order to block all local traffic, and it is set that way on my machine, but this is still going on. I can even ping from the server UI to the device and get a response. What is it that I'm missing? Here is a screenshot from the client's end on the peer settings: