I’m running Linux Mint on a home server that happens to run pihole. Since it’s both a dhcp and dns server for my network, it has a static ip address. It has an ethernet connection as well as wifi and it’s always been my understanding that you can’t have two network interfaces sharing the same IP address, so I’ve been looking into ways to have one network adapter enabled and the other disabled and then if the network connection of the active device is lost, the other re-enables with the same IP address and disables the other device. This mostly work.

However while debugging one bit of software that seems to have a problem with me disabling my wifi adapter, I inadvertently enabled both the eth and wifi connections while each have the same, manually assigned ip address and everything so far just seems to work. I didn’t think this was possible and I’m wondering, should I expect problems? I can connect to the machine remotely fine, pihole and dvr services installed on the box work. Is there any reason to believe this won’t work?

  • ReluctantMuskrat@lemmy.worldOP
    1·
    21 hours ago

    I definitely don’t intend to run anything core over wifi… my home servers all have direct eth connections but also have WiFi hardware that came with them. The WiFi is really just a backup in case the switch they’re connected to dies. And since it turns out the eth and WiFi devices can share the same ip, having a resilient backup was easier than I expected.

    In terms of size, the networks has about 70 devices and I’ve got 2 pi hole servers running dhcp & dns services, including unbound, all with ups’ and a generator backup so it’s about as resilient as I can make it.