Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
You're saying one VM was cloned from the other. I could imagine a DHCP client saving leases to disk (they can have pretty long validity periods), and if the box was assigned the .106 address at any point and then cloned, the cloned machine would probably try to take that address, in other words ARP the address to determine if it's taken, and if so, fall back to some other thing. I would have expected an APIPA address but 172.x.y.z is not out of the question depending on config.
Also, if your bridge has an interface connected to e.g. another ISP-provided router then it would expose any DHCP server running behind that interface to your VMs, creating a race.
Agreed. I've seen 172 addresses self-assigned before, even though the apipa spec says it should be 169.254.x.x.