netdev
[Top] [All Lists]

[RTNETLINK] Tunnel config via netlink (Was Re: Convert RTM_* to enum)

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: [RTNETLINK] Tunnel config via netlink (Was Re: Convert RTM_* to enum)
From: Ville Nuorvala <vnuorval@xxxxxxxxxx>
Date: Thu, 16 Sep 2004 12:08:54 +0300 (EEST)
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, YOSHIFUJI Hideaki <yoshfuji@xxxxxxxxxxxxxx>, James Morris <jmorris@xxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20040915020942.GA32721@gondor.apana.org.au>
References: <20040915020942.GA32721@gondor.apana.org.au>
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 15 Sep 2004, Herbert Xu wrote:

> I decided to bite the bullet and use netlink for the tunnel operations.

It's great if you have the time and energy to do this! Let me know if I
can be of any assistance with the ip6_tunnel.c modifications.

While designing the netlink interface it might perhaps be a good idea to
take a look at draft-ietf-ipv6-inet-tunnel-mib-02.txt, which is currently
in IESG processing. The IPv6 specific tunnel encapsulation limit (below)
is still missing from the draft but will be included in the RFC.

tunnelIfEncapsLimit OBJECT-TYPE
    SYNTAX     Integer32 (-1 | 0..255)
    MAX-ACCESS read-write
    STATUS     current
    DESCRIPTION
            "The maximum number of additional encapsulations permitted
            for packets undergoing encapsulation at this node.  A value
            of -1 indicates that no limit is present (except as a result
            of the packet size)."
    REFERENCE  "RFC 2473, section 4.1.1"
    ::= { tunnelIfEntry 11 }

Regards,
Ville
--
Ville Nuorvala
Research Assistant, Institute of Digital Communications,
Helsinki University of Technology
email: vnuorval@xxxxxxxxxx, phone: +358 (0)9 451 5257

<Prev in Thread] Current Thread [Next in Thread>