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

homeassistant

12045 readers
10 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
GreatAlbatross@feddit.uk
8
[Question] Setting up a bridged network for HomeAssistant in KVM Fedora (mander.xyz)
submitted 3 months ago* (last edited 3 months ago) by baseless_discourse@mander.xyz to c/homeassistant@lemmy.world
11 comments fedilink hide all child comments
 

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 3 months ago (1 children)

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.