[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00537) Re: [mipl] Re: Autoconfiguration problem with radvd
- To: Jun-ichiro itojun Hagino <itojun@xxxxxxxxxx>
- Subject: (usagi-users 00537) Re: [mipl] Re: Autoconfiguration problem with radvd
- From: "Venkata Jagana" <jagana@xxxxxxxxxx>
- Date: Mon, 21 May 2001 18:22:46 -0700
- Cc: usagi-users@xxxxxxxxxxxxxx, mipl@xxxxxxxxxxxxxxxxxxxxxxxxx
- Importance: Normal
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Sender: "Venkata Jagana" <jagana@xxxxxxxxxx>
>>As a first step, we have configured the addresses manually and
>>we haven't found any issues. However, with radvd, we thought
>>that we should be able to autoconfigure even router
>>interfaces (so that the route entries are also created
>>automatically for these two subnets) and then enabled forwarding
>>on the required interface(s) to go across the router. I don't see
>>any issue with it and haven't found any info on NDP regarding
>>why routers shouldn't be autoconfigured at all.
> RFC2462, very first portion specifically mentions "host
> autoconfiguration". in IPv6 terminology "host" = "not router".
True, RFC2462 talks about 'host' autoconfiguration only but doesn't talk
about routers as clearly specified in the last but one paragraph
of section 1 of RFC2462. My understanding is that it doesn't mean
'autoconfiguration' is limited to 'hosts only'.
However, in RFC 2461 (NDP), section 3 (protocol overview), there is
a definition for 'address autoconfiguration' problem - "how nodes
automatically
configure an address for an interface". Here 'nodes', according to
IPv6 terminology, refer to either routers or a hosts. So, I believe,
the autoconfiguration could be applied to either of them.
Thanks,
Venkat
----------------------------------------------------------------
Venkata R Jagana
IBM Beaverton
jagana@xxxxxxxxxx
Tel: (503) 578 3430 T/L 775-3430