James Lay wrote: > On 7/8/08 6:17 AM, "Andrei-Florian Staicu" <[EMAIL PROTECTED]> wrote: > >> Hello all, >> >> I seem to have a small problem when running ntop 3.3.6, listening on >> interfaces other than eth0. >> For example: >> /usr/bin/ntop -u nobody --sticky-hosts --use-syslog=local6 -i eth0 >> will run for ages, while >> /usr/bin/ntop -u nobody --sticky-hosts --use-syslog=local6 -i eth1 >> on the same machine >> will run for 5-30 seconds and yield Segmentation fault. >> The same is true for another machine: on eth0 it works, on eth3 I get >> Segmentation fault. >> The machines have different hardware configurations; one of them is a >> Slackware 12.1 and the latter is a Slackware 12.0. >> >> Do you have any ideas on why this could happen? >> If you need any more information, such as the logs, please let me know >> and I will post them, although I don't see differences between the logs >> between the two runs. >> >> Thanks in advance. >> > Do interfaces eth1 or eth3 have a valid IP assigned to them? > Yes, each of the four interfaces (machine 1 - eth0, eth1, machine 2 - eth0, eth3) have several IP's assigned on virtual interfaces (eth1,eth1:1, a.s.o.). ntop correctly determines all these interfaces at startup and correctly displays the statistics in the time it runs, until the Segmentation fault error.
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
