[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00532) Re: [mipl] Autoconfiguration problem with radvd
- To: <usagi-users@xxxxxxxxxxxxxx>
- Subject: (usagi-users 00532) Re: [mipl] Autoconfiguration problem with radvd
- From: Pekka Savola <pekkas@xxxxxxxxxx>
- Date: Mon, 21 May 2001 08:48:55 +0300 (EEST)
- Cc: Teemu Rinta-aho <teemu.rinta-aho@xxxxxxxxxxxxxx>, <mipl@xxxxxxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <OFB2C256E4.311735C5-ON88256A53.0008C4DE@LocalDomain>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
On Sun, 20 May 2001, Venkata Jagana wrote:
[snip]
> In fact, we believe one could have an init script that
> perform these steps in this exact order to avoid any manual configuration
> at the router. Pekka Savola pointed out in his mail that router
> cann't be autoconfigured but I am not sure why.
Well, you can work around this and use autoconfiguration _anyway_ as you
noticed, but clearly RFC2461 and RFC2462 only discuss Host
autoconfiguration; for Routers, the behaviour is Router Renumbering
(RFC2894). This is not currently implemented.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords