can someone please so an ebuild and insert it into portage. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 47111 [details] ebuild for ntop-3.1 adapt from the ebuild for ntop 3.0 This is only the ebuild for ntop-3.0 modified for ntop-3.1 I change only a lot variables. Sorry for my bad English. Truzzone
I got the following error running this: frog ns-2.27 # ntop Wed Jan 12 20:02:03 2005 Initializing gdbm databases Wed Jan 12 20:02:03 2005 ntop will be started as user nobody Wed Jan 12 20:02:03 2005 ntop v.3.1 MT (SSL) Wed Jan 12 20:02:03 2005 Configured on Jan 12 2005 19:58:53, built on Jan 12 2005 19:59:41. Wed Jan 12 20:02:03 2005 Copyright 1998-2004 by Luca Deri <deri@ntop.org> Wed Jan 12 20:02:03 2005 Get the freshest ntop from http://www.ntop.org/ Wed Jan 12 20:02:03 2005 Initializing ntop Wed Jan 12 20:02:03 2005 No default device configured. Using eth0 Wed Jan 12 20:02:03 2005 Checking eth0 for additional devices Wed Jan 12 20:02:03 2005 Resetting traffic statistics for device eth0 Wed Jan 12 20:02:03 2005 DLT: Device 0 [eth0] is 1, mtu 1514, header 14 Segmentation fault frog ns-2.27 # /etc/init.d/ntop start * Starting ntop... /sbin/runscript.sh: line 532: 18519 Segmentation fault start-stop-daemon --start --quiet --exec /usr/bin/ntop -- -d -L ${NTOP_OPTS} >/dev/null frog ns-2.27 # emerge info Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r2 i686) ================================================================= System uname: 2.6.10-gentoo-r2 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 08:06:09)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.90.0.1.1-r3 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-pipe" CHOST="i686-pc-linux-gnu"
Created attachment 48541 [details] new version use i18n to support multi-language add a patch to support openvpn tunnel
Created attachment 48542 [details, diff] Patch to suppport ntop 3.1 openvpn tun
Version 3.1 commited masked. I had the program giving SEGV when starting. To test please: add =net-analyzer/ntop-3.1 to your /etc/portage/package.unmask file env CFLAGS=-g FEATURES="maketest collision-detect strict keepwork nostrip" ACCEPT_KEYWORDS=~x86 emerge ntop cd /var/tmp/portage/ntop-3.1/work/ntop-3.1 ulimit -c unlimited .libs/ntop -L -u ntop -P /var/lib/ntop --interface eth0 gdb .libs/ntop core # try to see what is causing it. I've run out of time. Francisco, your patch reguarding MTU size. I've included it but I have the following questions: would ntop have selected a MTU otherwise? is the MTU always 1500 (ethernet limit I assume) If this is to fix for openvpn - should openvpn be fixed? Gives warning in the compile that I didn't get fixed: xmldumpPlugin.c:50:2: warning: #warning xmldumpPlugin.c:51:2: warning: #warning =========================================================== xmldumpPlugin.c:52:2: warning: #warning xmldumpPlugin.c:53:2: warning: #warning Missing header files, disabling xmldump plugin xmldumpPlugin.c:54:2: warning: #warning xmldumpPlugin.c:55:2: warning: #warning FOR MOST USERS THIS IS NOT A PROBLEM xmldumpPlugin.c:56:2: warning: #warning ntop will build and run just fine... xmldumpPlugin.c:57:2: warning: #warning xmldumpPlugin.c:58:2: warning: #warning Why? xmldumpPlugin.c:59:2: warning: #warning xmldumpPlugin.c:61:2: warning: #warning glibconfig.h unavailable xmldumpPlugin.c:64:2: warning: #warning glib.h unavailable xmldumpPlugin.c:67:2: warning: #warning gdome.h unavailable xmldumpPlugin.c:70:2: warning: #warning xmlversion.h unavailable xmldumpPlugin.c:75:2: warning: #warning xmldumpPlugin.c:76:2: warning: #warning =========================================================== xmldumpPlugin.c:77:2: warning: #warning
When patch is not installed, show this: Mon Jan 17 09:32:12 2005 Checking tun1 for additional devices Mon Jan 17 09:32:12 2005 Resetting traffic statistics for device tun1 Mon Jan 17 09:32:12 2005 **WARNING** DLT: Device 0 [tun1] MTU value unknown Mon Jan 17 09:32:12 2005 **WARNING** DLT: Processing continues OK Mon Jan 17 09:32:12 2005 DLT: Device 0 [tun1] is 113, mtu 65355, header 0 the mtu is not calculed for this type of device Also need patch in kernel to device tun make correct type see: http://bugs.gentoo.org/show_bug.cgi?id=78016 ntop forms a fixed MTU by each type of device (that I have understood) in source code OPenvpn not cat fixed, only ntop and kernel
