Date: Mon, 1 Mar 2004 23:09:25 +0300 From: Gleb Smirnoff <glebius@cell.sick.ru> To: fingers <fingers@fingers.co.za>, ng-netflow-users@lists.sourceforge.net Cc: freebsd-isp@freebsd.org Subject: Re: ng_netflow problems on 5.x Message-ID: <20040301200925.GA19700@cell.sick.ru> In-Reply-To: <20040301212119.U4576@snow.fingers.co.za> References: <20040301212119.U4576@snow.fingers.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 01, 2004 at 09:25:51PM +0200, fingers wrote: f> i seem to be having an identical problem on 2 5.2.1-R boxes, and f> ng_netflow (ng_netflow.c patched to 1.7, source taken from ports). You mean "netflow.c patched to 1.7" ? :) f> my previous (prior to patch) problem was a reboot after: f> f> <config> f> mkpeer fxp0: tee lower right f> name fxp0:lower tee0 f> connect fxp0: tee0: upper left f> </config> May be you mean "after connecting netflow node"? f> what am I missing? none of my config gives me any error. tcpdump on that f> port shows nothing. On which port? Is there any traffic flowing through fxp0? What does show "ngctl msg netflow0: info", "ngctl msg netflow0: ifinfo 0"? What does show "flowctl netflow0 show"? P.S. I suggest for us to move to ng-netflow-users@lists.sourceforge.net, and do not create unwanted traffic in freebsd-isp@freebsd.org. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040301200925.GA19700>