F5F Stay Refreshed Power Users Networks Ethernet is designed primarily for LAN connections.

Ethernet is designed primarily for LAN connections.

Ethernet is designed primarily for LAN connections.

G
GalacticJessi
Member
187
03-11-2016, 09:18 AM
#1
You're looking to switch your computers from Wi-Fi to LAN while keeping Wi-Fi for external connections. It's possible to manage this by configuring each device appropriately. Check the settings on each computer to ensure it uses Ethernet for local communication and switches to Wi-Fi for broader internet access. You may also need to adjust router settings if available.
G
GalacticJessi
03-11-2016, 09:18 AM #1

You're looking to switch your computers from Wi-Fi to LAN while keeping Wi-Fi for external connections. It's possible to manage this by configuring each device appropriately. Check the settings on each computer to ensure it uses Ethernet for local communication and switches to Wi-Fi for broader internet access. You may also need to adjust router settings if available.

O
ovcoming
Member
229
03-11-2016, 04:43 PM
#2
Windows usually favors LAN over Wi-Fi as long as it can connect using the IP address you specified. When both computers are linked via LAN and Wi-Fi, they typically have two distinct IP addresses. Choose the LAN IP for local connections to other machines. Ideally, keep LAN dedicated to machine-to-machine communication, assigning a separate IP range. This prevents devices from mistakenly accessing Wi-Fi when using an IP within the LAN range.
O
ovcoming
03-11-2016, 04:43 PM #2

Windows usually favors LAN over Wi-Fi as long as it can connect using the IP address you specified. When both computers are linked via LAN and Wi-Fi, they typically have two distinct IP addresses. Choose the LAN IP for local connections to other machines. Ideally, keep LAN dedicated to machine-to-machine communication, assigning a separate IP range. This prevents devices from mistakenly accessing Wi-Fi when using an IP within the LAN range.

E
Enzoline14
Member
71
03-12-2016, 01:25 AM
#3
But also lack a default gateway on the LAN side using Ethernet, so all outgoing traffic ends up via Wi-Fi. Internet access appears through Wi-Fi, but as long as your Ethernet configuration is correct, devices needing the LAN subnet will remain on Ethernet.
E
Enzoline14
03-12-2016, 01:25 AM #3

But also lack a default gateway on the LAN side using Ethernet, so all outgoing traffic ends up via Wi-Fi. Internet access appears through Wi-Fi, but as long as your Ethernet configuration is correct, devices needing the LAN subnet will remain on Ethernet.

M
Madi4067
Member
129
03-12-2016, 05:04 AM
#4
I was about to modify my entry, suggesting LAN could function as a separate network when limited to local communication.
M
Madi4067
03-12-2016, 05:04 AM #4

I was about to modify my entry, suggesting LAN could function as a separate network when limited to local communication.

I
Itzsonzy
Member
172
03-19-2016, 04:00 PM
#5
You're connecting everything to a network switch separate from the modem, and you're on Arch Linux. The IP address should stay consistent unless there are changes in routing or network configuration. Check your router settings and ensure no automatic DHCP changes are affecting it.
I
Itzsonzy
03-19-2016, 04:00 PM #5

You're connecting everything to a network switch separate from the modem, and you're on Arch Linux. The IP address should stay consistent unless there are changes in routing or network configuration. Check your router settings and ensure no automatic DHCP changes are affecting it.

W
wezenberg2
Junior Member
6
03-21-2016, 01:20 PM
#6
I determined the IP assignments by checking how the machines received their addresses. Static IPs remain fixed, while DHCP-based ones can change unless a static mapping is set on the server. You could also combine DHCP with DDNS and use hostnames, though that adds some complexity. There seems to be a method to prioritize interfaces in Arch, though I’m not certain how it works without more details.
W
wezenberg2
03-21-2016, 01:20 PM #6

I determined the IP assignments by checking how the machines received their addresses. Static IPs remain fixed, while DHCP-based ones can change unless a static mapping is set on the server. You could also combine DHCP with DDNS and use hostnames, though that adds some complexity. There seems to be a method to prioritize interfaces in Arch, though I’m not certain how it works without more details.

H
Homiak1986
Junior Member
22
03-28-2016, 06:57 AM
#7
the connections were set up automatically after linking, I believe the device lacks an interface but that might be incorrect—it could have been a Netgear 5-port switch.
H
Homiak1986
03-28-2016, 06:57 AM #7

the connections were set up automatically after linking, I believe the device lacks an interface but that might be incorrect—it could have been a Netgear 5-port switch.

M
Matt_Craft9
Junior Member
13
04-06-2016, 04:26 AM
#8
You were thinking about a management interface, which made me a bit unclear. If the switch has a DHCP server, it should be adjustable. However, I expected a simple unmanaged switch. Generally, switches don’t assign IP addresses—they’re meant for routing. If there’s no DHCP and devices are supposed to get IPs automatically, they might be using static IPs (like 169.254.x.x). In that scenario, you’d likely need to set up your own static assignments or add a DHCP server to the network.
M
Matt_Craft9
04-06-2016, 04:26 AM #8

You were thinking about a management interface, which made me a bit unclear. If the switch has a DHCP server, it should be adjustable. However, I expected a simple unmanaged switch. Generally, switches don’t assign IP addresses—they’re meant for routing. If there’s no DHCP and devices are supposed to get IPs automatically, they might be using static IPs (like 169.254.x.x). In that scenario, you’d likely need to set up your own static assignments or add a DHCP server to the network.

C
Caper
Junior Member
5
04-06-2016, 06:22 AM
#9
Alright, I'll take a look at that. Thanks!
C
Caper
04-06-2016, 06:22 AM #9

Alright, I'll take a look at that. Thanks!