Post #3109192

2026-06-05 00:50 UTC

I’m at a loss as to how this would work consistently. If 2 interfaces share an IP without bonding, then only 1 would answer the ARP request from anothet host trying to establish a connection. If your system allows same static on 2 devices on same land, then other hosts talk to whoever establishes a session or answers the ARP request. I’m curious why you would want this at all?

Replies (1)

@ReluctantMuskrat@lemmy.world 2026-06-05 03:02

In terms of why, all I really want is for the machine to have the same, consistent ip address. Since it’s one of my networks dns and dhcp servers, I want it always available with the same ip. It’s hard-wired but has wifi, so in theory if the eth connection or switch it’s attached to dies, the wifi connection can kick in and it can still serve the network if it still has the same ip address, otherwise the wifi connection is no benefit. Since I didn’t know I could assign both connections the same ip address and still be functional, I originally setup a script that monitors network status and disables the wifi if eth is active and then re-enables the wifi if the eth connection drops. This works well on my two servers with one exception… my dvr scheduling/recording services don’t work properly when the wifi adapter is disabled. Not sure why but that’s how I stumbled on this setup with both active with the same ip and realized everything just seemed to work.¯\_(ツ)_/¯

Open ##3111162