[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tunnelMIB (RC2667) implementations and/or deployment

To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: tunnelMIB (RC2667) implementations and/or deployment
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
Date: 23 Sep 2003 17:41:24 +0200
Cc: "mibs (E-mail)" <mibs@ops.ietf.org>
In-reply-to: <7D5D48D2CAA3D84C813F5B154F43B15502331636@nl0006exch001u.nl.lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B15502331636@nl0006exch001u.nl.lucent.com>
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Hi!

Bert> I'd be interested to hear about implementations and/or
Bert> deployment of the tunnelMIB as defined in RFC2667.

Some time ago, I've done a partial implementation (excl. the
tunnelConfigTable) for the NET-SNMP agent (focusing on the Linux
platform). It is part of the official NET-SNMP distribution.

I had a concern about the MIB design, which does not allow SET
operations on two objects (tunnelIfLocalAddress and
tunnelIfRemoteAddress) that IMHO should be writeable to allow
(re)configuring tunnel endpoints.

I'm actively using SNMPv3 and SET operations on these objects to
reconfigure my tunnel endpoint which changes daily due to dynamic IP
addresses assigned by my DSL provider. For that reason, I
intentionally did implement these read-only objects in a read-write
fashion.

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/net-snmp/net-snmp/agent/mibgroup/tunnel/tunnel.c?rev=5.3&content-type=text/vnd.viewcvs-markup

 -frank

References:
- tunnelMIB (RC2667) implementations and/or deployment
  - From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>

Prev by Date: tunnelMIB (RC2667) implementations and/or deployment
Next by Date: irrelevant objects in a row
Previous by thread: tunnelMIB (RC2667) implementations and/or deployment
Next by thread: Re: tunnelMIB (RC2667) implementations and/or deployment
Index(es):
- Date
- Thread