From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28425 invoked by alias); 9 May 2009 08:48:34 -0000 Received: (qmail 28417 invoked by uid 22791); 9 May 2009 08:48:33 -0000 X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,WEIRD_PORT X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 09 May 2009 08:48:28 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M2iEI-0001nJ-R6 for ecos-discuss@sources.redhat.com; Sat, 09 May 2009 08:48:22 +0000 Received: from 67-220-10-117.usiwireless.com ([67.220.10.117]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 May 2009 08:48:22 +0000 Received: from grante by 67-220-10-117.usiwireless.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 May 2009 08:48:22 +0000 To: ecos-discuss@sources.redhat.com From: Grant Edwards Date: Sat, 09 May 2009 08:48:00 -0000 Message-ID: References: <20090508221045.GA13907@ubuntu.local> <20090508230957.GA18135@ubuntu.local> <4A04BD1C.7000207@mlbassoc.com> User-Agent: slrn/0.9.8.1pl1 (Linux) X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: SNMP lockup X-SW-Source: 2009-05/txt/msg00048.txt.bz2 On 2009-05-08, Gary Thomas wrote: >>> The problem occurs when cyg_snmp_get_if() is called with if_num <= 0. [...] >>> I'm surprised nobody else has run into this. I'm told all our >>> customers who have HP or Cisco SNMP managers have had to >>> disable SNMP support in our products to keep them from locking >>> up every few minutes. >> >> I was just googling +'ifPhysAddress.0' >> >> It seems you are not alone :-) >> >> http://mtsc.moxa.com:8888/Software/DN/NPort/Firmware/NPort%205000/NPort%205600/ver3.2/VERSION.TXT That's interesting -- I hadn't found that. Since the bug was in eCos-specific code, do we assume that Moxa is using eCos for the NPort? >> UCD-SNMP had a lot of holes. eCos UCD-SNMP implementation has >> even more holes :-( Um... I blame Dick Cheney and Karl Rove! > Feel free to improve this Workin' on it... > - much of the networking code, including SNMP, is more than > seven (7!) years old. A lot has gone on in the world in that > time... What I'd like a pointer on is the interface numbering in SNMP OIDs. Are the interfaces supposed to be numbered 1..N with interface 0 being non-existent? Or are eCos interface numbers off by one and they should really be 0,1 instead of 1,2? [I tried looking through the OID/ASN.1 docs, but got lost rather quickly.] If SNMP interface numbers are supposed to start at #1, why do HP and Cisco SNMP managers ask for attributes of interface #0? I looked at network traces for one customer site using, I believe, HP Insight. It does read the interface attributes for interfaces 1 and 2. I don't see it attempt to read attributes for interface 3 (which doesn't exist). I do see it attempt to read attributes for interface 0 (which also doesn't exist). If interface numbers are supposed to start at #0, will renumbering the interfaces at this point (after product has been shipping for 7 years) cause more problems that it will solve? -- Grant -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss