Re: 6.2-STABLE: enc0 sees only outgoing packets in pf

2007-03-26 Thread Andre Albsmeier
On Mon, 26-Mar-2007 at 17:07:47 +1200, Andrew Thompson wrote: > On Mon, Mar 26, 2007 at 02:58:20AM +0200, Volker wrote: > > Andrew, Andre & all, > > > > I've checked it out once more (with a corrected setup) and now have > > been able to block traffic on enc0 in both directions (no matter if > > t

RE: Pass through packets

2007-03-26 Thread Greg Hennessy
> Hi, > > I just want to know how to handle properly packets which pass > through the firewall... That depends on what you're trying to do exactly. > > I can handle for all packets coming to all interface of my > firewall and the same with outgoing packets by using in/out > with statement

Pass through packets

2007-03-26 Thread Guillaume
Hi, I just want to know how to handle properly packets which pass through the firewall... I can handle for all packets coming to all interface of my firewall and the same with outgoing packets by using in/out with statement "on $interface" But what about forwarding packets ? With iptables we ca

Re: 6.2-STABLE: enc0 sees only outgoing packets in pf

2007-03-26 Thread Volker
On 03/26/07 08:47, Andre Albsmeier wrote: > On Mon, 26-Mar-2007 at 02:58:20 +0200, Volker wrote: >> Andrew, Andre & all, >> >> I've checked it out once more (with a corrected setup) and now have >> been able to block traffic on enc0 in both directions (no matter if >> the tunnel endpoint is final d

Current problem reports assigned to you

2007-03-26 Thread FreeBSD bugmaster
Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description o kern/82271 pf [pf] cbq scheduler cause bad latency o kern/92949 pf [pf] PF + ALTQ problems

Re: conf/110838: tagged parameter on nat not working

2007-03-26 Thread Remko Lodder
Synopsis: tagged parameter on nat not working Responsible-Changed-From-To: freebsd-bugs->freebsd-pf Responsible-Changed-By: remko Responsible-Changed-When: Mon Mar 26 09:11:58 UTC 2007 Responsible-Changed-Why: Over to maintainer group, although this might not be fixed in the 5_branch since (from