Sorry. I'm very newbie to the system, so don't blame me!
I renamed all my interfaces on my Gentoo box with simply rule in /etc/udev, then
i would enable proxy_arp only for interface named "pub0", so i put it with the
correct value in /etc/sysctl.conf
I rebooted, but i found that sysctl is launched before udev renaming then my
proxy_arp didn't work as i'm expected.
Steps to Reproduce:
1. rename the interfaces with udev rules in /etc/udev
2. set a features with sysctl.conf for specific interface
It's not so drammatic bug. I simply add sysctl -p -q on /etc/conf.d/local.start
sysctl is run long after udev is started
sysctl simply sets values in /proc/sys/net/ so something else is likely going on
Yeah, sysctl happens _way_ after udev runs at startup.
What is probably happening is your module is getting loaded for your device,
and that is racing with the sysctl stuff, right?
get back to us
Sorry guys, but i completely forget this issue!
I cannot test anymore on the machine because now is on production: it's a lovely
outgoing load balancer...
But i tried with my workstation.
Greg Kroah-Hartman was right, the problem is that the configuration for the
device was create by the kernel when the interface goes up (then at network
initialization) but the sysctl was already started.
Now i know a little bit more of Linux... and thank you Gentoo devs!