IP addresses in HAOS VM NAT:ed to docker...?

Configuration
1

I moved from Docker ti Home Assistant OS VM (Releases · home-assistant/operating-system · GitHub), to make discovery work by assigning a second nic in a different VLAN.

Now it seems like HAOS is using docker internally and maps my IP-addresses to something like 172.30.33.0, and there is no direct connection from my own networks.

The first hop is alwas the internal HAOS created network:
[core-ssh ~]$ traceroute 10.1.15.1
traceroute to 10.1.15.1 (10.1.15.1), 30 hops max, 46 byte packets
1 home-assistant.local.hass.io (172.30.32.1) 0.012 ms 0.007 ms 0.006 ms

What do I need to do to get at direct connection…??

Welcome to the Home Assistant command line.

System information

  • IPv4 addresses for eth0: 192.168.1.14/24*

  • IPv4 addresses for eth1: 10.1.15.4/24*

  • OS Version: Home Assistant OS 7.5*

  • Home Assistant Core: 2022.3.5*

  • Home Assistant URL: http://homeassistant.local:8123*

  • Observer URL: http://homeassistant.local:4357*
    [core-ssh ~]$ ifconfig
    eth0 Link encap:Ethernet HWaddr 02:42:AC:1E:21:00

  •      inet addr:172.30.33.0  Bcast:172.30.33.255  Mask:255.255.254.0*

  •      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1*

  •      RX packets:280498 errors:0 dropped:0 overruns:0 frame:0*

  •      TX packets:1336 errors:0 dropped:0 overruns:0 carrier:0*

  •      collisions:0 txqueuelen:0*

  •      RX bytes:72582122 (69.2 MiB)  TX bytes:526606 (514.2 KiB)*

lo Link encap:Local Loopback

  •      inet addr:127.0.0.1  Mask:255.0.0.0*

  •      UP LOOPBACK RUNNING  MTU:65536  Metric:1*

  •      RX packets:4 errors:0 dropped:0 overruns:0 frame:0*

  •      TX packets:4 errors:0 dropped:0 overruns:0 carrier:0*

  •      collisions:0 txqueuelen:1000*

  •      RX bytes:530 (530.0 B)  TX bytes:530 (530.0 B)*
2

Please expose your actual issue (XY problem - Wikipedia)

You’re pinging for the SSH addon, apparently, which is itself a separate docker container inside HAOS, unrelated to HA proper besides sharing some folders.

3

The issue is that HAOS is on VLAN1 and cannot discover devices on VLAN2, although routning/communication otherwise works fine. Instead of fiddeling with mDNS a lot of threads is suggesting just to add a second nic connected to VLAN2 to HAOS, and that is what I have done, but it still does not discover devices on VLAN2.

4

Are your VM NICs bridged?
If they are nated, multicast discover packets won’t get through…

5

They are not nated. Thats why I added a second nic for a direct connection vo VLAN2.

6

Got it to work. Found a setting where I could enable broadcast also for the second interface.