OpenVPN not working after restart …
-
What rule are you speaking of?
-
OpenVPN traffic is blocked after restart… I must open ANY wan or lan rule, click save and then apply for unblocking openvpn.
-
Exactly which version and build of pfSense are you running?
-
PC Version
1.0.1-SNAPSHOT-03-15-2007
built on Mon Mar 19 13:32:03 EDT 2007 -
If you run pfctl -sr | grep tun from SSH before you save/apply the rule I presume you do NOT get two lines like this:-
pass out quick on tunx all keep state label "let out anything from firewall host itself openvpn"
pass in quick on tunx all keep state label "let out anything from firewall host itself openvpn"where tunx is the OpenVPN tunnel (if you only have one it will be tun0)
and after save/apply rule you DO get two lines like that.
-
As you say… (write) ...
after restart there is no rule to pass traffic on tun interface...When i change rule and click apply ...
pass out quick on tun0 all keep state label "let out anything from firewall host itself openvpn"
pass in quick on tun0 all keep state label "let out anything from firewall host itself openvpn" -
Try letting the system boot. And then from a shell run:
/etc/rc.filter_configure_sync
Does this solve the issue?
-
Yes, it solve my problem after reboot…
pfctl -sr | grep tun
/etc/rc.filter_configure_sync
pfctl -sr | grep tun
pass out quick on tun0 all keep state label "let out anything from firewall host itself openvpn"
pass in quick on tun0 all keep state label "let out anything from firewall host itself openvpn" -
Try this from a shell:
fetch -o /etc/inc/openvpn.inc http://www.pfsense.com/~sullrich/openvpn.inc.txt
Reboot and see if they come up correctly now.
Thanks!
-
Oh yes, this help to solve my problem!
;D
Now i can connect to my pfsense box after restart via openvpn without any problems!
-
Great! I'll commit now.
-
And thank you and sh_man very much for your help and time…