HAOS usb3 ethernet adapter - settings not saving

Installation
1

I am trying to get a usb-ethernet adapter working so that I can put my Frigate cameras onto a different subnet to my home network.

Running HAOS on a Lenovo Tiny PC. USB3-Ethernet adapter is a Comsol UG3BAD.

  • Core 2023.12.3
  • Supervisor 2023.11.6
  • Operating System 11.2
  • Frontend 20231208.2

HAOS recognises the adapter and presents it as ENP0S20P0U5 in system - network - configure network interfaces, but it’s disabled.

If I set it to static and enter in the appropriate info I can save it, and it seems to be active in HA.

➜  ~ nmcli
Warning: nmcli (1.44.2) and NetworkManager (1.40.18) versions don't match. Restarting NetworkManager is advised.
eno1: connected to Supervisor eno1
        "eno1"
        ethernet (e1000e), 00:23:24:F7:3A:7C, hw, mtu 1500
        ip4 default
        inet4 192.168.0.33/24
        route4 192.168.0.0/24 metric 100
        route4 default via 192.168.0.1 metric 100
        inet6 fe80::84:e08c:2724:3546/64
        route6 fe80::/64 metric 1024

enp0s20f0u5: connected to Supervisor enp0s20f0u5
        "enp0s20f0u5"
        ethernet (r8152), 00:E0:4C:68:03:D7, hw, mtu 1500
        inet4 192.168.10.1/24
        route4 192.168.10.0/24 metric 101
        route4 192.168.0.1/32 metric 20101
        route4 default via 192.168.0.1 metric 20101
        inet6 fe80::ce70:f880:e68a:32cb/64
        route6 fe80::/64 metric 1024

but these settings don’t survive a hardware reboot

➜  ~ nmcli
Warning: nmcli (1.44.2) and NetworkManager (1.40.18) versions don't match. Restarting NetworkManager is advised.
eno1: connected to Supervisor eno1
        "eno1"
        ethernet (e1000e), 00:23:24:F7:3A:7C, hw, mtu 1500
        ip4 default
        inet4 192.168.0.33/24
        route4 192.168.0.0/24 metric 100
        route4 default via 192.168.0.1 metric 100
        inet6 fe80::84:e08c:2724:3546/64
        route6 fe80::/64 metric 1024

enp0s20f0u5: unavailable
        "enp0s20f0u5"
        ethernet (r8152), 00:E0:4C:68:03:D7, hw, mtu 1500

Is this something wrong in my methodology, a hardware fault, or a bug in HAOS?

2

Did you try from Settings → System → Network in the UI?

Also how are you planning on using this network?

DHCP (how?) or static IP addressing?

3

Yes - settings, system, network, configure network interfaces.

Click on tab for the new adapter, change radio button from disabled to static, enter static ip address 192.168.10.1/24, gateway address, DNS address - all under IPv4, left IPv6 as disabled.

Save, check setting using nmcli in Advanced SSH and Web terminal. Settings display as saved.

Reboot hardware (Developer tools, restart, advanced options, reboot system). Settings are gone after the reboot, interface is set as disabled, and it displays as unavailable from nmcli.

I was going to set the IP address’s statically to the alternate subnet (192.168.10.xxx) in the cameras onboard config but I’m not 100% sure on what I need to do there yet - I’ve just been stuck at step 1 getting the usb-eth interface to work.

4

A bit more info…

I had a usb wifi adapter laying around so I plugged that into the Lenovo usb port, removed the usb-ethernet adapter, set up the wifi adapter and rebooted.

Wifi adapter showing up no problem in HA networking. Tempted to run the HA server on wifi and use the eth for the cameras , but would much rather have two working eth ports.

Dunno… maybe the Comsol usb-eth adapter is incompatible with HA? Any suggestions on one that is known to work? I’m in Aus but I guess Amazon will take my money still.

5

I have the same error, I think.

i have end0 as auto for ipv4 and ipv6 and wlan0 i wanted to configure it to connect to huawei inverter, which needs to have ipv4 in the wifi interface as auto, but it won’t let me connect. i see this

nmcli device status
Warning: nmcli (1.44.2) and NetworkManager (1.40.18) versions don’t match. Restarting NetworkManager is advised.
DEVICE TYPE STATE CONNECTION
end0 ethernet connected Supervisor end0
wlan0 wifi disconnected –
p2p-dev-wlan0 wifi-p2p disconnected –

6

Problem solved (apparently).

I didn’t have the usb-eth adapter plugged into anything on the network in my initial testing, it was just hanging off the usb port of the Lenovo.

Plugged an ethernet cable into it and plugged that into my camera switch - usb-eth interface now survives a reboot.

usb-eth interface set to 192.168.10.1, cameras all set to 192.168.10.xxx, frigate config changed accordingly - all cameras work, usb-eth interface survives hardware reboots.

Maybe that was an obvious oversight, but I thought the usb-eth adapter interface should still be available and working in HAOS even if it wasn’t plugged into anything - I assume the built in eth card is still visible even if it’s not being used?