binding + autoconfig

Hi,

I bonded together two Ethernet interfaces, and if I keep
restarting
networking, the bond interface sometimes does, but mostly
does not get
its global prefix from the router.  The two physical
interfaces and
the bond share a MAC, and accordingly also share their
link-local
addresses.  I've got the impression that the bond gets its
global
address only if the right interface is activated in the bond
first,
but I haven't checked this rigorously yet.  Any thoughts on
this?

On the other hand, I could live without autoconfiguration
complicating
my life.  How could I disable that?
/proc/sys/net/ipv6/conf/*/autoconf and accept_ra are already
all set
to 0, but a networking restart still gets me link-local
addresses...
-- 
Regards,
Feri.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

On Thu, Aug 23, 2007 at 04:06:06AM +0200, Wagner Ferenc
wrote:
> /proc/sys/net/ipv6/conf/*/autoconf and accept_ra are
already all set
> to 0, but a networking restart still gets me link-local
addresses...

You cannot disable that. It's also not part of routing
advertisement --
even if you have no working IPv6 setup but you do have the
ipv6 module
loaded, you will have a link-local address. It's the kernel
that
generates the link-local address, not the routing
advertisement or
anything.

-- 
<Lo-lan-do> Home is where you have to wash the
dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

Wouter Verhelst <wouterdebian.org> writes:

> On Thu, Aug 23, 2007 at 04:06:06AM +0200, Wagner Ferenc
wrote:
>> /proc/sys/net/ipv6/conf/*/autoconf and accept_ra
are already all set
>> to 0, but a networking restart still gets me
link-local addresses...
>
> You cannot disable that. It's also not part of routing
advertisement --
> even if you have no working IPv6 setup but you do have
the ipv6 module
> loaded, you will have a link-local address. It's the
kernel that
> generates the link-local address, not the routing
advertisement or
> anything.

Eh, that was a desperate last ditch attempt after setting
autoconf to
zero didn't help.  What's controlled by autoconf, then? 
Thanks for
the reply, anyway.
-- 
Regards,
Feri.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

On Thu, Aug 23, 2007 at 01:42:58PM +0200, Ferenc Wagner
wrote:
> Wouter Verhelst <wouterdebian.org> writes:
> 
> > On Thu, Aug 23, 2007 at 04:06:06AM +0200, Wagner
Ferenc wrote:
> >> /proc/sys/net/ipv6/conf/*/autoconf and
accept_ra are already all set
> >> to 0, but a networking restart still gets me
link-local addresses...
> >
> > You cannot disable that. It's also not part of
routing advertisement --
> > even if you have no working IPv6 setup but you do
have the ipv6 module
> > loaded, you will have a link-local address. It's
the kernel that
> > generates the link-local address, not the routing
advertisement or
> > anything.
> 
> Eh, that was a desperate last ditch attempt after
setting autoconf to
> zero didn't help.  What's controlled by autoconf, then?
 Thanks for
> the reply, anyway.

if you have route advertisement running on your network,
your
globally-valid IP address that's generated automatically...

if you provide the output of 'ip addr show', I could tell
you which one.

-- 
<Lo-lan-do> Home is where you have to wash the
dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

Wouter Verhelst <wuter.be> writes:

> On Thu, Aug 23, 2007 at 01:42:58PM +0200, Ferenc Wagner
wrote:
> 
>> What's controlled by autoconf, then?
>
> if you have route advertisement running on your
network, your
> globally-valid IP address that's generated
automatically...

Thanks for the info, that clears it up.  What's more,
finally I found
the docs in ip-sysctl.txt. 

Now to make sure I'm not mistaken: the link-scope IPv6
address of my
bond interface is flagged tentative.  This is probably
because its
slave devices also have the same MAC, thus the same
link-scope IPv6
address, so the kernel level autoconfiguration fails at the
uniqeness
check.  Right?  It's not stable, though: often I end up with
three
identical IPv6 addresses on the tree interfaces.
-- 
Regards,
Feri.


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

On Thu, Aug 23, 2007 at 04:45:06PM +0200, Ferenc Wagner
wrote:
> Wouter Verhelst <wuter.be> writes:
> > On Thu, Aug 23, 2007 at 01:42:58PM +0200, Ferenc
Wagner wrote:
> >> What's controlled by autoconf, then?
> > if you have route advertisement running on your
network, your
> > globally-valid IP address that's generated
automatically...
> 
> Thanks for the info, that clears it up.  What's more,
finally I found
> the docs in ip-sysctl.txt. 
> 
> Now to make sure I'm not mistaken: the link-scope IPv6
address of my
> bond interface is flagged tentative.  This is probably
because its
> slave devices also have the same MAC, thus the same
link-scope IPv6
> address, so the kernel level autoconfiguration fails at
the uniqeness
> check.  Right?

No clue, but it sounds not too far-fetched, so it could be
true. Hey, I
don't know everything 

> It's not stable, though: often I end up with three
> identical IPv6 addresses on the tree interfaces.

That sounds like a race somewhere, then. If you don't need
these
link-local addresses, I wouldn't worry about it.

-- 
<Lo-lan-do> Home is where you have to wash the
dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org