Hi!

I'm testing ntop. After a somewhat difficult build process, I got a
compiled ntop to run. But that gave me a segmentation fault. Using gdb
I got this info:

(gdb) bt
#0  0x80f90d8 in pcap_findalldevs ()
#1  0x80eeb57 in pcap_lookupdev ()
#2  0x481a7f8f in initDevices (devices=0x0) at initialize.c:704
#3  0x804e3a4 in main (argc=1, argv=0x8047c78) at main.c:478
#4  0x804d88e in __start ()

Hm... Pcap, problems. Since this is a BSD/OS 4.2 box with 802.1q vlans
active, I substituted the libpcap.a just compiled with the system
supplied libcap. Now, ntop runs, but identifies all the traffic as
protocol "other". I'm not sure how to solve this. See:

#/sbin/ifconfig -a
exp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
        link type ether 0:90:27:f6:4e:2b mtu 1500 speed 100Mbps
        media auto (100baseTX full_duplex) status active
lo0: flags=8009<UP,LOOPBACK,MULTICAST>
        link type loop mtu 4352
        inet 127.0.0.1 netmask 255.0.0.0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
        link type 802.1Q 0:90:27:f6:4e:2b mtu 1500 speed 100Mbps
        vlan parent exp0 vid 3
        inet 172.16.1.7 netmask 255.255.248.0 broadcast 172.16.7.255
vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
        link type 802.1Q 0:90:27:f6:4e:2b mtu 1500 speed 100Mbps
        vlan parent exp0 vid 63
        inet 10.254.254.250 netmask 255.255.255.0 broadcast
10.254.254.255
vlan2: flags=0<>
        link type 802.1Q 0:0:0:0:0:0
vlan3: flags=0<>
        link type 802.1Q 0:0:0:0:0:0

Normally, vlan0 show dissected traffic. Exp0 shows vlan tagged
packets. Ntop is picking the right interface (vlan0).

Any idea?

Regards,

Roberto


_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to