Home Assistant losing IP Address

1

Hi,

I’m running Home Assistant on a NUC I3 on ESXI (VMDK VMWare Workstation)
But i’m having alot of problems with the network, most of the times after a reboot in 5 to 10 minutes Hassio loses it’s IP address.
When i look at the console screen i see these messages.
[ 1040.216660] hassio: port 39vethd7687770) entered disabled state
[ 1040.224633] veth3ec88f5: renamed from eth0
[ 1040.243182] hassio: port 39vethd7687770) entered disabled state
…
Sometimes, when i’m lucky, after 5-20 reboots it keeps on running, until i have to reboot because of a major config change or an update.

Anyone an idea on how to fix this?

EDIT: when i look at the console and do “ip a” i see all the IP’s including the IPV4 i need.
But below it has a timer “valid_lft” counting down, and as soon as it reaches 0, IP address is gone and only a IPV6 address is visible and also counting down from 7030 sec.

EDIT2: i just set the lease time to 31536000 (one year) for the Home-Assistant reserve in my DHCP server.
Timer is now counting down from 31536000…
Somehow Hassio doesn’t request (or receives) a IP address from the DHCP server when the counter reaches 0.

crossing fingers that it keeps working

EDIT3: Couple of hours passed, and still working.
Looks like it’s a DHCP request problem (Only HASSIO is losing it’s IP, all other devices don’t have this problem).

2

Why are you using DHCP?

Set a static IP address. See step 4 of the getting started instructions.

3

Hi Tom,

It’s just the way i’ve setup my network, everything uses dhcp except the gateway.
Important devices have a reserved lease, regular devices get IP’s at random.

But the work-around seems to work, it’s still online (and counting down) and i’m 100% sure i’ll have to reboot again before the countdown reaches 0 and will restart the countdown.

Still strange that it doesn’t re-request a DHCP lease when the lease ends.