From netramet-owner  Tue Apr  2 16:17:34 1996
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) id QAA18435 for netramet-outgoing; Tue, 2 Apr 1996 16:14:24 +1200 (NZST)
Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) with SMTP id QAA18430 for <[email protected]>; Tue, 2 Apr 1996 16:14:19 +1200 (NZST)
Received: from bha.oz.au (daemon@localhost) by online.tmx.com.au (8.6.5/8.6.5) with MHSnet id OAA23780 for [email protected]; Tue, 2 Apr 1996 14:14:13 +1000
Received: from owl by wurrup (AIX 3.2/UCB 5.64/4.03)
         id AA35517; Tue, 2 Apr 1996 14:10:25 +1000
Date: Tue, 2 Apr 1996 14:10:25 +1000
Message-Id: <9604020410.AA35517@wurrup>
X-Sender: mrm@rabbit
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: [email protected]
From: Mark Myatt <[email protected]>
Subject: NetraMet performance
Sender: [email protected]
Precedence: bulk

Hello,

I have just recently found out about the Netramet product and am very
interested in it.  I have read in the reference manual that a 386SX PC (25MHz)
can process about up to 1250 packets / second sustained.  I was wondering
what that equates to in a typical ethernet LAN using solely IP packets ie.
could all packets be tracked on a LAN running 10 Mbps ethernet?  What about
100 Mbps ethernet?  Also, what about the performance of modern day processors
such as a Pentium running Linux?

Any help would be much appreciated.

Mark Myatt.

---------------------------------------------------------------------------
Mark Myatt               59-69 Shafston Ave          Phone: +61-7-3258-4531
Systems Engineer         Kangaroo Point QLD 4169       Fax: +61-7-3258-4557
BHA Computer Pty Ltd     Australia                  E-mail: [email protected]
---------------------------------------------------------------------------



From netramet-owner  Fri Apr  5 23:56:16 1996
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) id XAA20124 for netramet-outgoing; Fri, 5 Apr 1996 23:51:59 +1200 (NZST)
Received: from tuminfo2.informatik.tu-muenchen.de ([email protected] [131.159.0.81]) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) with ESMTP id XAA20041; Fri, 5 Apr 1996 23:46:47 +1200 (NZST)
Received: from hphalle0.informatik.tu-muenchen.de ([131.159.4.1]) by tuminfo2.informatik.tu-muenchen.de with ESMTP id <26932-3>; Fri, 5 Apr 1996 13:46:41 +0200
Received: from goeb.modem.informatik.tu-muenchen.de ([172.16.1.68]) by hphalle0.informatik.tu-muenchen.de with SMTP id <397023-222>; Fri, 5 Apr 1996 13:46:23 +0100
Received: by goeb.modem.informatik.tu-muenchen.de with Microsoft Mail
       id <[email protected]>; Fri, 5 Apr 1996 13:34:49 +-200
Message-ID: <[email protected]>
From: Goeb Michael <[email protected]>
To: "'Mailing list NeTraMet'" <[email protected]>,
       "'Mailing list RTFM'" <[email protected]>
Subject: NeTraMet for Token Ring
Date:   Fri, 5 Apr 1996 13:34:05 +-200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Hello,

I'm currently using NeTraMet 3.3 on Ethernetsegments
quite successfuly.
My major Problem is that we have a large token-ring backbone.
I now want to ask if anyone has modified NeTraMet
to work with token-ring ?

Michael


From netramet-owner  Tue Apr  9 12:05:19 1996
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) id MAA10565 for netramet-outgoing; Tue, 9 Apr 1996 12:02:10 +1200 (NZST)
Received: from homer.is.com.fj (homer.is.com.fj [202.62.124.238]) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) with ESMTP id MAA10560 for <[email protected]>; Tue, 9 Apr 1996 12:02:07 +1200 (NZST)
Received: from it.is.com.fj (it.is.com.fj [202.62.124.233]) by homer.is.com.fj (8.7.1/8.7.1) with SMTP id MAA10838 for <[email protected]>; Tue, 9 Apr 1996 12:02:04 +1200 (GMT-12)
Date: Tue, 9 Apr 1996 12:02:04 +1200 (GMT-12)
Message-Id: <[email protected]>
X-Sender: [email protected]
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: [email protected]
From: Ilaitia Tuisawau <[email protected]>
Subject: Reboot System
Sender: [email protected]
Precedence: bulk

Hello All,

I have a rather trivial question, but would appreciate all feedback. What is
the best way to add NeMaC to the /etc/rc file so that it is restarted
automatically after a system reboot?

I have added both NeTraMet and NeMaC (with all required parameters) to the
/etc/rc file. After a reboot, NeTraMet starts up as expected, but NeMaC has
a problem finding the mib.txt file. This is even after putting it in the
root path, environment (MIBTXT=../mib.txt), and even doing a cd to the
netramet sub-directory.

All responses are appreciated.

Cheers,
Ilaitia


From netramet-owner  Thu Apr 11 05:01:31 1996
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) id EAA18974 for netramet-outgoing; Thu, 11 Apr 1996 04:59:09 +1200 (NZST)
Received: from exodo.upr.clu.edu (exodo.UPR.CLU.EDU [136.145.57.24]) by mailhost.auckland.ac.nz (8.7.3/8.7.3-ua) with SMTP id EAA18959 for <[email protected]>; Thu, 11 Apr 1996 04:58:51 +1200 (NZST)
Received: from anibalpc.upr.clu.edu by exodo.upr.clu.edu (SMI-8.6/SMI-SVR4)
       id MAA15847; Wed, 10 Apr 1996 12:59:06 +0400
Received: by anibalpc.upr.clu.edu with Microsoft Mail
       id <[email protected]>; Wed, 10 Apr 1996 13:00:53 -0300
Message-ID: <[email protected]>
From: Anibal Morales <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: Testing
Date: Wed, 10 Apr 1996 13:00:52 -0300
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Hello... anybody here...

Anibal

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.