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
There is a bug in the DHCP interface discovery. The for loop…
for dev in `get_device_by_hwaddr` ; do
…correctly iterates over all relevant interfaces. But the $DEVICE variable is only set the first time of the loop. In subsequent loop iterations this line will prevent $DEVICE from taking on the new interface name:
[ -z "$DEVICE" -a -n "$HWADDR" ] && DEVICE=$(get_device_by_hwaddr $HWADDR)
$DEVICE is still present from the previous run so the test for an empty string ([ -z $DEVICE]) will always fail.
This bug will not appear if the first interface found is the interface which you want to use for a recovery. But in my case the first interface was a Wifi interface (wlan0) and the second was my connected ethernet interface (eth0). However the 'dhclient' kept trying to get an IP address on wlan0.
I will send a pull request in a minute to fix this issue. I have already tested it on my system.
In addition it may be better to ask the user which interface to use for DHCP if there are multiple of them.
The text was updated successfully, but these errors were encountered:
Fixed that in the recovery system the DHCP client
did not iterate through all network interfaces.
It incorrectly took only the first found interface.
If the interface that is intended for recovery
was not the first one, automatic recovery had failed,
see #1986
rear/usr/share/rear/skel/default/etc/scripts/system-setup.d/58-start-dhclient.sh
Line 35 in eb63155
There is a bug in the DHCP interface discovery. The for loop…
…correctly iterates over all relevant interfaces. But the $DEVICE variable is only set the first time of the loop. In subsequent loop iterations this line will prevent $DEVICE from taking on the new interface name:
$DEVICE is still present from the previous run so the test for an empty string ([ -z $DEVICE]) will always fail.
This bug will not appear if the first interface found is the interface which you want to use for a recovery. But in my case the first interface was a Wifi interface (wlan0) and the second was my connected ethernet interface (eth0). However the 'dhclient' kept trying to get an IP address on wlan0.
I will send a pull request in a minute to fix this issue. I have already tested it on my system.
In addition it may be better to ask the user which interface to use for DHCP if there are multiple of them.
The text was updated successfully, but these errors were encountered: