Hi list again,
Sorry for delayed replie, I was away :)
My problem was solved by adding:
pass quick on tun0
to my /etc/pf.conf
Thanks Mark Rolen
Update. With help from the mailing list, both of my problems have
been solved. The first problem was the same as the original
poster. To reiterate, the problems were:
1. On startup, pf would not allow any packets through on tun0.
Thus openvpn would not work. The temporary fix was to ssh
I do have an /etc/hostname.tun0 file that I created manually with
touch.
What is the theory of openvpn being the problem source? Obviously
openvpn started up correctly or I would have to do more to fix the
problem than merely running pfctl -f /etc/pf.conf. :-) Thanks for
the pfctl -sr
* jean-philippe luiggi [EMAIL PROTECTED] [2007-07-20 03:04]:
I'm perhaps wrong but i think the interface must exists before loading
any rules which use it.
yes, you are almost wrong.
--
Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED]
BS Web Services, http://bsws.de
Full-Service ISP -
Mark Rolen [EMAIL PROTECTED] wrote:
I had the same symptom, where I'd have to manually reload my pf
rules
after a reboot to get OpenVPN traffic to flow. Using tcpdump
showed
that pf was blocking all the traffic on my tun interfaces although
I had
a set skip rule for them.
Here are my pf
[EMAIL PROTECTED] wrote:
Does this point to a problem with set skip on { lo, tun0 }? I
will try your suggestion to see if it works (pass quick on { tun0
tun1 }), but I dislike using quick in my rules.
I added up to my /etc/hostname.tun0 to see if that worked based
on one of the suggestions
On Fri, 20 Jul 2007 09:46:41 -0700 Mark Rolen [EMAIL PROTECTED]
wrote:
Using
the pass quick on tun0 rule somewhere at the top of your rules
should
work for you, let me know if not.
I made the following two changes to my pf.conf and this fixed the
problem.
#set skip on { lo, tun0 }
pass
Hi list,
I'm having weird problem with my openvpn install and pf.
I start vpn and connect to it from client computers with no problems,
but I can't access any computers on internal lan. Then I issue pfctl -f
/etc/pf.conf and everything starts to work. So my rc.local script is:
---
if [
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
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.
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
I had the same symptom, where I'd have to manually reload my pf rules
after a reboot to get OpenVPN traffic to flow. Using tcpdump showed
that pf was blocking all the traffic on my tun interfaces although I had
a set skip rule for them.
I may not be completely right here, but I believe pf
Hello,
I'm perhaps wrong but i think the interface must exists before loading
any rules which use it.
Best regards,
Jean-philippe.
On Thu, 19 Jul 2007 10:47:31 +0300
Tomas [EMAIL PROTECTED] wrote:
Hi list,
I'm having weird problem with my openvpn install and pf.
I start vpn and connect
13 matches
Mail list logo
