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 16 hours ago by ReluctantMuskrat@lemmy.world to c/linux@lemmy.ml

19 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

[–] LordCrom@lemmy.world 2 points 8 hours ago (1 children)

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?

[–] ReluctantMuskrat@lemmy.world 1 points 6 hours ago

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.¯\_(ツ)_/¯