Hello Everyone,

I have an issue with Wireguard. It's similar case (or at least seems so) as in this topic: https://community.tp-link.com/en/business/forum/topic/610050

however I do not know what's the actual solution and if the OP actually had the same exact problem as I did.

The idea is that I want any and all traffic to pass through the VPN, as if I've been connecting from (say) home.

Once I connect, I have no trouble reaching local hardware. But when I try to browse the net, it doesn't work at all.

Moreover - if I connect to a jumphost (be it Windows or Linux based, doesn't matter), the jumphost itself has now trouble reaching the outside world.

I can't open any network site, ping times out, and if I try to use my local DNS, even the name resolution fails, as the DNS itself can't reach outside world (I don't have and don't want to cache entries for hours or days, that's not the point here and it still won't fix anything besides the name resolution).

I thought that when I set the allowed IPs to 0.0.0.0/0, then everything will work as planned but it clearly doesn't.

It is as if the whole traffic is being routed back to WG subnet instead of going where it's supposed to (WAN in that case), but that's just a wild guess.

Can anyone help me out? Am I doing something wrong or it's like that by design (and if so, why?).

ps. congratulations on the regexp words filtering - if one sentence in post ends in " T " and the next begins with " IT'S " it's interpreted as female feeding organs. Flabbergasting.