cross-posted from: https://mander.xyz/post/16531247

I have tried to follow several tutorial to setup using either ip or nmtui:

However, the bridge inherits the MAC address of host after enslaving the host hardware enp1s0.... This causes my router to give both the host and the bridge the same ip address, making the ha instance inaccessible.

The red hat tutorial clearly show that the bridge and the host have different IP, so I was wondering if I am doing something wrong.


alternatively, I can set the home assistant vm to run in NAT and port forward from host, but I have several device that communicate over different ports. So it would be annoying to forward all these ports. Not to mention, many appliances don’t have documentation about the ports they use.

I can also potentially use virtualbox, but it is not well supported on silverblue, especially with secureboot enabled.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    The bridged adapter can’t have the same MAC address. Two of the same MAC address can’t exist in the same IP space, else the router can’t route packets to them. Just change the bridged adapter’s MAC address to something else.

    Is there an issue with using Docker for this? Seems like an easier route.

    Edit: I’d venture a guess that if in NAT mode, the MAC address might stay the same, which wouldn’t be an issue. Are you positive it’s actually using bridged mode?

    • baseless_discourse@mander.xyzOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Two of the same MAC address can’t exist in the same IP space, else the router can’t route packets to them.

      Yes, this seems to be my problem, both the host and the vm got the same IP, and I think I cannot send any traffic to either my host or vm. So my router is probably confused, as you suggested.

      Is there an issue with using Docker for this?

      I forgot to mention this, docker indeed work. However, ha requires a privileged docker running as root, which means ha essentially runs as root on the host.

      This is fine on dedicated hardware, but as my server have other infrastructure on there, running ha as root can be a security risk.