Unable to interface with DietPi over personal VPN

[trendy]

A few of them.

Wireguard server + OpenVPN client, again

This one makes sure the wireguard will use the ISP and not the VPN. Then you need to masquerade wireguard IPs to the eth0 IP when the destination is in the lan, or to the openvpn client when the destination is the internet.

Need VPN iproute help

Given the requirement to route only the hotspot over vpn, I would suggest the following. Filter the default gateway from the OpenVPN client. cat << EOF >> /etc/openvpn/client.conf pull-filter ignore redirect-gateway route-nopull EOF Now your default gateway remains the eth1 after the VPN is up. Isolate the hostspot and route it over the VPN ip rule add from 192.168.42.0/24 lookup 42 ip route add default via 10.6.19.1 dev tun1 table 42 Fix the firewall iptables -t nat -A POSTROUTING -s 1…

Wireguard, iptables and access to dietpi from another VLAN

I am trying to ssh to DietPi that has a running Wireguard client from a PC on another VLAN. As my issue seems to be closely related with what was discussed in this topic: Wireguard Client & iptables I have based my iptables rules on the proposed solutions there. However, while the solution works fine as long as I am accessing DietPi from a machine that is on the same VLAN, the access is denied when I move to another VLAN. I have the following setup. PC on VLAN 1, Dietpi running Wireguard and Mo…