On Jan 13, "Luca Deri" wrote:
`your wish`
ifconfig -a
fwe0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
ether 02:30:1b:00:09:1a
ch 1 dma -1
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet6 fe80::230:1bff:feb1:8b6%bge0 prefixlen 64 scopeid 0x2
inet 128.32.155.122 netmask 0xffffff80 broadcast 128.32.155.127
ether 00:30:1b:b1:08:b6
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
nge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=13<RXCSUM,TXCSUM,VLAN_HWTAGGING>
ether 00:09:5b:22:d2:75
media: Ethernet autoselect (none)
status: no carrier
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
Thanks for looking at it.
Mike
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mike,
> can you please send the output of "ifconfig -a"?
>
> Thanks, Luca
>
> Mike Hunter wrote:
>
> | On Jan 13, "Stanley Hopcroft" wrote:
> |
> |> Dear Sir,
> |>
> |> Unfortunately I cannot speak about FreeBSD 5.x, but I have had good
> |> results with ntop 2.2.x on FreeBSD-4.x-RELEASE (albeit without
> |> sFlow or nFlow).
> |>
> |> I suggest that
> |>
> |> 1 You consider using a CVS ntop since ntop 2.3 is on the point of
> |> release (I still use 2.2/sans sFlow on 4.x-RELEASE but have
> |> successfully piloted 2.2.98)
> |>
> |>
> |> 2 The fault that your ntop log shows suggests the problem is in the
> |> configure process - I am suprised that it built, so possibly this
> |> is a stupid remark - not being able to locate the RRD shared
> |> object.
> |>
> |> 2.1 Does the rrd shared object exist on your system (dev branch
> |> rrds used _not_ to either build a .so or install it in a standard
> |> place) ?
> |>
> |> 2.2 If so, you may have to provide configure with its location.
> |>
> |> If you persist with 5.x you will probably do the eventual FreeBSD
> |> porter a favour as well as others like me that currently use 4.x
> |> and are wondering about the stability of the CURRENT branch (for my
> |> applications I will probably wait until the STABLE branch fork
> |> expect at 5.3-RELEASE).
> |
> |
> | Rats. Ntop built from cvs:
> |
> | (gdb) set args -w 3000 -W 3001 (gdb) run Starting program:
> | /usr/local/bin/ntop -w 3000 -W 3001 12/Jan/2004 15:13:16 ntop will
> | be started as user nobody 12/Jan/2004 15:13:16 ntop v.2.2.98 MT
> | (SSL) 12/Jan/2004 15:13:16 Configured on Jan 12 2004 14:59:49, built
> | on Jan 12 2004 15:06:28. 12/Jan/2004 15:13:16 Copyright 1998-2004 by
> | Luca Deri <[EMAIL PROTECTED]> 12/Jan/2004 15:13:16 Get the freshest ntop
> | from http://www.ntop.org/ 12/Jan/2004 15:13:16 Initializing ntop
> |
> | Program received signal SIGBUS, Bus error. 0x2806add0 in
> | rlock_release () from /libexec/ld-elf.so.1 (gdb) bt #0 0x2806add0 in
> | rlock_release () from /libexec/ld-elf.so.1 #1 0x28067a24 in
> | _rtld_bind () from /libexec/ld-elf.so.1 #2 0x280673a1 in
> | _rtld_bind_start () from /libexec/ld-elf.so.1 #3 0x2811f621 in
> | getLocalHostAddressv6 (addrs=0x0, device=0x80ca7f0 "bge0") at
> | util.c:423 #4 0x28108195 in addDevice (deviceName=0x293cb6c0 "bge0",
> | deviceDescr=0x293cb6c0 "bge0") at initialize.c:1392 #5 0x28108b6d in
> | initDevices (devices=0xbfbfe750 "BIOCSETIF: any: Device not
> | configured") at initialize.c:1589 #6 0x2810172a in initNtop
> | (devices=0x0) at globals-core.c:553 #7 0x0804c5a4 in main (argc=5,
> | argv=0xbfbfebf4) at main.c:1182 #8 0x0804ac32 in _start ()
> |
> | Freebsd is 5.1-CURRENT FreeBSD 5.1-CURRENT #4: Thu Nov 13 20:10:38
> | PST 2003
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
