From netramet-owner  Wed Feb  4 16:32:35 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id QAA22441 for netramet-outgoing; Wed, 4 Feb 1998 16:27:48 +1300 (NZDT)
Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with SMTP id QAA22427 for <[email protected]>; Wed, 4 Feb 1998 16:27:44 +1300 (NZDT)
Received: from cc-pc16 by cc-server9 with SMTP(PP);
         Wed, 4 Feb 1998 16:27:35 +1300
Received: by localhost with Microsoft MAPI; Wed, 4 Feb 1998 16:29:49 +1300
Message-ID: <[email protected]>
From: Glen Eustace <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: Syntax change between releases ?
Date: Wed, 4 Feb 1998 16:29:46 +1300
Organization: Computing Services - Massey University
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

I am trying to upgrade from 3.4 to 4.1, the following rules work
fine on 3.4 but I get error on 4.1, what do I change and to what
to get the required result.

ip_pkt:
 SourcePeerAddress & 255.255.0.0 = 130.123.0.0         : GotoAct,
which_net;
 Null & 0 = 0                                          : Retry, 0;
which_net:
 SourcePeerAddress & 255.255.255.255 = 0               : PushPktto,
Next;
 DestPeerAddress & 192.0.0.0 = 192.0.0.0               : GotoAct,
MU_C;
 DestPeerAddress & 192.0.0.0 = 128.0.0.0               : GotoAct,
MU_B;
 DestPeerAddress & 192.0.0.0 = 64.0.0.0                : GotoAct,
MU_A;
 DestPeerAddress & 192.0.0.0 = 0.0.0.0                 : GotoAct,
MU_A;
MU_C:
 DestPeerAddress & 255.255.255.0 = 0                   : PushPkttoAct,
cnt_pkt;
MU_B:
 DestPeerAddress & 255.255.0.0 = 0                     : PushPkttoAct,
cnt_pkt;
MU_A:
 DestPeerAddress & 255.0.0.0 = 0                       : PushPkttoAct,
cnt_pkt;
cnt_pkt:
 Null & 0 = 0                                          : Count, 0

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Glen Eustace, Systems Engineer - Networking, Computing Services,
Massey University, Private Bag 11222, Palmerston North, N.Z.
Ph: +64 6 350 5161, Fax: +64 6 350 5607, Mobile +64 25 500 321
Pvt Ph: +64 6 356 2562


From netramet-owner  Mon Feb  9 11:23:03 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id LAA23892 for netramet-outgoing; Mon, 9 Feb 1998 11:18:23 +1300 (NZDT)
Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with SMTP id LAA23874 for <[email protected]>; Mon, 9 Feb 1998 11:18:16 +1300 (NZDT)
Received: from cc-pc16 by cc-server9 with SMTP(PP);
         Mon, 9 Feb 1998 11:17:59 +1300
Received: by localhost with Microsoft MAPI; Mon, 9 Feb 1998 11:19:42 +1300
Message-ID: <[email protected]>
From: Glen Eustace <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: Syntax change between releases
Date: Mon, 9 Feb 1998 11:19:37 +1300
Organization: Computing Services - Massey University
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Last week, I posted a small rule file that is currently working fine
with v3.4 of NeMaC but which has syntax errors with 4.1.  I couldn't
recall the exact wording of the error as the server I am using to get
4.1 sorted out had lost a disk and was unavailable.  The disk has now
been replaced and this is the error. NB: This rule file is fine with
3.4

NeMaC: NeTraMet Manager & Controller V4.1
/SF/its-admin1-is/usr/local/netramet/cc-ntm3.rules   36:
 DestPeerAddress & 255.255.255.0 = 0                   : PushPkttoAct, cnt_pkt;
Possible flow into rule: must GotoAct !!!
/SF/its-admin1-is/usr/local/netramet/cc-ntm3.rules   38:
 DestPeerAddress & 255.255.0.0 = 0                     : PushPkttoAct, cnt_pkt;
Possible flow into rule: must GotoAct !!!
/SF/its-admin1-is/usr/local/netramet/cc-ntm3.rules   40:
 DestPeerAddress & 255.0.0.0 = 0                       : PushPkttoAct, cnt_pkt;
Possible flow into rule: must GotoAct !!!

3 errors in rule file(s)
/SF/its-admin1-is/usr/local/netramet/cc-ntm3.rules

I would appreciate someone telling me what I must change.

Thanks.


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Glen Eustace, Systems Engineer - Networking, Computing Services,
Massey University, Private Bag 11222, Palmerston North, N.Z.
Ph: +64 6 350 5161, Fax: +64 6 350 5607, Mobile +64 25 500 321
Pvt Ph: +64 6 356 2562


From netramet-owner  Wed Feb 11 16:18:01 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id QAA04924 for netramet-outgoing; Wed, 11 Feb 1998 16:12:17 +1300 (NZDT)
Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with SMTP id QAA04919 for <[email protected]>; Wed, 11 Feb 1998 16:12:14 +1300 (NZDT)
Received: from cc-pc16 by cc-server9 with SMTP(PP);
         Wed, 11 Feb 1998 16:11:17 +1300
Received: by localhost with Microsoft MAPI; Wed, 11 Feb 1998 16:13:11 +1300
Message-ID: <[email protected]>
From: Glen Eustace <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: Problems with ntm32
Date: Wed, 11 Feb 1998 16:13:09 +1300
Organization: Computing Services - Massey University
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Through a process of trial and error, I have concluded that the cmd
PushPktto, has changed between 3.4 and 4.1, by changing it to
PushPkttoAct I believe the outcome is the same and I don't get any
error reported from NeMaC.

Well so much for that, I can not get NeMaC to talk to ntm32.  NTM32
reports the error

AAEB 1 0
.\snmplib\snmpagnt.c (411)

And NeMac says that the community doesn't have write access to the
meter.  I am starting NTM32 as follows

ntm32 -h96 -f10000 -p2000 -w xxxx -r xxxx

and I run NeMac

/NeMaC -r rules 130.123.128.197 xxxx

I have compiled NeMaC under Dec Unix on an alpha, if this helps.

Thanks.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Glen Eustace, Systems Engineer - Networking, Computing Services,
Massey University, Private Bag 11222, Palmerston North, N.Z.
Ph: +64 6 350 5161, Fax: +64 6 350 5607, Mobile +64 25 500 321
Pvt Ph: +64 6 356 2562


From netramet-owner  Thu Feb 12 11:20:00 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id LAA14412 for netramet-outgoing; Thu, 12 Feb 1998 11:18:45 +1300 (NZDT)
Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with SMTP id LAA14407 for <[email protected]>; Thu, 12 Feb 1998 11:18:43 +1300 (NZDT)
Received: from cc-pc16 by cc-server9 with SMTP(PP);
         Thu, 12 Feb 1998 11:18:31 +1300
Received: by localhost with Microsoft MAPI; Thu, 12 Feb 1998 11:20:47 +1300
Message-ID: <[email protected]>
From: Glen Eustace <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: RE: Problems with ntm32
Date: Thu, 12 Feb 1998 11:20:38 +1300
Organization: Computing Services - Massey University
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

On Thursday, February 12, 1998 1:17 AM, Marcelo Quintino da Silva
[SMTP:[email protected]] wrote:
>       I have the same problem......  ;-(

> > Well so much for that, I can not get NeMaC to talk to ntm32.  NTM32
> >
> > reports the error
> >
> > AAEB 1 0
> > ..\snmplib\snmpagnt.c (411)
> >
> > And NeMac says that the community doesn't have write access to the
> > meter.  I am starting NTM32 as follows
> >
> > ntm32 -h96 -f10000 -p2000 -w xxxx -r xxxx
> >
> > and I run NeMac
> >
> > ./NeMaC -r rules 130.123.128.197 xxxx
> >
> > I have compiled NeMaC under Dec Unix on an alpha, if this helps.

I have tried compiling NeMaC under Solaris, to see whether this problem
is related to the NeMaC OS or 64bit architecture.  It would appear that
it isn't as the same problem re-occurs.



From netramet-owner  Fri Feb 13 10:07:51 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id KAA22155 for netramet-outgoing; Fri, 13 Feb 1998 10:01:45 +1300 (NZDT)
Received: from lemon.netlink.co.nz (lemon.netlink.co.nz [203.97.244.37]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with ESMTP id KAA22141 for <[email protected]>; Fri, 13 Feb 1998 10:01:41 +1300 (NZDT)
Received: from netlink.co.nz (localhost [127.0.0.1])
       by lemon.netlink.co.nz (8.8.8/8.8.8) with ESMTP id KAA15039
       for <[email protected]>; Fri, 13 Feb 1998 10:01:40 +1300 (NZDT)
Message-ID: <[email protected]>
Date: Fri, 13 Feb 1998 10:01:40 +1300
From: Milton Ngan <[email protected]>
Organization: NetLink New Zealand
X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: [email protected]
Subject: SMC PCI Cards..
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

I am running 32bit NeTraMet 4.1 with a SMC9432TX Fast Ethernet PCI card.
Unfortunately it seems the packet driver from SMC or the card does not
support promiscuous mode.

Does anyone have any recommendations for FE PCI cards that work, or a
packet driver that will work?

Cheers

M.



From netramet-owner  Fri Feb 13 11:11:41 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id LAA00886 for netramet-outgoing; Fri, 13 Feb 1998 11:11:03 +1300 (NZDT)
Received: from brolga.cc.uq.edu.au ([email protected] [130.102.128.5]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with ESMTP id LAA00858 for <[email protected]>; Fri, 13 Feb 1998 11:10:55 +1300 (NZDT)
Received: from brolga.cc.uq.edu.au ([email protected] [130.102.128.5])
       by brolga.cc.uq.edu.au (8.8.6/8.8.7) with SMTP id IAA12193;
       Fri, 13 Feb 1998 08:10:28 +1000 (EST)
Message-Id: <[email protected]>
X-Authentication-Warning: brolga.cc.uq.edu.au: [email protected] [130.102.128.5] didn't use HELO protocol
To: Milton Ngan <[email protected]>
Subject: Re: SMC PCI Cards..
cc: [email protected]
In-reply-to: Your message of "Fri, 13 Feb 1998 10:01:40 +1300."
            <[email protected]>
Date: Fri, 13 Feb 1998 08:10:27 +1000
From: David Vu <[email protected]>
Sender: [email protected]
Precedence: bulk

Milton,

If this uses the DEC FastEthernet chip dc21x4x then it might work
with the packet driver from crynwr:

ftp://ftp.crynwr.com/drivers/dc21x4pk_11_0.zip

We have used Acton EN1207TX, D-Link DFE500, and 3com FastEtherlink
XL reliably for a while.

Cheers,

David.

>>>>I am running 32bit NeTraMet 4.1 with a SMC9432TX Fast Ethernet PCI card.
Unfortunately it seems the packet driver from SMC or the card does not
support promiscuous mode.

Does anyone have any recommendations for FE PCI cards that work, or a
packet driver that will work?

From netramet-owner  Fri Feb 13 13:19:24 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id NAA17775 for netramet-outgoing; Fri, 13 Feb 1998 13:17:13 +1300 (NZDT)
Received: from mail.telstra.com.au (mail.telstra.com.au [192.148.160.16]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with ESMTP id NAA17764 for <[email protected]>; Fri, 13 Feb 1998 13:17:09 +1300 (NZDT)
Received: (from uucp@localhost) by mail.telstra.com.au (8.8.2/8.6.9) id LAA05834 for <[email protected]>; Fri, 13 Feb 1998 11:16:34 +1100 (EST)
Received: from mail-gw.fwall.telstra.com.au(192.148.147.16)
via SMTP by mail.telstra.com.au, id smtpd005754; Fri Feb 13 11:16:08 1998
Received: (from uucp@localhost) by mail-gw.fwall.telstra.com.au (8.8.2/8.6.9) id LAA18110 for <[email protected]>; Fri, 13 Feb 1998 11:16:07 +1100 (EST)
Received: from cdn-mail.dn.itg.telecom.com.au(144.135.109.134), claiming to be "cdn-mail.telecom.com.au"
via SMTP by mail-gw.fwall.telstra.com.au, id smtpd018022; Fri Feb 13 11:15:34 1998
Received: from shiva.trl.OZ.AU (shiva.trl.oz.au [137.147.20.34]) by cdn-mail.telecom.com.au (8.8.2/8.6.9) with ESMTP id LAA03465 for <[email protected]>; Fri, 13 Feb 1998 11:15:33 +1100 (EST)
Received: (from kowalski@localhost) by shiva.trl.OZ.AU (8.8.8/8.6.12) id LAA04297 for [email protected]; Fri, 13 Feb 1998 11:15:23 +1100 (EST)
Date: Fri, 13 Feb 1998 11:15:23 +1100 (EST)
From: Jacek Kowalski <[email protected]>
Message-Id: <[email protected]>
To: [email protected]
Subject: Re: SMC PCI Cards..
Sender: [email protected]
Precedence: bulk

Intel EtherExpress PRO/100 works OK for us on FreeBSD.

Cheers,
Jacek

>I am running 32bit NeTraMet 4.1 with a SMC9432TX Fast Ethernet PCI card.
>Unfortunately it seems the packet driver from SMC or the card does not
>support promiscuous mode.

>Does anyone have any recommendations for FE PCI cards that work, or a
>packet driver that will work?

>Cheers

>M.

From netramet-owner  Fri Feb 13 13:51:44 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id NAA21933 for netramet-outgoing; Fri, 13 Feb 1998 13:50:07 +1300 (NZDT)
Received: from lemon.netlink.co.nz (lemon.netlink.co.nz [203.97.244.37]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with ESMTP id NAA21881 for <[email protected]>; Fri, 13 Feb 1998 13:50:00 +1300 (NZDT)
Received: from netlink.co.nz (localhost [127.0.0.1])
       by lemon.netlink.co.nz (8.8.8/8.8.8) with ESMTP id NAA16042;
       Fri, 13 Feb 1998 13:49:43 +1300 (NZDT)
Message-ID: <[email protected]>
Date: Fri, 13 Feb 1998 13:49:43 +1300
From: Milton Ngan <[email protected]>
Organization: NetLink New Zealand
X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: David Vu <[email protected]>
CC: [email protected]
Subject: Re: SMC PCI Cards..
References: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

David Vu wrote:

> If this uses the DEC FastEthernet chip dc21x4x then it might work
> with the packet driver from crynwr:
>
> ftp://ftp.crynwr.com/drivers/dc21x4pk_11_0.zip

Unfortunately the new SMC9432TX uses SMC's new chipset the 83c170, which is not
compatible to the DEC chipset.

M.



From netramet-owner  Mon Feb 16 08:59:21 1998
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) id IAA19547 for netramet-outgoing; Mon, 16 Feb 1998 08:54:47 +1300 (NZDT)
Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by mailhost.auckland.ac.nz (8.8.5/8.7.3-ua) with SMTP id IAA19540; Mon, 16 Feb 1998 08:54:44 +1300 (NZDT)
Received: from cc-pc16 by cc-server9 with SMTP(PP);
         Mon, 16 Feb 1998 08:52:50 +1300
Received: by localhost with Microsoft MAPI; Mon, 16 Feb 1998 08:55:09 +1300
Message-ID: <[email protected]>
From: Glen Eustace <[email protected]>
To: "'Nevil Brownlee'" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: RE: 4.1 syntax question, ntm32 problem
Date: Mon, 16 Feb 1998 08:55:05 +1300
Organization: Computing Services - Massey University
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

On Saturday, February 14, 1998 2:49 PM, Nevil Brownlee
[SMTP:[email protected]] wrote:
>  * Replace the last two tests with an unconditional GotoAct, i.e.
>       Null & 0 = 0: GotoAct, MU_A;
>    This would more clearly indicate what these rules are doing.

As stated, this is the better solution.  I will use it. Thanks.

> These two command lines look OK.  All I can suggest is that you
> check to be sure that the write community (I guess it isn't really
> xxxx!) is the same in both cases.

Funny it may be, but I have tried, xxxx, and our normal community and
public and all give the same result.

> Hope this helps, Nevil

Unfortunately it doesn't. Have you any other suggestions ?

Thanks, Glen.

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.