In other words, a DHCP server takes over the address allocation and not each device independently.

In other words, an IP should be permanently assigned via DHCP and the MAC address. If you're going to go to the trouble of assembling a device, then you might want to use it in other networks. So I can throw away the two conventional solutions for eth0 for the new eth1.ĭoes anyone have a corresponding solution? A static IP address is not the solution I am looking for. Of course, match and link cannot work because I never know what I have to match. Inside /boot/config.txt or /boot/cmdline.txt I can not change the MAC address of eth1 because it is on the USB ethernet adapter, right? The MAC address will always change and the USB adapter is loaded after the network card on the Raspberry Pi, right?Īs I said, the MAC address of eth1 changes constantly during booting. I can match and link this as example in /etc/systemd/network/00-default.link with: Īs you can see it works fine. As example I have following line: smsc95xx.macaddr=0a:b9:0c:6a:45:89 If I edit /boot/config.txt or /boot/cmdline.txt I only can change the static MAC address of eth0. That is why the USB ethernet adapter is used. This Ethernet port cannot even be reached and used because of a housing.

It is of course from the Raspberry Pi itself. But it is not the needed ethernet adapter. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 At first you can see as example this: eth0: flags=40Įther 0a:b9:0c:6a:45:90 txqueuelen 1000 (Ethernet) I am using a Raspberry Pi and a common USB ethernet adapter.

Startech usb to ethernet mac