No it does not work for me; there is a change to the iwl-phy0:assoc LED after those scripts are run.
The LED controls (/sys/class/leds/*) are re-symlinked when a WiFi connection is brought up or taken down. The physical devices "/sys/devices/pci0000:00/0000:00:1c.3/0000:06:00.0/leds/iwl-phy0:*" (on my machine) are not the same ones as from a previous WiFi connection (even though they are the same names), so I believe the problem lies in HAL or UDEV.
I think that after a link is brought up (and after all the if-up.d scripts are run), the /sys/devices/ are re-created and it's that process where iwl-phy0:assoc is set to "indicate" it's configured to [phy0assoc], but is actually set to [phy0rx] or [phy0tx], causing the LED to blink during link activity.
That's my guess as to why scripts in if-up.d/ don't fix the problem. I hope that makes sense...
Hi Tom,
No it does not work for me; there is a change to the iwl-phy0:assoc LED after those scripts are run.
The LED controls (/sys/class/leds/*) are re-symlinked when a WiFi connection is brought up or taken down. The physical devices "/sys/devices/ pci0000: 00/0000: 00:1c.3/ 0000:06: 00.0/leds/ iwl-phy0: *" (on my machine) are not the same ones as from a previous WiFi connection (even though they are the same names), so I believe the problem lies in HAL or UDEV.
I think that after a link is brought up (and after all the if-up.d scripts are run), the /sys/devices/ are re-created and it's that process where iwl-phy0:assoc is set to "indicate" it's configured to [phy0assoc], but is actually set to [phy0rx] or [phy0tx], causing the LED to blink during link activity.
That's my guess as to why scripts in if-up.d/ don't fix the problem. I hope that makes sense...