DougieLawson wrote: ↑
Wed Oct 04, 2017 6:09 am
Predictable names uses the device MAC to create the name the software sees. That means I can have a single /etc/dhcpcd.conf file that's common to all 14 of my raspberries.
how can that be?
A single /etc/dhcpcd.conf file common to all 14 of your raspberries would imply 14 raspberries with identical MAC addresses?!
Unless you proliferate all MAC addresses of all raspberries across each /etc/dhcpcd.conf of each raspberry. What is of no benefit compared to the situation where you use a distinct /etc/dhcpcd.conf for each raspberry.
What to do if you want to extend to 14+1 raspberries? You then would have to change all /etc/dhcpcd.conf of all your raspberries. If you still want to have a 'single' /etc/dhcpcd.conf file that's common to all.
To overcome all this a method should be created to assign static names (like wlan0, wlan1, eth0, eth1 etc.) for existing NICs which remain constant no matter what hardware interfaces are actually found on a particular machine. The interface naming could be derived from USB dongle plug-in position starting with name wlan1. The internal wlan could be statically assigned to wlan0.
Code: Select all
| wlan1 | wlan2 |
| wlan3 | wlan4 |
+---------------+ (RPI USB ports)
Does such a thing already exist or do I have to implement that myself?
The systemd-predictable stuff currently in use is unacceptable.
A trivial example (sufficient for 1 additional USB wlan dongle) which already provides a simple solution suitable for a common use case:
Problem: you want uniquely address 2 wlan devices (1 onboard, 1 USB dongle) on a raspberry the most easy way (i.e. which predictable device names independent of MAC addresses
and other hardware specific stuff):