8
submitted 1 month ago* (last edited 1 month ago) by baseless_discourse@mander.xyz to c/homeassistant@lemmy.world

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.

you are viewing a single comment's thread
view the rest of the comments
[-] baseless_discourse@mander.xyz 1 points 1 month ago

I have figured out the problem. Turns out although in ip a, the MAC is the same, yet in the vm, the MAC is different.

As for being assigned the same IP, it is just my stupid router... Getting a new MAC (creating a new VM) fixes the issue.

this post was submitted on 10 Aug 2024
8 points (90.0% liked)

homeassistant

11833 readers
9 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS