I just plugged my HL4 into the wall the first time this morning—it booted up fine, I can use the local monitor connections to interact with the device locally.
It didn’t automatically pick up an IPv4 address, it just shows LOWER_UP via ip a. Okay, so I read through the HL4 User Manual and glanced through the IP address configuration section—I usually set manual IP addresses for my devices, but would rather do that on my router instead of on each device.
But figuring maybe something isn’t quite happy in the DHCP configuration, I went ahead and set a manual IPv4 address, gateway, and DNS entry, and saved the configuration.
I did this once in the UI, and then confirmed it was set correctly in nmtui.
However, I’m still not getting a link or IP address, can’t ping the outside world, and the link light on the network jack is not lighting up… it just shows the same status in ip a output.
I tested the same cable and port on another computer (just unplugged from the HL4 and plugged into the other computer) and it lights up and works fine…
Is there something else in the setup process I’m missing? There’s only one port on the back of the HL4 (the motherboard’s built-in 2.5G port), so it can’t be too difficult, I would assume!
I may try plugging in a separate USB NIC to see if that is picked up automatically.
1 Like
Here’s what I currently see:
I’ve switched it to automatic and back to static IP but the Ethernet port never connects 
I also tried an external Ethernet dongle, and it is recognized but also never gets an IP address assigned.
1 Like
I just noticed my Network Configuration settings has no-auto-default=*, which seems to not be Rocky Linux’s default (see Rocky Linux Network Configuration).
Here’s the network configuration for the Ethernet port:
1 Like
I apologize for the weird blotchy green text — JetKVM is only allowing me to get a display through a DisplayPort-to-HDMI adapter and that seems to be getting a wonky resolution. The HDMI ports aren’t giving me output currently.
So here’s what I found that helped me solve the issue:
- RHEL 7/8/9 installs
NetworkManager-config-server by default.
- That package creates a config file
/usr/lib/NetworkManager/conf.d/00-server.conf which includes the no-auto-default=* setting.
- Using
sudo nano /usr/lib/NetworkManager/conf.d/00-server.conf, commenting out the two settings under [main], then restarting NetworkManager (sudo systemctl restart NetworkManager) finally brought up the interface!
3 Likes
Well… after a reboot, I get no connection again.
So it looks like the best solution is to remove the NetworkManager-config-server package entirely?
sudo dnf remove NetworkManager-config-server
sudo systemctl restart NetworkManager
1 Like
Hey Jeff, Was that “NetworkManager-config-server” tool something you installed or did it come on the server preinstalled?
I agree that the best option would be to remove that package as we do not use it here for our servers and none of the enterprise servers I’ve worked with ever had that package installed.
Looking online :
This adds a NetworkManager configuration file to make it behave more
like the old “network” service. In particular, it stops NetworkManager
from automatically running DHCP on unconfigured ethernet devices, and
allows connections with static IP addresses to be brought up even on
ethernet devices with no carrier.
After removing that package does that resolve the issue for you?
That was installed out of the box in the ‘fully built & burned in’ package — I plugged it in, didn’t get networking at all (through the built-in 2.5G port, nor through a USB Ethernet adapter), then plugged in a monitor and did all my debugging to find that package.
Uninstalling the package with dnf remove then restarting NetworkManager solved the problem and now it gets network access on every fresh boot.
6 Likes
