You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running softflowd on pfsense 21.02.2-RELEASE on a netgate SG-1100 is failing to send any netflow traffic and is producing a segfault - see below (i've redacted the IPs)
There's no netflow traffic being sent by the firewall, and hence no traffic being received by the collector.
I'm not sure where to go next in terms of digging into the problem - any suggestions?
FYI I had first raised this with netgate who suggested I follow up with the maintainer of the package - see issue reported here: https://redmine.pfsense.org/issues/10436 . There's a separate support ticket where I have just been told:
I checked with our development team on this issue. Unfortunately Netflow is a third party package that we only "wrap up" to provide to pfSense. As such, you will want to follow up with the package maintainer as there isn't much we can do here to provide assistance for this package as it is unsupported. The best place to communicate is via the redmine and directly with the maintainer of the package.
I ran into a similar issue running this command: softflowd -i eth0 -n collector_host:2055 -L 3 -m 8192 -v 10 -P udp -D
I never got flow to "collector_host" until I removed the -D. softflowd -i eth0 -n collector_host:2055 -L 3 -m 8192 -v 10 -P udp
Not sure if that is your issue but took me a bit to figure out so thought I'd share. Not sure about your core.
@natemccallum : Interesting. I've tried it with and without and doesn’t seem to make a difference, except that i can't see debug output! Thanks anyway.
Running softflowd on pfsense 21.02.2-RELEASE on a netgate SG-1100 is failing to send any netflow traffic and is producing a segfault - see below (i've redacted the IPs)
There's no netflow traffic being sent by the firewall, and hence no traffic being received by the collector.
I'm not sure where to go next in terms of digging into the problem - any suggestions?
FYI I had first raised this with netgate who suggested I follow up with the maintainer of the package - see issue reported here: https://redmine.pfsense.org/issues/10436 . There's a separate support ticket where I have just been told:
The text was updated successfully, but these errors were encountered: