Am 03.01.2014 19:40, schrieb Pierre Schmitz:
Am 03.01.2014 19:33, schrieb Thomas Bächler:
--- configs/releng/root-image/etc/udev/rules.d/81-dhcpcd.rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/releng/root-image/etc/udev/rules.d/81-dhcpcd.rules b/configs/releng/root-image/etc/udev/rules.d/81-dhcpcd.rules index 970da69..eadc669 100644 --- a/configs/releng/root-image/etc/udev/rules.d/81-dhcpcd.rules +++ b/configs/releng/root-image/etc/udev/rules.d/81-dhcpcd.rules @@ -1 +1 @@ -ACTION=="add", SUBSYSTEM=="net", ENV{SYSTEMD_WANTS}="dhcpcd@$name.service" +ACTION=="add", SUBSYSTEM=="net", NAME=="en*|eth*", ENV{SYSTEMD_WANTS}="dhcpcd@$name.service"
Are we sure this works as intended? I have seen wireless drivers naming the device eth0 and I guess the new udev naming also uses en* here.
This is legacy stuff in any case. All newer driver (i.e. mac80211 and newer hardmac drivers) don't use ethX anymore.
Or wasn#t your goal to exclude wireless here but virtual devices like tun/tap etc.?
Right now, dhcpcd is activated on wireless, tap, ppp and other stuff that usually doesn't make sense.