Date: Thu, 1 Apr 2010 02:20:14 +0200 From: Luigi Rizzo <rizzo@iet.unipi.it> To: "Ass.Tec. Matik" <asstec@matik.com.br> Cc: freebsd-ipfw@freebsd.org Subject: Re: ipfw error in last stable version freebsd 8 Message-ID: <20100401002014.GA57424@onelab2.iet.unipi.it> In-Reply-To: <cd82fc45e95950cb83326ef7c1f28323.squirrel@wm.matik.com.br> References: <4BB24C86.3030709@hardonline.com.br> <20100331020943.GA47928@onelab2.iet.unipi.it> <20100331164302.GA55699@korolev-net.ru> <20100331170221.GB55010@onelab2.iet.unipi.it> <cd82fc45e95950cb83326ef7c1f28323.squirrel@wm.matik.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 31, 2010 at 03:47:49PM -0300, Ass.Tec. Matik wrote: > > > > it means that you are probably using a new kernel and an old /sbin/ipfw. > > The new ipfw/dummynet has a different kernel/userland API to accommodate > > some new features, and the kernel has a compatibility layer to translate > > requests back and forth between the two APIs. > > > > > where this is coming from: > > ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536 sys/netinet/ipfw/ip_fw_log.c Revision 200654 - (view) (annotate) - [select for diffs] Modified Thu Dec 17 23:11:16 2009 UTC (3 months, 1 week ago) by luigi Add some experimental code to log traffic with tcpdump, similar to pflog(4). To use the feature, just put the 'log' options on rules you are interested in, e.g. ipfw add 5000 count log .... and run tcpdump -ni ipfw0 ... net.inet.ip.fw.verbose=0 enables logging to ipfw0, net.inet.ip.fw.verbose=1 sends logging to syslog as before. cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100401002014.GA57424>