Forget HA (for a while) and focus on the IP address problem. Start from scratch with a new VM, and/or inspect one of your VM's where the networking works. Find the difference.
this post was submitted on 03 Nov 2023
14 points (88.9% liked)
Selfhosted
40445 readers
993 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Could it be that you need to run the VM network in NAT mode, instead of a "Bridge" mode?
Please note, I have little experience in troubleshooting these, I'm just spitballing ideas here...
No, then the VMs would get their own subnet. You want the NIC bridged so that the router actually sees the VMs.
Gotcha. I learned something new. Thanks :)
output from "nmcli device status" command:
DEVICE TYPE STATE CONNECTION
virbr0 bridge connected virbr0
so i assume its in bridge mode?
Not an expert, just something I did and learned from; does the hardware you're running on have more than one ethernet port (enp#...)? Is it possible you've selected the wrong one?
Also I notice my VMs in proxmox have the bridge nomenclature of vmbr0 (not virb0). Perhaps something there?
Just throwing ideas out there, I'm pretty new at this.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HA | Home Assistant automation software |
| ~ | High Availability |
| IP | Internet Protocol |
| NAT | Network Address Translation |
3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #261 for this sub, first seen 3rd Nov 2023, 12:30] [FAQ] [Full list] [Contact] [Source code]
OP, are all of the working-as-expected VMs also members of the virbr0 network?
I'm thinking that this is a firewall issue on your VM host. If you DO NOT have any other working VMs then could you try disabling the firewall on the VM host and see if the VM can receive DHCP traffic.
I currently have no other VM's running. I'll see if disabling the firewall helps.
Did you ever figure out what was causing your issues?
No sadly I didn't. I got it working a few times after reconfiguring everything but it never survived a reboot.
When I ran all my vms in kvm I used macvtap for the nic type.