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?

  • Dave.@aussie.zone
    link
    fedilink
    arrow-up
    3
    ·
    11 hours ago

    It’s often not possible on other operating systems. Especially the consumer versions of a certain operating system starting with “W”, that system will refuse to have duplicate IPs.

    But essentially it’s always been possible (but, probably not preferred these days) to have redundant routes/paths on Unix systems. The way you have it now is more of a side effect of being able to do more complex network setups, like using different interfaces to talk to different subnets, or using a slow link as a backup to a fast link.

    With your current setup you should get a slow failover ability, for example if you ping some other device and then unplug your Ethernet cable, you’ll have a bit of a pause in replies and then they will start again as the stack switches to the other link.