OpenVPN not working after restart …
-
I have this problem as well with slow machines running off the cd/floppy disk. It could be a timing problem or to do with a fix that was put in recently to stop the OpenVPN port (1194) from being hijacked by another process.
Basically the two rules to allow traffic in and out of the TUNx interface are not written. When you change a filter rule and apply (you do not actually have to change anything, just save!) the rules get written.
Either way I agree it is a pain but at least you know how to get traffic moving!
-
Hmm - should have checked BEFORE posting :D. I have just downloaded the livecd snapshot and tried it and had no problems.
Which snapshot are you running? Scott put in a fix yesterday that solved some problems with TUNx interface being blocked - which is what is causing your problem.
Check that the snapshot you are using is after 1.0.1-SNAPSHOT-03-08-2007 built on Thu Mar 15 11:35:13 EDT 2007 - check the file creation date on the snapshot if you are not sure.
-
I tried download and apply last snapshot before i start writing this post…
And dont help me... :D -
Not being a developer I probably can't help much more.
Have a look at this thread which will help you track down whether it is the same problem I had
http://forum.pfsense.org/index.php/topic,4020.0.html
-
Ech.. i hope that some developer fix this soon :(
-
This has been fixed. Upgrade to a recent snapshot.
-
Sorry but not help to me…
I tried last snapshot and I still must update any rule after pfsense restart... before that, openvpn dont work :(
-
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…