On Thu July 19 2007 5:12:58 pm Bill wrote: > On Thu, 19 Jul 2007 15:06:55 -0700 > > <[EMAIL PROTECTED]> spake: > > I have the same problem. I was going to post a this question too > > along with another question. > > > > When I first boot up my OpenBSD 4.1 sever. I can not access my > > OpenVPN wireless connection. I can access ssh wirelessly though. > > So what I do is login via ssh and run pfctl -f /etc/pf.conf. Now > > my OpenVPN connection works just fine. I too have my startup > > script in /etc/rc.local but it is much simpler: > > > > /usr/local/sbin/openvpn /var/openvpn/server.conf > > > > I am curious to know why pf requires a command line start for it to > > work. > > I have a few OpenVPN installations running and do not have this problem > with any of them. I start my PF normally through the rc.conf.local >
Same here I have few installations which are very reliable and problem free. > Do you have a hostname.tun0 file in /etc? > > I forget if OpenVPN will create the tun0, but it could be why PF needs > to be run after in your instance. I have simply: > > UP my hostname.tun0 is set to inet 0.0.0.0 0.0.0.0 NONE Either way probably works fine. Have you checked out your log files? Openvpn does a good job logging in my experience. If the logs are empty I would try turning up the verbosity or running openvpn by hand before doing a reload of the pf rules. It would also be interesting to run pfctl -sr before reloading to see if they even loaded properly. -- Tim Kuhlman Network Administrator ColoradoVnet.com
