netdev
[Top] [All Lists]

Re: linux-2.2.17 auto-configuration

To: netdev@xxxxxxxxxxx
Subject: Re: linux-2.2.17 auto-configuration
From: Jacek Konieczny <jajcus@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 6 Oct 2000 19:27:36 +0200
Cc: Moter Du <Moter_Du@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <C6BEA88DAF6AD31185F500105A835CBB01BAC139@stslex.siemens.com.tw>; from Moter_Du@stsl.siemens.com.tw on Fri, Oct 06, 2000 at 05:55:01PM +0800
References: <C6BEA88DAF6AD31185F500105A835CBB01BAC139@stslex.siemens.com.tw>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Mutt/1.1.11i
On Fri, Oct 06, 2000 at 05:55:01PM +0800, Moter Du wrote:
> I'm confused by auto-configuration in linux-2.2.17. In summary it seems
> Linux supports only solicited auto-configuration, not unsolicited
> auto-configuration. The term 'solicited auto-configuration' means Linux
> sends a RS and Router replies a RA. The term 'unsolicited
> auto-configuration' means Router advertises a RA periodically. In the latter
> case Linux does receive the RA, but it never auto-configured itself.
> 
> I should trace into the kernel. But if some can point out the answer I would
> appreciate very much.
Some time ago I have sent here (and to one of IPv6 maintainers) a patch
fixing 2.2.x-kernel auto-configuration bug. It seems it was not included
in 2.2.17 kernel.

The problem I was fixing was "disapearing" "all-nodes" multicast
address. After the interface went down and up it lost the ff02::1
multicast address and it received no RA. After removing and loading the
module it would come back and auto-configuration worked again.

I hope this helps.

Greets,
        Jacek 


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