Is fixed now John, I had user and group nobody by accident in my custom openvpn config which was breaking the execution of the updown script.
I will remove my amendments now from firewall-start as they wont be needed now the DNS block rules are correctly removed on vpn shutdown.
For my VPN I use 192.168.0.1 which is pushed by my VPN via a DHCP push command, although I am not sure if that actually works so I have a openvpn-event script set which puts a dnsmasq conf in place that has 192.168.0.1 set as the dns server. All my lan devices still use the router as the DNS server.
The issue was ip6tables block rules which were left in place due to me breaking the updown.sh script on openvpn shutdown
Whilst we on the subject of openvpn, I have noticed that when the openvpn is running, ipv6 traffic still works normally outside of the vpn. I do not mean dns lookups but actual normal ipv6 traffic, so if a dns lookup returns ipv6 addresses like e.g. on youtube, then youtube would not go over the vpn.
I will remove my amendments now from firewall-start as they wont be needed now the DNS block rules are correctly removed on vpn shutdown.
For my VPN I use 192.168.0.1 which is pushed by my VPN via a DHCP push command, although I am not sure if that actually works so I have a openvpn-event script set which puts a dnsmasq conf in place that has 192.168.0.1 set as the dns server. All my lan devices still use the router as the DNS server.
The issue was ip6tables block rules which were left in place due to me breaking the updown.sh script on openvpn shutdown
Whilst we on the subject of openvpn, I have noticed that when the openvpn is running, ipv6 traffic still works normally outside of the vpn. I do not mean dns lookups but actual normal ipv6 traffic, so if a dns lookup returns ipv6 addresses like e.g. on youtube, then youtube would not go over the vpn.
Last edited: