IP address not showing up correctly OMV5

Zitat von TechnoDadLife

For some reason the IP address that shows up in the terminal is off by one most of the time.

Only by one you're lucky, you know the windows auto negotiation ip, well I've seen that on omv as well usually a reboot seems to sort it out as well as setting a static ip.
I've shut down my test machine for now and I shall be in no rush to move to OMV5

In that case the welcome message (/etc/issue) is created before the IP address changes. The systemd unitfile that's doing that is executed after the network is up, but with DHCP this might be problematic to detect. I fear this can't be fixed somehow.

Zitat von votdev

I fear this can't be fixed somehow.

I would remove it. Just add a script to /etc/update-motd.d that will show ip address on login of any user or recommend typing: ip a to get it.

Zitat von ryecoaaron

I would remove it. Just add a script to /etc/update-motd.d that will show ip address on login of any user or recommend typing: ip a to get it.

But the MOTD is only displayed after login. This is not helpful if you simply want to see the IP addresses after bootup. Think about a headless setup where the user doesn't know the IP address. In this case he simply has to plug a monitor. For MOTD he also needs to plug a keyboard and log in.

A better solution would be to check if systemd has a feature to update a unit after an event occurs, e.g. IP address changes. Something like already exists for .mount unit files.

Zitat von votdev

But the MOTD is only displayed after login. This is not helpful if you simply want to see the IP addresses after bootup. Think about a headless setup where the user doesn't know the IP address. In this case he simply has to plug a monitor. For MOTD he also needs to plug a keyboard and log in.

I know that but the message (or issue) is already on the screen and probably wrong or not useful. You need a keyboard to refresh it. Most people should be able to get their IP from their router. If not, plugin a keyboard in is generally easier than plugging in a monitor.

Zitat von votdev

A better solution would be to check if systemd has a feature to update a unit after an event occurs, e.g. IP address changes. Something like already exists for .mount unit files.

This still wouldn't fix the problem that the message is already on the screen. Nothing is going to update that that I know of.

Zitat von ryecoaaron

This still wouldn't fix the problem that the message is already on the screen. Nothing is going to update that that I know of.

Oh yes, that's what i thought yesterday when thinking about this, but forgot when writing the post today.