Doing a bit more research, I got to the bootom of this.
In a somewhat recent nordvpn versions, firewall rules in iptables got more restrictive, and dhcp packets would get drop. You can see that by default, your raspberry pi has no rules in the iptables, but when you establish a nordvpn connection, a bunch of rules are added. (use iptables -L) To enable dhcp, you would need to add a rule at the top (Before the drop section), with something like:
That's enough to allow dhcp traffic. Note that if you add this rule after you established a nordvpn connection, it will work. But, if you add this rule before establishing the nordvpn connection, nordvpn will add it's own set of rule before the dhcp related one. in particular, the DROP rules will be above the dhcp one, and therefore the traffic to dhcp won't work anymore, until you add the dhcp rule again.
It's a bit anoying, but the correct bash script / cron job can handle that.
Of course, there is also the option to prevent nordvpn to add it's own firewall rules with something like
In a somewhat recent nordvpn versions, firewall rules in iptables got more restrictive, and dhcp packets would get drop. You can see that by default, your raspberry pi has no rules in the iptables, but when you establish a nordvpn connection, a bunch of rules are added. (use iptables -L) To enable dhcp, you would need to add a rule at the top (Before the drop section), with something like:
Code:
iptables -I INPUT 1 -i wlan0 -p udp --sport 67:68 --dport 67:68 -j ACCEPTIt's a bit anoying, but the correct bash script / cron job can handle that.
Of course, there is also the option to prevent nordvpn to add it's own firewall rules with something like
Code:
nordvpn set firewall disabledStatistics: Posted by cofcof — Mon Mar 17, 2025 11:38 am