From netramet-owner  Thu Jan  7 02:24:52 1999
Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id CAA08568
       for netramet-outgoing; Thu, 7 Jan 1999 02:20:22 +1300 (NZDT)
Received: from ultra3000.ifsc.sc.usp.br (uspfsc.ifqsc.sc.usp.br [143.107.228.1])
       by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with ESMTP id CAA08562
       for <[email protected]>; Thu, 7 Jan 1999 02:20:14 +1300 (NZDT)
Received: from ifsc.sc.usp.br (atm7.ifqsc.sc.usp.br [143.107.228.29])
       by ultra3000.ifsc.sc.usp.br (8.8.8/8.8.8) with ESMTP id LAA01713
       for <[email protected]>; Wed, 6 Jan 1999 11:24:26 -0200 (EDT)
Message-ID: <[email protected]>
Date: Wed, 06 Jan 1999 11:06:42 -0200
From: Marcelo Silva Freitas <[email protected]>
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: [email protected]
Subject: netramet on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

I compile fine NeTraMet43b in my FreeBSD-2.2.6 but when I try to run
       (./NeTraMet -i ed0)
appear the mesage:
       /dev/bpf0: device not configured
I put the line:
       pseudo-device  bpfilter  4
in my kernel config file and recompiled it ....
After, I try to run again and appear the same mesage.
There is only one bpf into /dev directory:
crw-------  1  root   wheel     23,     0   Aug  24  13:07  /dev/bpf0
Is that correct?
I have too the /usr/lib/libpcap.a  and  /usr/lib/libpcap.so.2.2  and the
LIBS set as -L/usr/lib.
Is there anything more that I must to do?
Thanks.



From netramet-owner  Fri Jan  8 09:21:17 1999
Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id JAA27770
       for netramet-outgoing; Fri, 8 Jan 1999 09:17:23 +1300 (NZDT)
Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79])
       by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with SMTP id JAA27758
       for <netramet@auckland>; Fri, 8 Jan 1999 09:17:20 +1300 (NZDT)
From: Nevil Brownlee <[email protected]>
To: [email protected]
Subject: Re: Packet loss on FreeBSD meters using BPF
Message-ID: <[email protected]>
Date: Fri, 8 Jan 1999 09:19:39 +1300 (New Zealand Daylight Time)
Priority: NORMAL
X-Mailer: Simeon for Win32 Version 4.1.4 Build (40)
X-Authentication: none
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: [email protected]
Precedence: bulk

--- Begin Forwarded Message ---

Subject: Re: Packet loss on FreeBSD meters using BPF
To: [email protected]
Date: Wed, 6 Jan 1999 21:53:36 +0100 (CET)
From: "Kurt Jaeger" <[email protected]>
Cc: [email protected], [email protected]
In-Reply-To: <[email protected]> from "Siegfried LOEFFLER" at Oct 30, 1998 09:32:27 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

> From: Daniel Ayers <[email protected]>
[...]
> I have done some testing with FreeBSD 2.2.7 and NeTraMet 4.2, 4.2.1 and
> 4.3b1.  My system also reported lost packets ("lsp=" in the "#Stats:" line
> in the flow files), so I decided to look through the NeTraMet and FreeBSD
> sources to find out what was behind that number.
[...]
> The short explaination is that BPF has a small internal buffer where
> incoming packets are stored.  On my system (FreeBSD 2.2.7) that buffer is
> 4k.  If the buffer is full, packets are discarded.
[...]
> I'm not well-versed in tuning FreeBSD (I'm more familiar with Linux), all
> I did was change line 99 of net/bpf.c from:
>
> #define BPF_BUFSIZE 4096
>
> to:
>
> #define BPF_BUFSIZE 40960
>
> Reconfigured, recompiled and it worked fine.

This apparently *is* user-configurable using a simple ioctl call:

Here a hint from libpcap-0.4:

      v = 32768;      /* XXX this should be a user-accessible hook */
      /* Ignore the return value - this is because the call fails on
       * BPF systems that don't have kernel malloc.  And if the call
       * fails, it's no big deal, we just continue to use the standard
       * buffer size.
       */
      (void) ioctl(fd, BIOCSBLEN, (caddr_t)&v);

Interestingly, the /usr/src/sys/net/bpf.c allows a maximum of
BPF_MAXBUFSIZE, as defined in bpf.h: 32 KB.

--
MfG/Best regards, Kurt Jaeger                                  21 years to go !
LF.net GmbH        [email protected]
Vor dem Lauch 23   fon +49 711 90074-23 Friedrich-Ebert-Str.1
D-70567 Stuttgart  fax +49 711 7289041  40210 Duesseldorf fon +49 211 179253-11
For Redmond: "nuke the site from orbit-- it's the only way to be sure."

--- End Forwarded Message ---


From netramet-owner  Fri Jan  8 11:16:37 1999
Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id LAA09713
       for netramet-outgoing; Fri, 8 Jan 1999 11:15:29 +1300 (NZDT)
Received: from mako.netlink.co.nz (mako.netlink.co.nz [202.20.93.10])
       by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with ESMTP id LAA09707;
       Fri, 8 Jan 1999 11:15:26 +1300 (NZDT)
Received: from angel.office.netlink.net.nz (angel.office.netlink.net.nz [203.97.244.128]) by mako.netlink.co.nz (8.8.6/8.8.6)
        with ESMTP id LAA09477; Fri, 8 Jan 1999 11:15:25 +1300 (NZDT)
Received: from lemon.office.netlink.net.nz ([203.97.244.37]) by angel.office.netlink.net.nz with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9)
       id Z4QGYV5Z; Fri, 8 Jan 1999 11:06:09 +1300
Date: Fri, 8 Jan 1999 11:15:24 +1300 (NZDT)
From: Daniel Ayers <[email protected]>
To: Nevil Brownlee <[email protected]>
cc: [email protected]
Subject: Re: Packet loss on FreeBSD meters using BPF
In-Reply-To: <[email protected]>
Message-ID: <Pine.GSO.4.00.9901081111560.20579-100000@lemon.office.netlink.net.nz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: [email protected]
Precedence: bulk


>> #define BPF_BUFSIZE 4096
>> to:
>> #define BPF_BUFSIZE 40960

> This apparently *is* user-configurable using a simple ioctl call:
> Here a hint from libpcap-0.4:
>        v = 32768;      /* XXX this should be a user-accessible hook */
>        (void) ioctl(fd, BIOCSBLEN, (caddr_t)&v);

Nevil, maybe you could include something of this nature in the UNIX
NeTraMet meter in cases where libpcap/BSD is being used.  This seems to be
necessary for the meter to work well.

I just took the quick/dumb/easy approach, I just added a zero to the
number that was already there! :-)

My meters work well, BTW.  4.3b5 on FreeBSD 2.2.8.

Daniel.

------------------------------------------------------------------------------
Daniel Ayers, B.Sc (Hons), M.Sc              Email: [email protected]
Network Security Specialist              DDI Phone: +64-4-916-5622
Netlink                                        Fax: +64-4-916-5300
23 Waring Taylor St, PO Box 5358            Mobile: +64-21-387-334
Wellington, New Zealand                        URL: http://www.netlink.co.nz


From netramet-owner  Wed Jan 27 23:09:29 1999
Received: by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id XAA16960
       for netramet-outgoing; Wed, 27 Jan 1999 23:04:31 +1300 (NZDT)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
       by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id XAA16951
       for <[email protected]>; Wed, 27 Jan 1999 23:04:16 +1300 (NZDT)
Received: from ccrle.nec.de (cologne.berlin.ccrle.nec.de [192.168.100.79])
       by yamato.ccrle.nec.de (8.8.8/3.6W980303HK) with ESMTP id LAA18354
       for <[email protected]>; Wed, 27 Jan 1999 11:07:09 +0100 (CET)
Message-ID: <[email protected]>
Date: Wed, 27 Jan 1999 11:03:55 +0100
From: Juergen Quittek <[email protected]>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: NeTraMet mailing list <[email protected]>
Subject: NeTraMet43b7: TCP_ATR
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

I tried to compile NeTraMet43b7 on Solaris 2.5.1 and on Linux
2.0.35 systems and observed a problem with the TCP_ATR flag.

In configure.in TCP_ATR is commented out, therefore it is not
set by the configure script (same as in NeTraMet422).
But flowhash.c does not compile with TCP_ATR being undefined.
I got the following error message:

gcc -g -I../../src/snmplib -I../../src/meter -I../../src/meter/tcpdump
-DLINUX  -DSIZEOF_LONG=4 -DNEW_ATR=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1
-DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_GETOPT_H=1
-DHAVE_MEMORY_H=1 -DHAVE_MALLOC_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMMOVE=1  -c
./../src/meter/flowhash.c
./../src/meter/flowhash.c: In function `count':
./../src/meter/flowhash.c:2339: `sfp' undeclared (first use this function)

However, everything works with TCP_ATR set.

   Juergen

--
Juergen Quittek    [email protected]   http://www.ccrle.nec.de
NEC Europe Ltd., C&C Research Laboratories  Tel: +49 30 254230-19
Hardenbergplatz 2, 10623 Berlin, Germany    Fax: +49 30 254230-99

From netramet-owner  Wed Jan 27 23:14:56 1999
Received: by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id XAA17434
       for netramet-outgoing; Wed, 27 Jan 1999 23:14:52 +1300 (NZDT)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
       by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id XAA17429
       for <[email protected]>; Wed, 27 Jan 1999 23:14:45 +1300 (NZDT)
Received: from ccrle.nec.de (cologne.berlin.ccrle.nec.de [192.168.100.79])
       by yamato.ccrle.nec.de (8.8.8/3.6W980303HK) with ESMTP id LAA18492
       for <[email protected]>; Wed, 27 Jan 1999 11:17:40 +0100 (CET)
Message-ID: <[email protected]>
Date: Wed, 27 Jan 1999 11:14:26 +0100
From: Juergen Quittek <[email protected]>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: NeTraMet mailing list <[email protected]>
Subject: NeTraMet for IPv6?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Is somebody already working on porting NeTraMet to IPv6?

The code already contains some preparations IPv6. What would be
major issues for the port, if we do not define new attributes?

   Juergen

--
Juergen Quittek    [email protected]   http://www.ccrle.nec.de
NEC Europe Ltd., C&C Research Laboratories  Tel: +49 30 254230-19
Hardenbergplatz 2, 10623 Berlin, Germany    Fax: +49 30 254230-99

From netramet-owner  Fri Jan 29 04:06:41 1999
Received: by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id EAA02676
       for netramet-outgoing; Fri, 29 Jan 1999 04:03:06 +1300 (NZDT)
Received: from beech.sucs.soton.ac.uk (beech.sucs.soton.ac.uk [152.78.129.138])
       by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id EAA02656
       for <[email protected]>; Fri, 29 Jan 1999 04:02:57 +1300 (NZDT)
Received: from cedar.sucs.soton.ac.uk (cedar.sucs.soton.ac.uk [152.78.128.92])
   by beech.sucs.soton.ac.uk (8.8.8/relay-02) with ESMTP id PAA21846
   for <[email protected]>; Thu, 28 Jan 1999 15:02:53 GMT
Received: from pogles.staff.sucs.soton.ac.uk (pogles.staff.sucs.soton.ac.uk [152.78.132.57])
   by cedar.sucs.soton.ac.uk (8.8.8/relay-02) with SMTP id OAA28586
   for <[email protected]>; Thu, 28 Jan 1999 14:49:11 GMT
From: Simon Lane <[email protected]>
To: [email protected]
Subject: NeTraMet OC3MON
Message-ID: <[email protected]>
Date: Thu, 28 Jan 1999 14:56:30 +0000 (GMT)
Priority: NORMAL
X-Mailer: Simeon for Win32 Version 4.1.4 Build (40)
X-Authentication: none
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: [email protected]
Precedence: bulk

Hello,

We have been runing NeTraMet very successfully for some time -
monitoring all our external traffic on an FDDI ring. However, we are
soon to migrate to an ATM external connection, and so won't have the
luxury of the FDDI ring.

I am therefore starting to look at the OC3MON version of the meter.
Ideally, I would like this on unix - for which I guess we use FreeBSD.

My understanding of the requirements is a little vague at present, so I
would be most greatful for some comments of the following points.

 http://moat.nlanr.net.OC3mon-monitors specifies what appears to be a
 relatively standard (but rack-mount) PC with two FORE PCA-200E ATM
 cards. I would probably use a free standing PC instead - presumably,
 the exact motherboard SCSI adapter etc are not critical?

 I assume that to build the meter, I install FreeBSD (and compilers
 etc) on the PC, then install the ATM Device Drivers as specified in
 the Coral-1.1 Installation Notes.

 Then I install Libpcap and NeTraMet in the usual way, compiling with
 GNU-C. Presumably also, the Configure scripts detect the ATM cards,
 and build the appropriate executables.

Would welcome your comments on how easy this process has been in
practice

Thank You

Simon Lane,
Computing Services,
University of Southampton.

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.