"
Holla!
A workaround is to use a server inside your network wich NATs incoming traffic to gateway then out to internet.
i got a wireguard-server on my LAN wich runs dietpiVM (80mb ram usage) i have forwarded the listening-port to the router wich routes all traffic thru mullvad (wich means that i have to portforward again in mullvads webinterface).
So i connect to the mullvad public ip + port to access my wireguardserver wich then routes it to the internet (via same mullvad tunnel).
result: I can access my home network + internet thru a secure tunnel + bonus using a piholeVM to block ads over tunnel aswell.
its not perfect but it works and its stable, i havent done any speedtests but havent noticed any latencies in real day to day using.
Hope this helps
A workaround is to use a server inside your network wich NATs incoming traffic to gateway then out to internet.
i got a wireguard-server on my LAN wich runs dietpiVM (80mb ram usage) i have forwarded the listening-port to the router wich routes all traffic thru mullvad (wich means that i have to portforward again in mullvads webinterface).
So i connect to the mullvad public ip + port to access my wireguardserver wich then routes it to the internet (via same mullvad tunnel).
result: I can access my home network + internet thru a secure tunnel + bonus using a piholeVM to block ads over tunnel aswell.
its not perfect but it works and its stable, i havent done any speedtests but havent noticed any latencies in real day to day using.
Hope this helps
