Re: Getting Involved

2012-01-21 Thread Bjoern A. Zeeb
On 21. Jan 2012, at 23:26 , Greg Hennessy wrote: >>> >> There is one catch. >> FreeBSD does not want to break compatibility of old syntax and that is why >> i did not port the latest version of pf(4). > > Shades of the versioning/maintenance issues surrounding putting Perl in the > base way ba

RE: Getting Involved

2012-01-21 Thread Greg Hennessy
> > > There is one catch. > FreeBSD does not want to break compatibility of old syntax and that is why > i did not port the latest version of pf(4). Shades of the versioning/maintenance issues surrounding putting Perl in the base way back in the day. > What is there now makes it 'trivial' to go

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Bjoern A. Zeeb
The following reply was made to PR kern/163208; it has been noted by GNATS. From: "Bjoern A. Zeeb" To: =?iso-8859-1?Q?Tilman_Keskin=F6z?= Cc: Fabian Keil , bug-follo...@freebsd.org, freebsd-pf@freebsd.org Subject: Re: kern/163208: [pf] PF state key linking mismatch Date: Sat, 21 Jan 2012 21:01

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Bjoern A. Zeeb
On 21. Jan 2012, at 20:52 , Tilman Keskinöz wrote: > > On Jan 21, 2012, at 21:01 , Fabian Keil wrote: > >> Tilman Keskinöz wrote: >> >>> Same here. >>> >>> Also Fabian Keil reported this in >>> http://lists.freebsd.org/pipermail/freebsd-current/2011-July/025696.html >> >> This has been fixe

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Tilman Keskinöz
The following reply was made to PR kern/163208; it has been noted by GNATS. From: =?iso-8859-1?Q?Tilman_Keskin=F6z?= To: Fabian Keil Cc: bug-follo...@freebsd.org, freebsd-pf@freebsd.org Subject: Re: kern/163208: [pf] PF state key linking mismatch Date: Sat, 21 Jan 2012 21:52:09 +0100 On Jan 21

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Tilman Keskinöz
On Jan 21, 2012, at 21:01 , Fabian Keil wrote: > Tilman Keskinöz wrote: > >> Same here. >> >> Also Fabian Keil reported this in >> http://lists.freebsd.org/pipermail/freebsd-current/2011-July/025696.html > > This has been fixed in CURRENT shortly thereafter: > http://lists.freebsd.org/piperma

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Fabian Keil
The following reply was made to PR kern/163208; it has been noted by GNATS. From: Fabian Keil To: Tilman =?ISO-8859-1?Q?Keskin=F6z?= Cc: bug-follo...@freebsd.org, freebsd-pf@FreeBSD.org Subject: Re: kern/163208: [pf] PF state key linking mismatch Date: Sat, 21 Jan 2012 21:01:18 +0100 --Sig_/aS

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Fabian Keil
Tilman Keskinöz wrote: > Same here. > > Also Fabian Keil reported this in > http://lists.freebsd.org/pipermail/freebsd-current/2011-July/025696.html This has been fixed in CURRENT shortly thereafter: http://lists.freebsd.org/pipermail/freebsd-pf/2011-July/006199.html Maybe the fix hasn't been

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Tilman Keskinöz
The following reply was made to PR kern/163208; it has been noted by GNATS. From: =?iso-8859-1?Q?Tilman_Keskin=F6z?= To: bug-follo...@freebsd.org, freebsd-pf@FreeBSD.org Cc: freebsd-lis...@fabiankeil.de Subject: Re: kern/163208: [pf] PF state key linking mismatch Date: Sat, 21 Jan 2012 20:40:36 +

Re: kern/163208: [pf] PF state key linking mismatch

2012-01-21 Thread Tilman Keskinöz
Same here. Also Fabian Keil reported this in http://lists.freebsd.org/pipermail/freebsd-current/2011-July/025696.html Any ideas? ___ freebsd-pf@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail t

Re: Getting Involved

2012-01-21 Thread Ermal Luçi
On Fri, Jan 20, 2012 at 11:04 PM, Walt Elam wrote: > I would like to help with the development of the PF port for FreeBSD but am > not quite sure how to get involved. More specifically, I would like to help > get something ported over that accepts the new rule syntax since it becomes > increasing

Re: Maximum throughput ? limit?

2012-01-21 Thread Bartek W. aka Mastier
W dniu 19.01.2012 17:32, Adam PAPAI pisze: Bartek W. aka Mastier wrote: Indeed. The default maximum is 10 000 states as I remember. I.e. one of the main routers in my case. core quad. set limit { states 30, frags 1, src-nodes 10 } I had the states up to 25 but the frags an