netdev - IPv6 autoconf/accept_ra default values

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Jan 2010 00:45:37 +0100 (CET)
From:	Kolbjørn Barmen <linux@...la.no>
To:	Brian Haley <brian.haley@...com>
cc:	Vlad Yasevich <vladislav.yasevich@...com>, davem@...emloft.net,
	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: IPv6 autoconf/accept_ra default values - revisited

Cheers, remember me? :)

Regarding the autoconf parameter for the ipv6 module, was it not the
intention that it should cover accept_ra as well?

I ask since I have used this paramater in the belief that it also did
cover accept_ra, however on a couple of systems that are using bridge
interface, I noticed that they "fall off" ipv6-wise, unless I explisitly
ping them.

So I finally got around to find out what was going on, and to my surprise
I see that they both have autoconfigured routes on eth0 (using link local)
that they want to use instead of what I have statically configured for br0.

So, could "autoconf" also please turn off accept_ra?
Or, if you like, add another parameter for it :P

I tried using disable_ipv6 in all kinds of tricky ways to get what I want,
but it's close to impossble, with interfaces coming and going in the
bridge I always end up with autoconfigured addresses where I dont want
them, strange routing issues etc. I cannot just add entries in sysctl.conf
for bridge interfaces, since the bridge interfaces (and others for that
matter) are not there when sysctl is run on bootup.

And the entire "all" vs. "default" still confuses me.

* "default" is supposed to cover _all future_ interfaces?
* "all" is supposed to cover _all existing_ interfaces, and change them?
  If not, then what is its function?

And lastly - all this would be a non-issue if the defaults values were so
that all autoconf/accept_ra were 0 - it's _so_ easy to turn on, but
incredibly complicated to turn off. The harder it is to make sense out of
things like this, the harder it is to have people start with IPv6.

Cheers again! :)

-- kolla
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html