Anyone else having an issue with your adapters no longer showing up in HA? I’ve had these setup for months, but now no longer seem to want to show up within HassOS. I’ve tried deleting and recreating
Wondering what changed causing adapters not to be available to the HA container?
seems it maybe something with os 11
opened 08:25PM - 22 Oct 23 UTC
closed 08:56PM - 24 Oct 23 UTC
bug
board/raspberrypi
### Describe the issue you are experiencing
In my pre-11.0 setup there was a … secondary VLAN-enabled adapter (based on `eth0`) to isolate the network traffic. After upgrading to 11.0 the adapter disappeared. After re-adding it manually using `nmcli con add type vlan con-name end0@vlan2 dev end0 id 2 ip4 192.168.2.20/23 gw4 192.168.2.1`, everything works again.
### What operating system image do you use?
rpi4-64 (Raspberry Pi 4/400 64-bit OS)
### What version of Home Assistant Operating System is installed?
11.0
### Did you upgrade the Operating System.
Yes
### Steps to reproduce the issue
1. have second network adapter with VLAN enabled
2. upgrade to HassOS 11.0
3. the secondary adapter is lost
### Anything in the Supervisor logs that might be useful for us?
I did not found anything relevant.
### Anything in the Host logs that might be useful for us?
This is how the interface addition appears in the logs:
```txt
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.2597] manager: (end0.2): new VLAN device (/org/freedesktop/NetworkManager/Devices/38)
Oct 22 20:13:56 homeassistant kernel: 8021q: 802.1Q VLAN Support v1.8
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.2801] device (end0.2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.2941] audit: op="connection-add" uuid="b3e062e9-ddfe-48d4-8b56-3e595bdc8fa8" name="end0@vlan2" pid=23539 uid=0 result="success"
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.2965] device (end0.2): carrier: link connected
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.2990] device (end0.2): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3014] policy: auto-activating connection 'end0@vlan2' (b3e062e9-ddfe-48d4-8b56-3e595bdc8fa8)
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3031] device (end0.2): Activation: starting connection 'end0@vlan2' (b3e062e9-ddfe-48d4-8b56-3e595bdc8fa8)
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3035] device (end0.2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3051] device (end0.2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3063] device (end0.2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant systemd-resolved[434]: end0.2: Bus client set default route setting: no
Oct 22 20:13:56 homeassistant systemd-resolved[434]: end0.2: Bus client set MulticastDNS setting: yes
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.3308] device (end0.2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 22 20:13:56 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.4162] device (end0.2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.4172] device (end0.2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 22 20:13:56 homeassistant NetworkManager[443]: <info> [1698005636.4192] device (end0.2): Activation: successful, device activated.
Oct 22 20:13:56 homeassistant systemd-resolved[434]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Oct 22 20:14:06 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 22 20:14:23 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-4fdee32d3114cf9e590d4bb416bd7ad3f24373d034191134820bc5547151eaa9-runc.mR0iAq.mount: Deactivated successfully.
Oct 22 20:14:40 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-b429a79c0b977ae23bcc22c5ed48fdcb3255f05cd1707d1a15a76221895a5d88-runc.HPLFgF.mount: Deactivated successfully.
Oct 22 20:15:25 homeassistant NetworkManager[443]: <info> [1698005725.7192] audit: op="connection-update" uuid="b3e062e9-ddfe-48d4-8b56-3e595bdc8fa8" name="end0@vlan2" args="connection.timestamp" pid=23758 uid=0 result="success"
```
### System information
_No response_
### Additional information
_No response_
Looks like there was an interface rename within the HA container from eth0 to end0
As well you can now use ‘ha’ to create a new network vlan interface immediately without rebooting and without the use of nmcli
ha network vlan end0 3 --ipv4-method static --ipv4-nameserver 192.168.2.6 --ipv4-address 192.168.3.14/28 --ipv4-gateway 192.168.3.1
