On 2/13/07, Neil Horman <[EMAIL PROTECTED]> wrote:
1) Kernel network driver X detects that it has hardware to drive, and consequently calls register_netdev. This creates the network interface and registers all the appropriate proc and sysfs files, which are now accessible in user space.
The problem is that in the IPv6 case, the sysfs files are _not_ registered in this step but only after the interface is set up (in fact after the first proper address is added to the interface, which generally would be the link local address).
As has been seen, one place to fix this is by adding logic to the ifup scripts for the appropriate protocol to issue sysctl -w commands to set configs prior to issuing the ifconfig up or ip link up commands.
Due to the previous point, this wouldn't work. I believe the proper solution is to init the ipv6 dev on interface creation (and thus trigger the adding of the sysfs files) and not when the first address is added to the interface. There might be issues with this solution (known internal races, module unloading issues, etc), that's why i asked previously if there were any known ones. Hugo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
