I am replying to this as I too would like some clarification as to the difference between the two options {eui64|autoconf} for enabling the old IPv6 behavior.
I typically read the man pages frequently and routinely and while sometimes they are lacking on linux, I have found the man pages for FreeBSD and OpenBSD to be very thorough. So needless to say I initially thought it was a bug introduced into the kernel when according to the man page all I had to do to re-enable IPv6 for a certain interface was call autoconf as an option (which made sense to me). This only worked enough to enable IPv6 addressing, but no enough functionality to actually plumb up the necessary routes even for the IP that was assigned and RA's were not being respected despite the tuning of the appropriate sysctl. It wasn't until I read else in the update changelog that someone else on this list (I forget his name now and have deleted the email) the link to said page where it said something conflicting to the man page. There it said to use the eui64 option also with no mention of the autoconf option. So in one place it says to use one option with no mention of the other, and then in the other place its the complete opposite with neither clarifying what's the exact difference between the two, and when one should be used over the other. Reilly On 01/08/2015 03:20 AM, Harald Dunkel wrote: > On 01/07/15 23:38, Sebastian Benoit wrote: >> autoconf is only enabled if you do >> >> ifconfig <if> inet6 autoconf >> >> otherwise, RAs will be ignored. >> > Thanx very much. I would suggest to mention the default in > ifconfig(8). > > Regards > Harri