Ntop 4.1.0_3 v2 no longer open

vladick0732

Hi friends!

After reading the previous posts, I removed a tick in the position of "Track all traffic" (I have it was), in Diagnostics: ntop Settings, and it worked. :)
Prior to that upgraded to the new version.

pf5432.jpg_thumb

jimp

I checked in a better fix that respects that option now. It should be OK no matter how that's set.

josekym

Hello Jimp,

Tried v2.2 update and the problem persists… :-[

However, I also noted vladick0732's observation and everything runs fine now, except I do not have IPv6 traffic stats on the reports now (as expected).

Thanks for the efforts! ;)

r5a

Still getting the issue as well

4.1.0_3 v2.2

can't access 3000, timed out.

edit: i checked the file above

Edit the file ntop.sh in /usr/local/etc/rc.d and add -4 to the parameter list of rc_start()
heres what i have

#!/bin/sh
# This file was automatically generated
# by the pfSense service handler.

rc_start() {
	/usr/local/bin/ntop -i em0 -u root -d -4 -6 -M -x 8102 -X 8192 &
}

rc_stop() {
	/usr/bin/killall ntop
}

case $1 in
	start)
		rc_start
		;;
	stop)
		rc_stop
		;;
	restart)
		rc_stop
		rc_start
		;;
esac

reboot service and i do a netstat -an and i see this


$ netstat -an
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address          Foreign Address       (state)
tcp6       0      0 *.3000                 *.*                    LISTEN
tcp6       0      0 *.53                   *.*                    LISTEN
tcp4       0      0 *.53                   *.*                    LISTEN
tcp4       0      0 *.80                   *.*                    LISTEN
tcp4       0      0 *.443                  *.*                    LISTEN
tcp4       0      0 *.22                   *.*                    LISTEN
tcp6       0      0 *.22                   *.*                    LISTEN

not sure why its not taking ipv4 on its listen interface. tried removing reinstalling the package

jimp

Apparently because that makes it bind to ipv6 only… I removed that track option from the GUI in the new version and forced -4. It appears they broke their own options, so nothing we can do until ntop releases a fixed version. In the meantime using only -4 will make it listen as expected.

It may not capture ipv6 traffic in that case (it might... haven't tried it) but it'll have to do for now.

r5a

Thanks jimp. I'll edit my rc.d file now and report back.

I was the guy who asked to update to the latest earlier, sorry about causing headaches!

jimp

It's ok, couldn't predict that they'd break it in this way. :-)

r5a

Works fine.

I think like 1% of the world is using IPv6

As a request, wouldn't it make sense to put the nTop in Diganostics to Status as nTop GUI

Then have ntop settings in services?

A little more neat and organized.

jimp

We're pushing for ipv6 support in pfSense 2.1. The number of people using it is growing every day, so it's not something we can toss aside :-)

Not sure about moving the menu entries around. Status does probably make more sense for both of them, or even services, but the case for Diagnostics is sort of there as well.

josekym

Hello jimp,

I just pushed ntop v2.3 update today and all runs well now without extra tweaking, defaulted to tcp4 listening. On the IP prefs, it indicates support for both IP v4 and v6.

Thanks and have a nice day. :)