On 12/16/05, Ben Beuchler <[EMAIL PROTECTED]> wrote:
> > > I just re-read the subject of your message...so, all the trouble started
> > > with an IOS upgrade? That sucks!
> >
> > I'm assuming that was the cause. I didn't notice it at the time, but
> > the dates match up.
>
> Interestingly, flow-receive works fine on another host on the same
> subnet. Same version of flow-tools, same router. So it seems less
> likely that it's actually an IOS problem.
>
> It looks like I've got something funky going on with my Gentoo box.
> I'm not running a host-based firewall, other network stuff on that box
> works fine, and the box is able to communicate directly with the
> router. I'm quite puzzled.
If you ran a sniffer like ethereal, or something similar on that machine,
you'd be able to see if the UDP flow packets are reaching the box.
Are you providing the right IP address to flow-receive for the source
of the UDP packets? If you have a complex network, or are using
something like the samplicator software, the packet may not have
the source IP you expect. Again, ethereal or another sniffer would
let you see what IP the UDP flow packets are coming from and
what port they're going to.
You may want to try running it with out setting remote ip, and should
also make sure that you don't have localip configured (as per the man page).
Other than that the only other thing I can think of would be to make sure
the owner of the flow-receive process has write permissions where
you're trying to save the flow data (and that the dir. exists etc.)
You could see if flow-capture works on the machine. It could also receive
and record the flow packets.
- VAB
--
V. Alex Brennen [EMAIL PROTECTED]
http://cryptnet.net/people/vab/
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
