Hi, Thanks for the great ntop software! I have a problem that appears to be cause by a bug in the software. The problem is that ntop gets the params of two interfaces wrong, causing ntop to report their type as "No link-layer encapsulation". As a result of this the misdetected interfaces aren't monitored. See the attached screenshot. Please note that -- apart from the misdetected interface type -- the MTU is misreported as well for these interfaces.
I use ntop-3.2 on Gentoo Linux with kernel 2.6.17.
This machine is a firewall/router and has the following interfaces:
# ifconfig -a
dmz Link encap:Ethernet HWaddr 00:40:F4:67:44:96
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:302126 errors:0 dropped:0 overruns:0 frame:0
TX packets:180958 errors:0 dropped:0 overruns:0 carrier:0
collisions:74882 txqueuelen:1000
RX bytes:385384713 (367.5 Mb) TX bytes:23851290 (22.7 Mb)
Interrupt:10 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5674 errors:0 dropped:0 overruns:0 frame:0
TX packets:5674 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:735176 (717.9 Kb) TX bytes:735176 (717.9 Kb)
loc Link encap:Ethernet HWaddr 00:40:F4:67:44:97
inet addr:192.168.3.2 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1412350 errors:0 dropped:0 overruns:0 frame:0
TX packets:2038610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:127834281 (121.9 Mb) TX bytes:1772438755 (1690.3 Mb)
Interrupt:12 Base address:0x2000
net Link encap:Ethernet HWaddr 00:40:F4:67:44:95
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1173613 errors:0 dropped:0 overruns:0 frame:0
TX packets:731859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1201718037 (1146.0 Mb) TX bytes:76561504 (73.0 Mb)
Interrupt:11 Base address:0x6000
Ntop is started with the following arguments on the commandline:
-u ntop -P /var/lib/ntop -i lo,dmz,loc,net -r 20 -w 3000 -M --no-fc
--skip-version-check --w3c
Apart from the misdetection, ntop appears to function normally.
Could it be that ntop mixes the device names 'lo' and 'loc'?
If you need any other information, please let me know.
Regards,
Toon.
screenshot-ntop-Global-Traffic-Statistics.png
Description: PNG image
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
