norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.6K
active users

#wireguard

4 posts3 participants1 post today

#wireguard weirdness

My phone has a WG client on it that connects back to the house (WG server is on the ASUS router). I can connect to Internet through the tunnel, and two devices (both servers) in the LAN, but not others, even with firewall on the router turned off.

The WG config has AllowedIPs = 0.0.0.0/0

Two of the devices are JetKVMs. Three are cameras. Can't see any restrictions on there.

Replied in thread

@bradley I'm NOT exposing my #pihole (s) directly to the internet - I use one at home and another one via #wireguard #vpn whereever I may roam 🙂 Exposed ports for GUI and "healtchecks" are on a "random" highport which keeps logs mostly clear of "noise". Sometimes some scanners like #censys (or #shodan ) might also find these ports, but #iptables is very helpful 😉
Feel free to ask my via PM if something is not clear. I like feedback to make my docs better.

I'm at the absolute end of my comprehension of Wireguard and WG-Easy. I, for the love of anything, CANNOT get my VPN to stay connected for more than 3 minutes. I have tried connecting via direct Public IP, my Domain with A Certs, PersistentKeepalive, changing/removing UFW/Firewall, hosting on bare metal, LXC, VM. I am at a complete loss and simply do not understand this anymore. If anyone has any ideas, please send them my way. #proxmox #selfhosting #vpn #lxc #vm #wireguard

FFS! A server can't run both #Docker *and* #Wireguard on #Linux.

Docker creates a "bridge" network interface which, apparently, interferes with WireGuard.

That was a depressing evening of eliminating the impossible. Completely stopping Docker allowed my VPN to connect.

And there's no way to actually run a Docker container without the network bridge (any documentation that says otherwise is lying).

Replied in thread

@StaceyCornelius In the past I did configure seperate systems for clients so they can travel without fuss regardless if "P.R." #China or #Russia or the #USA or #KSA...

  • The trick is to never have anything on your device and have a dedicaded burner!

Using @tails_live / @tails / #Tails and @torproject / #TorBrowser and when that's not an option, a #SSH-Tunnel / #OpenVPN or #WireGuard-#VPN to be able to #VNC into a machine.

  • Remember: They can only extract data that was saved on a machine!

CONSIDER THE #US ENEMY TERRITORY AS IN "If you wouldn't enter #NorthKorea, then why would you enter the USA?"

@ceresbzns You'd probably hate it, as it involves using short-lived nfs mounts through #wireguard tunnels. The hosts in the LAN copy the certs they need in this way. Systemd timers automate this "pulling". I only had to write 10 lines of bash code, in the way of actual programming.

Replied in thread

@floe

Through a #wireguard tunnel ssh works in both directions.

With wireguard use PersistentKeepAlive on the "forgetting" side of NAT. Usually a home modem does NAT, so the computer that is not at home needs PersistentKeepAlive, and the home modem ideally has a fixed IP address or a DNS host name.