From: "Denis V. Lunev" <den@parallels.com>
To: Chr <chunkeey@web.de>
Cc: hostap@lists.shmoo.com, netdev@vger.kernel.org
Subject: Re: IPv6 unique local address flushes on up/down
Date: Tue, 25 Mar 2008 18:11:38 +0300 [thread overview]
Message-ID: <1206457898.14357.16.camel@iris.sw.ru> (raw)
In-Reply-To: <200803251557.21563.chunkeey@web.de>
On Tue, 2008-03-25 at 15:57 +0100, Chr wrote:
> Hi,
>
> I have a problem with hostapd & IPv6...
>
> as you might know, or not... hostapd needs to initialize
> the interface (e.g it changes it to master/accesspoint mode,
> which can only be done if the interface is down)...
>
> However if the interface is brought down & up again (e.g whenever
> hostap starts or restarts)... the IPv6 logic flushes the unique-local ipv6
> address that I gave it (by hand) with ip addr add fddb:xyz...::1//64 dev ath0
> in /etc/network/interfaces ifup script (-probably debian specific-).
>
> And that's bad, because bind9,ISC dhcp-server v4.1 and racoon(IPsec/VPN)
> needs a static address for their records/lease database and configuration...
>
> This wasn't problem with the old IPv4... because there the
> 10.x.y.z or 192.168.a.b addresses aren't deleted when the interface
> was _reinitialized_ by the hostap...
>
> Now my question, which _one_ should we fix the applications or the stack?!
> I think the network stack, but I don't know if there are RFC about this
> issue... or is there already some flag/setting which I've missed so far?
On interface down IPv6 stack unconditionally deletes all addresses from
the interface in the addrconf_ifdown routine.
next prev parent reply other threads:[~2008-03-25 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 14:57 IPv6 unique local address flushes on up/down Chr
2008-03-25 15:11 ` Denis V. Lunev [this message]
2008-03-25 15:24 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-25 16:07 ` Chr
2008-03-25 16:20 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-25 17:16 ` Chr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206457898.14357.16.camel@iris.sw.ru \
--to=den@parallels.com \
--cc=chunkeey@web.de \
--cc=hostap@lists.shmoo.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).