Migration from eth0 to end0 for DHCP

[MiguelAngelLV]

Problem/Motivation

When update Home Assistant Supervisor to 11.0, eth0 change to end0, so, Adguard select a random network device (Docker0 in my case) instead end0 and it does not work fine

Expected behavior

After update to Supervisor 11.0, Adguard set end0 instead of eth0

Actual behavior

Set a random network device

Steps to reproduce

• With supervisor 10.X, configure adguard with DHCP server and eth0
• Update to supervisor 11.X

[LoermansA]

I seem to be experiencing the same problem. I've had to revert to my networks default DHCP server to get everything up and running again.

[dredjohn21]

I also couldn’t figure out how to solve this and had to revert to my routers dhcp

[MiguelAngelLV]

I also couldn’t figure out how to solve this and had to revert to my routers dhcp

Only need set end0 in network device:

[LoermansA]

I also couldn’t figure out how to solve this and had to revert to my routers dhcp

Only need set end0 in network device:

Oh wow, now I feel really silly! Awesome, thanks for your reply!

[sinclairpaul]

I think we can close this out, it's likely caused by a breaking change in the Home Assistant OS latest release and listed in the release notes - https://github.com/home-assistant/operating-system/releases/tag/11.0