[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00533) Re: [mipl] Re: Autoconfiguration problem with radvd
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 00533) Re: [mipl] Re: Autoconfiguration problem with radvd
- From: Jun-ichiro itojun Hagino <itojun@xxxxxxxxxx>
- Date: Mon, 21 May 2001 16:31:22 +0900
- Cc: Pekka Savola <pekkas@xxxxxxxxxx>, mipl@xxxxxxxxxxxxxxxxxxxxxxxxx
- In-reply-to: jagana's message of Sun, 20 May 2001 18:32:13 MST. <OF7AA7A5B6.C99770CF-ON88256A53.00047386@LocalDomain>
- List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Sender: itojun@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".
itojun