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'm staging a server with a custom config of LF-Edge and an USB stick that has override for static IP on eth0.
I plugged a laptop into eth0 just for doing ping tests to confirm that the IP got configured.
Ping works for 10-15 seconds after which it fails.
If I look in the logs I see
"Not testing highest priority DevicePortConfig key usb due to All attempts to connect to controller...../edgedevice/ping failed: (send vai eth0 with SRC IP)"
after that the IP on eth0 goes away and it switched to DHCP
ERROR: Summary: Waiting for DHCP IP address(es)
It will only switch back to having an IP on eth0 (from the override) if I do:
ifconfig down/up
or a reboot
Expected behavior
That the static IP override remains in place.
Is this how it should behave by design with fallback to DHCP and ignoring the static IP override on eth0 if it cannot reach controller?
The text was updated successfully, but these errors were encountered:
Describe the unexpected behaviour
I'm staging a server with a custom config of LF-Edge and an USB stick that has override for static IP on eth0.
I plugged a laptop into eth0 just for doing ping tests to confirm that the IP got configured.
Ping works for 10-15 seconds after which it fails.
If I look in the logs I see
"Not testing highest priority DevicePortConfig key usb due to All attempts to connect to controller...../edgedevice/ping failed: (send vai eth0 with SRC IP)"
after that the IP on eth0 goes away and it switched to DHCP
ERROR: Summary: Waiting for DHCP IP address(es)
It will only switch back to having an IP on eth0 (from the override) if I do:
Expected behavior
That the static IP override remains in place.
Is this how it should behave by design with fallback to DHCP and ignoring the static IP override on eth0 if it cannot reach controller?
The text was updated successfully, but these errors were encountered: