Ancestors

Toot

Written by WeAreAllOne on 2024-12-05 at 13:21

Can't access containers remotely

https://lemm.ee/post/49067507

=> More informations about this toot | More toots from WeAreAllOne@lemm.ee

Descendants

Written by exu on 2024-12-05 at 13:33

Can you ping the server through your tunnel? Maybe try a traceroute to see if it gets through your router correctly.

If this does work, check if the arrs have some “restrict to local network” setting.

If not, I’d check the firewall logs on your router to see if it is blocking the connection.

=> More informations about this toot | More toots from exu@feditown.com

Written by just_another_person@lemmy.world on 2024-12-05 at 14:09

Wireguard only gets you to the endpoint. You need extra routes from there.

Post your wg config, and possibly the staticnroute table on the router.

=> More informations about this toot | More toots from just_another_person@lemmy.world

Written by colonelp4nic@lemmy.world on 2024-12-05 at 14:43

To add, here’s an example of my config addition to ensure 192.168.1.* is accessible over VPN

push "route 192.168.1.0 255.255.255.0 vpn_gateway"

=> More informations about this toot | More toots from colonelp4nic@lemmy.world

Written by just_another_person@lemmy.world on 2024-12-05 at 15:14

OpenVPN does routing a tad differently, but same point applies. Network clients need to know where to go to find a route that isn’t part of the home subnet they are joined too. With containers in the mix without bridging, the host needs to know that the WG subnet can be found at the router.

=> More informations about this toot | More toots from just_another_person@lemmy.world

Written by WeAreAllOne on 2024-12-05 at 15:47

Ah makes sense. I’m using a Mikrotik router and implemented the Back to Home function which automatically creates the tunnel and all firewall configs. Supposedly it’s like me being in my home network but I need to look into your suggestions.

=> More informations about this toot | More toots from WeAreAllOne@lemm.ee

Written by just_another_person@lemmy.world on 2024-12-05 at 16:01

That may look fine from your router’s perspective, but if your network clients don’t get an updated routing tables, they won’t know or possibly accept traffic from the new subnet on the VPN.

=> More informations about this toot | More toots from just_another_person@lemmy.world

Written by WeAreAllOne on 2024-12-05 at 19:35

Solved. All I needed to do was route the Back to Home (wire guard ) address list to a table for the server. 🤙

=> More informations about this toot | More toots from WeAreAllOne@lemm.ee

Written by BCsven@lemmy.ca on 2024-12-06 at 05:35

You can set up one device to do masquerading and forwarding then you can see entire lan

=> More informations about this toot | More toots from BCsven@lemmy.ca

Written by Hiro8811@lemmy.world on 2024-12-08 at 09:42

I’m not familiar with wireguard but I use Tailscale and it works really well

=> More informations about this toot | More toots from Hiro8811@lemmy.world