Linux

65604 readers

227 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Can a server's eth & wifi share the same IP address? (lemmy.world)

submitted 11 hours ago by ReluctantMuskrat@lemmy.world to c/linux@lemmy.ml

18 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] dgriffith@aussie.zone 5 points 10 hours ago (1 children)

The "metric 600" on your Wi-Fi adapter indicates to the system that it is a higher cost route than your Ethernet one. So the IP stack will prefer sending packets out via the Ethernet port.

Local devices who haven't heard from you lately will send to whatever device gives them a response to their ARP ("who has IP address X?") request first, and seeing as Ethernet is lower latency than WiFi, they will mostly use your Ethernet adapter as their target when sending data to you.

Devices that have received data from you already will have the MAC address of your Ethernet adapter in their ARP table, so they'll just send packets to that without bothering to issue an ARP request.

Devices off your subnet talk to your router, so they don't care about your MAC address, they'll just use IP to talk to your router, who will then do the ARP request and hand the packets on to your computer via whatever interface answers first.

[–] ReluctantMuskrat@lemmy.world 1 points 9 hours ago (1 children)

Thanks for the detailed explanation. Has this always been possible though? Was I just imagining that manually assigning to network adapters the same ip address wasn't possible?

[–] dgriffith@aussie.zone 3 points 6 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.