Homeassistant only accessible on server machine

Installation
1

I installed HA on my Linux desktop using the existing disk image and the Virtual Machine Manager (KVM) of Linux MInt,

Everything works perfectly as long as I access HA in a browser via IP address or homeassistant.local:8123 - but only if I do it on my desktop (i.e. the server itself)

As soon as I try to do the same with my laptop or phone (connected in home WLAN), than the page cannot be reached.

I suspect, that the reason may be that the Virtual Machine Manager assigned an IP Address (192.168.122.167), that is in a different subnet, than the rest of all my sensors and wifi clients (192.18.10.xxx)

Also the HA server (192.168.122.167) does not show up on my router (Fritzbox).

Does anybody have an idea how to solve this?
I tried to change the IP addres of HA in Systems - Networking ā€“ but to no avail.

2

KVM, Donā€™t let KVM act as a DHCP, And make sure it uses a Bridge-Network interface for your VM
So Read up On KVM, use Google or their dedicated Forum

3

Thanks for the reply.

The VM is using virbr0 as bridge network.
Unfortunately I cannot disable the DHCP for KVM - even after studying the available material.

If I enable xml editing and try to apply my changes, it always reverts back to the default :frowning:

4

Obviously not a bridge on your Host, but most likely a bridge inside the KVM

5

That would indicate you are running a ā€˜Privateā€™ Bridge, you want to ensure you are running a ā€˜Publicā€™ Bridge. The Home Assistant server should get an IP Address in the same subnet as your Host system via the DHCP Server the host system gets it IP Address (probably your router).

6

Thanks guys - the ā€œbridgeā€ is definitely the problem - but unfortunately I have no idea what I am doing wrong.

I am following the HA Linux installation guide word by word, and the only network name that is accepted is the virbr0 - and that ends in what I described above.

I just tried the installation under VirtualBox and that works as advertised - so I guess I am stuck with that for the moment. :frowning:

7

Which also made me wonder why you have chosen KVM :slight_smile: , i previously used VMWare in Linux, and also in Windows

Below is a similar case as yours (tons of them out there :wink: )
https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/kvm-how-to-make-vm-get-ip-from-same-dhcp-as-host-4175696914/#post6261871 .

Basically KVM creates itā€™s own virtual network, and you have to bypass this, by creating the bridge in Linux( Your Hostā€™s Nic ) and point to that , as explained in the Url

1 Like
8

In a university dorm your local WiFi is provided by the university and is. Likely you only route to the larger Internet. I would simply use what they give you and let you HA instance obtain an IP address from the universityā€™s DHCP server.

When debugging networking, my first step is to strip away all the complexity I can and make it work in the most conventional manner possible. Them later AFTER it works add back in whatever you like. Iā€™d get rid of the local router but the liniux PC on the university WiFi and the VM to use ā€œbridgeā€ mode for networking. That has a good chance of working one first attempt. as everything is on one subnet.

Later experiment with a more complex setup.

9

Thanks for your input - but I hate to admit it - with 65 years old, my university days are long gone :slight_smile:

I think you may have missinterpreted my description - everyhing is in my house and I donā€™t even access the internet when I try to pull up Homeassistant on my phone - it is all via my local WLAN.

10

kvm is not the problem here, you can set up tap bridge based networking for it just fine - you just need to do it, rather than taking the simply defaults (userspace networking, thatā€™s sufficient to give clients internet access, but nothing else).

11

Who said it was ? , Seems like you not only copy/quote half a sentence, You also donā€™t read half of what you reply to ā€¦ redundant bullock, or are you just bored