search

tasket / Qubes-vpn-support

VPN configuration in Qubes OS
GNU General Public License v3.0
126 stars 28 forks source link

f-30 iptables: bad rule #53

Closed ghost closed 4 years ago

ghost commented 4 years ago 
Apr 05 01:23:49 sys-vpn systemd[1]: Starting VPN Client for Qubes proxyVM...
Apr 05 01:23:49 sys-vpn qubes-vpn-setup[715]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:23:50 sys-vpn qubes-vpn-setup[715]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:23:52 sys-vpn qubes-vpn-setup[715]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:23:52 sys-vpn qubes-vpn-setup[715]: Error: Firewall rule(s) not enabled!
Apr 05 01:23:52 sys-vpn systemd[1]: qubes-vpn-handler.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 01:23:52 sys-vpn qubes-vpn-setup[989]: STOP-ing network forwarding!
Apr 05 01:23:52 sys-vpn systemd[1]: qubes-vpn-handler.service: Failed with result 'exit-code'.
Apr 05 01:23:52 sys-vpn systemd[1]: Failed to start VPN Client for Qubes proxyVM.
Apr 05 01:24:03 sys-vpn systemd[1]: qubes-vpn-handler.service: Scheduled restart job, restart counter is at 1.
Apr 05 01:24:03 sys-vpn systemd[1]: Stopped VPN Client for Qubes proxyVM.
Apr 05 01:24:03 sys-vpn systemd[1]: Starting VPN Client for Qubes proxyVM...
Apr 05 01:24:03 sys-vpn qubes-vpn-setup[1004]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:05 sys-vpn qubes-vpn-setup[1004]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:07 sys-vpn qubes-vpn-setup[1004]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:07 sys-vpn qubes-vpn-setup[1004]: Error: Firewall rule(s) not enabled!
Apr 05 01:24:07 sys-vpn systemd[1]: qubes-vpn-handler.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 01:24:07 sys-vpn qubes-vpn-setup[1012]: STOP-ing network forwarding!
Apr 05 01:24:07 sys-vpn systemd[1]: qubes-vpn-handler.service: Failed with result 'exit-code'.
Apr 05 01:24:07 sys-vpn systemd[1]: Failed to start VPN Client for Qubes proxyVM.
Apr 05 01:24:17 sys-vpn systemd[1]: qubes-vpn-handler.service: Scheduled restart job, restart counter is at 2.
Apr 05 01:24:17 sys-vpn systemd[1]: Stopped VPN Client for Qubes proxyVM.
Apr 05 01:24:17 sys-vpn systemd[1]: Starting VPN Client for Qubes proxyVM...
Apr 05 01:24:17 sys-vpn qubes-vpn-setup[1015]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:19 sys-vpn qubes-vpn-setup[1015]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:21 sys-vpn qubes-vpn-setup[1015]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 05 01:24:21 sys-vpn qubes-vpn-setup[1015]: Error: Firewall rule(s) not enabled!
Apr 05 01:24:21 sys-vpn systemd[1]: qubes-vpn-handler.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 01:24:21 sys-vpn qubes-vpn-setup[1023]: STOP-ing network forwarding!
Apr 05 01:24:21 sys-vpn systemd[1]: qubes-vpn-handler.service: Failed with result 'exit-code'.
Apr 05 01:24:21 sys-vpn systemd[1]: Failed to start VPN Client for Qubes proxyVM.
tasket commented 4 years ago

@0rb677 FWIW, I haven't been able to reproduce this problem with the regular Qubes fedora template versions 30 and 31.

If this is still an issue I recommend switching to Debian as I've never had to code workarounds for Debian startup the way I've had to in the past with Fedora.

ghost commented 4 years ago

@tasket its fixed. And its worked good for me now. I use debian templates as vpn too.Thank you.