From: Peter Bieringer <hidden> Date: 2004-08-30 08:09:46
Hi,
during playing around with RFC3041 capability in Linux kernel, I recognized
that the toggle (e.g. net.ipv6.conf.eth0.use_tempaddr) in sysctl is only
recognized if interface state changes from down to up, which means you
can't enable RFC3041 on an already running interface.
Is this
a) by design
b) temporary issue, will be solved later
c) bug, will be solved soon
I would need an answer because I want to implement support for this feature
in initscripts-ipv6, and it has a major impact on the location where to put
the related scripting code.
In case of a) -> before interface goes up, "ifup" needs to be extended
In case of b),c) -> "ifup-ipv6" can be extended
Thank you very much for any hint,
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
In article [off-list ref] (at Mon, 30 Aug 2004 10:09:46 +0200), Peter Bieringer [off-list ref] says:
during playing around with RFC3041 capability in Linux kernel, I recognized
that the toggle (e.g. net.ipv6.conf.eth0.use_tempaddr) in sysctl is only
recognized if interface state changes from down to up, which means you
can't enable RFC3041 on an already running interface.
Not quite true. net.ipv6.conf.eth0.use_tempaddr is recognized, but
new temporary addresses is created only when new public address is created
(by specification).
Is this
a) by design
b) temporary issue, will be solved later
c) bug, will be solved soon
a
and even b; we can probably extend our implementation
to create temprary address when net.ipv6.conf.eth0.use_tempaddr is changed
from 0 to 1.
--
Hideaki YOSHIFUJI @ USAGI Project [off-list ref]
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
In article [off-list ref] (at Mon, 30
Aug 2004 10:09:46 +0200), Peter Bieringer [off-list ref] says:
quoted
during playing around with RFC3041 capability in Linux kernel, I
recognized that the toggle (e.g. net.ipv6.conf.eth0.use_tempaddr) in
sysctl is only recognized if interface state changes from down to up,
which means you can't enable RFC3041 on an already running interface.
Not quite true. net.ipv6.conf.eth0.use_tempaddr is recognized, but
new temporary addresses is created only when new public address is created
(by specification).
Ok, should be perhaps noted in ip-sysctl.txt.
quoted
Is this
a) by design
b) temporary issue, will be solved later
c) bug, will be solved soon
a
and even b; we can probably extend our implementation
to create temprary address when net.ipv6.conf.eth0.use_tempaddr is
changed from 0 to 1.
(or to 2)
Hmm, from users point of view I would request the extension, because in
case of if sysctl-toggle will be done too late (means RA was already
received), nothing happen until next down->up cycle, if prefix of RA is
still the same.
Would such extension break any specifications?
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
In article [off-list ref] (at Mon, 30
Aug 2004 10:09:46 +0200), Peter Bieringer [off-list ref] says:
quoted
during playing around with RFC3041 capability in Linux kernel, I
recognized that the toggle (e.g. net.ipv6.conf.eth0.use_tempaddr) in
sysctl is only recognized if interface state changes from down to up,
which means you can't enable RFC3041 on an already running interface.
Not quite true. net.ipv6.conf.eth0.use_tempaddr is recognized, but
new temporary addresses is created only when new public address is created
(by specification).
quoted
Is this
a) by design
b) temporary issue, will be solved later
c) bug, will be solved soon
a
and even b; we can probably extend our implementation
to create temprary address when net.ipv6.conf.eth0.use_tempaddr is
changed from 0 to 1.
Any news on that? Have you plans to implement it?
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
From: Pekka Savola <hidden> Date: 2005-02-10 20:33:41
On Thu, 10 Feb 2005, Peter Bieringer wrote:
quoted
a
and even b; we can probably extend our implementation
to create temprary address when net.ipv6.conf.eth0.use_tempaddr is
changed from 0 to 1.
Any news on that? Have you plans to implement it?
Speaking of which, it would REALLY useful to implement the similar
"state change triggers" for e.g. accept_ra (which would send out a RS
immediately, which is currently impossible from the user space).
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings