You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be a better install experience if the replica.one build for the ECW5211-L devices defaulted to a static IP on the default bridge instead of relying on DHCP.
The issue with DHCP is that to be able to ssh into the device after flashing, you need to look through your DHCP server logs and identify the IP which was assigned. Additionally, for the 2 devices I flashed with replica, both seemed to have "issues" promptly obtaining an IP address via DHCP on the default bridge for some reason. Neither device quickly (took >> 10 seconds + user action) obtained a DHCP address on first boot after flash; I had to power cycle and unplug/replug the Ethernet cable before they finally obtained an IP.
I don't believe my DHCP server (dnsmasq in this case) is faulty but suspect there's some lag between when networkd comes up and when it solicits for a DHCP address on the bridge. This really slows down the verification process when flashing a number of these devices which tends to be a manual process.
My thoughts are the default network configuration could be improved by:
adding Address=192.168.1.1/24 to [Network] section in /etc/systemd/network/br-lan.network
This would ensure a static address is available on the bridge interface in the event DHCP fails or isn't present where the device is being tested.
cc: @storrgie
The text was updated successfully, but these errors were encountered:
I think it would be a better install experience if the replica.one build for the ECW5211-L devices defaulted to a static IP on the default bridge instead of relying on DHCP.
The issue with DHCP is that to be able to ssh into the device after flashing, you need to look through your DHCP server logs and identify the IP which was assigned. Additionally, for the 2 devices I flashed with replica, both seemed to have "issues" promptly obtaining an IP address via DHCP on the default bridge for some reason. Neither device quickly (took >> 10 seconds + user action) obtained a DHCP address on first boot after flash; I had to power cycle and unplug/replug the Ethernet cable before they finally obtained an IP.
I don't believe my DHCP server (dnsmasq in this case) is faulty but suspect there's some lag between when networkd comes up and when it solicits for a DHCP address on the bridge. This really slows down the verification process when flashing a number of these devices which tends to be a manual process.
My thoughts are the default network configuration could be improved by:
Address=192.168.1.1/24
to[Network]
section in/etc/systemd/network/br-lan.network
This would ensure a static address is available on the bridge interface in the event DHCP fails or isn't present where the device is being tested.
cc: @storrgie
The text was updated successfully, but these errors were encountered: