1
23.7 Legacy Series / Firewall itself not going through VPN
« on: September 15, 2023, 07:03:30 pm »
So I managed to get my whole network back up and running for Wireguard, minus one caveat... It appears that the firewall itself cannot connect to the Internet when trying to directly access external sites. For example, I can't get the latest DNS blocklists for Unbound, and can't ping ip addresses (whether they're external or internal to the VPN). I noticed that the traffic attempts to go through my main ISP true IP address instead of the wireguard, resulting in it just failing.
How can I get the firewall to see "itself" as the IP address of the main wireguard ip address instead of the ISP's? Or to ask in an easier way, how can I force the firewall's traffic (outside the regular connection to my ISP for connectivity) to be completely routed through the VPN?
How can I get the firewall to see "itself" as the IP address of the main wireguard ip address instead of the ISP's? Or to ask in an easier way, how can I force the firewall's traffic (outside the regular connection to my ISP for connectivity) to be completely routed through the VPN?