Bug#658677: [kfreebsd-image-9] Please enable pflog device by default

2012-02-10 Thread Dererk
On 10/02/12 16:57, Robert Millan wrote: > 2012/2/6, Dererk : >> That was easy! :-) >> As you mention, removing the patch did work as expected and nicely! Thanks! >> >> I'll let tcpdump guys know about this so we can, altogether when this >> issue is solved, this quite relevant kbsd feature working

Bug#658677: [kfreebsd-image-9] Please enable pflog device by default

2012-02-10 Thread Dererk
On 10/02/12 16:57, Robert Millan wrote: > 2012/2/6, Dererk : >> That was easy! :-) >> As you mention, removing the patch did work as expected and nicely! Thanks! >> >> I'll let tcpdump guys know about this so we can, altogether when this >> issue is solved, this quite relevant kbsd feature working

Bug#658677: [kfreebsd-image-9] Please enable pflog device by default

2012-02-10 Thread Robert Millan
2012/2/6, Dererk : > That was easy! :-) > As you mention, removing the patch did work as expected and nicely! Thanks! > > I'll let tcpdump guys know about this so we can, altogether when this > issue is solved, this quite relevant kbsd feature working in time for > wheezy. So what else is needed?

Bug#658677: [kfreebsd-image-9] Please enable pflog device by default

2012-02-06 Thread Dererk
On 06/02/12 05:04, Petr Salinger wrote: >> Petr, since you're listed as patch author, do you know if this feature >> worked in the past? > > tcpdump worked somehow, but I do not remember exactly, > it is 4 years ago, see #448695. > > Probably, the used to need . > It is not needed any longer. It l

Bug#658677: [kfreebsd-image-9] Please enable pflog device by default

2012-02-06 Thread Petr Salinger
Petr, since you're listed as patch author, do you know if this feature worked in the past? tcpdump worked somehow, but I do not remember exactly, it is 4 years ago, see #448695. Probably, the used to need . It is not needed any longer. It looks like the proper fix is just to discard 50_kfreeb