Possible to have both Wi-Fi and Ethernet connected to the same network?Change ip addr label in LinuxHow to create permanent ip alias belonging to different subnets in CentosConfusion about interfaces, iptables, connections, local connectionHow do I fix Debian that refuses to connect to the internet in VirtualBox?Can't figure out why Ethernet packets are ignoredWifi does not work in laptop 1 when laptop 2 is connectedScript to create macvlan bridge on the host doesn't work unless it's run twiceDebian8 server : Can't resolve IP adresses or DNSHow to find the network namespace of a veth peer ifindex?Conflict between wlan and ethernet board
What about the virus in 12 Monkeys?
Venezuelan girlfriend wants to travel the USA to be with me. What is the process?
Is it logically or scientifically possible to artificially send energy to the body?
Forgetting the musical notes while performing in concert
What is a romance in Latin?
Can my sorcerer use a spellbook only to collect spells and scribe scrolls, not cast?
How badly should I try to prevent a user from XSSing themselves?
Am I breaking OOP practice with this architecture?
Zip/Tar file compressed to larger size?
Could the museum Saturn V's be refitted for one more flight?
Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?
What exploit Are these user agents trying to use?
What does “the session was packed” mean in this context?
How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?
How can saying a song's name be a copyright violation?
Avoiding direct proof while writing proof by induction
Watching something be piped to a file live with tail
What are some good books on Machine Learning and AI like Krugman, Wells and Graddy's "Essentials of Economics"
Size of subfigure fitting its content (tikzpicture)
Is the myth that if you can play one instrument, you can learn another instrument with ease true?
Why do bosons tend to occupy the same state?
Im going to France and my passport expires June 19th
iPad being using in wall mount battery swollen
Why is consensus so controversial in Britain?
Possible to have both Wi-Fi and Ethernet connected to the same network?
Change ip addr label in LinuxHow to create permanent ip alias belonging to different subnets in CentosConfusion about interfaces, iptables, connections, local connectionHow do I fix Debian that refuses to connect to the internet in VirtualBox?Can't figure out why Ethernet packets are ignoredWifi does not work in laptop 1 when laptop 2 is connectedScript to create macvlan bridge on the host doesn't work unless it's run twiceDebian8 server : Can't resolve IP adresses or DNSHow to find the network namespace of a veth peer ifindex?Conflict between wlan and ethernet board
I am running Arch Linux (on a Raspberry Pi 3) and tried to connect both the Ethernet and the Wi-Fi to the same network. route
shows me the following:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 1024 0 0 eth0
default gateway 0.0.0.0 UG 1024 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 eth0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 wlan0
ip addr
shows me the following:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 85717sec preferred_lft 85717sec
inet6 fe80::ba27:ebff:fee4:4f60/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 85727sec preferred_lft 85727sec
inet6 fe80::ba27:ebff:feb1:1a35/64 scope link
valid_lft forever preferred_lft forever
Both wlan0
and eth0
interfaces were able to get an IP address from the router.
But it turns out that only one of these interfaces ever works. The other interface cannot be pinged and is not connectable. Usually it's the Ethernet that works but sometimes it's the Wi-Fi.
What's happening? What can I do to make this work?
networking arch-linux wifi network-interface ethernet
add a comment |
I am running Arch Linux (on a Raspberry Pi 3) and tried to connect both the Ethernet and the Wi-Fi to the same network. route
shows me the following:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 1024 0 0 eth0
default gateway 0.0.0.0 UG 1024 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 eth0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 wlan0
ip addr
shows me the following:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 85717sec preferred_lft 85717sec
inet6 fe80::ba27:ebff:fee4:4f60/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 85727sec preferred_lft 85727sec
inet6 fe80::ba27:ebff:feb1:1a35/64 scope link
valid_lft forever preferred_lft forever
Both wlan0
and eth0
interfaces were able to get an IP address from the router.
But it turns out that only one of these interfaces ever works. The other interface cannot be pinged and is not connectable. Usually it's the Ethernet that works but sometimes it's the Wi-Fi.
What's happening? What can I do to make this work?
networking arch-linux wifi network-interface ethernet
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What doesarp
show on each side. What doestcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?
– Mikel
Apr 29 '17 at 16:25
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
From another machine on192.168.1.0/24
? Please addarp
output to your question.
– Mikel
Apr 29 '17 at 16:28
1
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36
add a comment |
I am running Arch Linux (on a Raspberry Pi 3) and tried to connect both the Ethernet and the Wi-Fi to the same network. route
shows me the following:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 1024 0 0 eth0
default gateway 0.0.0.0 UG 1024 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 eth0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 wlan0
ip addr
shows me the following:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 85717sec preferred_lft 85717sec
inet6 fe80::ba27:ebff:fee4:4f60/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 85727sec preferred_lft 85727sec
inet6 fe80::ba27:ebff:feb1:1a35/64 scope link
valid_lft forever preferred_lft forever
Both wlan0
and eth0
interfaces were able to get an IP address from the router.
But it turns out that only one of these interfaces ever works. The other interface cannot be pinged and is not connectable. Usually it's the Ethernet that works but sometimes it's the Wi-Fi.
What's happening? What can I do to make this work?
networking arch-linux wifi network-interface ethernet
I am running Arch Linux (on a Raspberry Pi 3) and tried to connect both the Ethernet and the Wi-Fi to the same network. route
shows me the following:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 1024 0 0 eth0
default gateway 0.0.0.0 UG 1024 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 eth0
gateway 0.0.0.0 255.255.255.255 UH 1024 0 0 wlan0
ip addr
shows me the following:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 85717sec preferred_lft 85717sec
inet6 fe80::ba27:ebff:fee4:4f60/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:27:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 85727sec preferred_lft 85727sec
inet6 fe80::ba27:ebff:feb1:1a35/64 scope link
valid_lft forever preferred_lft forever
Both wlan0
and eth0
interfaces were able to get an IP address from the router.
But it turns out that only one of these interfaces ever works. The other interface cannot be pinged and is not connectable. Usually it's the Ethernet that works but sometimes it's the Wi-Fi.
What's happening? What can I do to make this work?
networking arch-linux wifi network-interface ethernet
networking arch-linux wifi network-interface ethernet
edited 2 days ago
GAD3R
27.9k1958114
27.9k1958114
asked Apr 29 '17 at 15:51
rityzmonrityzmon
1585
1585
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What doesarp
show on each side. What doestcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?
– Mikel
Apr 29 '17 at 16:25
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
From another machine on192.168.1.0/24
? Please addarp
output to your question.
– Mikel
Apr 29 '17 at 16:28
1
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36
add a comment |
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What doesarp
show on each side. What doestcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?
– Mikel
Apr 29 '17 at 16:25
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
From another machine on192.168.1.0/24
? Please addarp
output to your question.
– Mikel
Apr 29 '17 at 16:28
1
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What does
arp
show on each side. What does tcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?– Mikel
Apr 29 '17 at 16:25
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What does
arp
show on each side. What does tcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?– Mikel
Apr 29 '17 at 16:25
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
From another machine on
192.168.1.0/24
? Please add arp
output to your question.– Mikel
Apr 29 '17 at 16:28
From another machine on
192.168.1.0/24
? Please add arp
output to your question.– Mikel
Apr 29 '17 at 16:28
1
1
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36
add a comment |
1 Answer
1
active
oldest
votes
As you have found out, from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
The routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap.
The advised solution for having more than one interface connected to the same network is to aggregate them together in a bridge interface.
The bridge interface will "own" the IP address, and the actual real interfaces are grouped as a virtual single entity under br0
.
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0
Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f362133%2fpossible-to-have-both-wi-fi-and-ethernet-connected-to-the-same-network%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As you have found out, from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
The routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap.
The advised solution for having more than one interface connected to the same network is to aggregate them together in a bridge interface.
The bridge interface will "own" the IP address, and the actual real interfaces are grouped as a virtual single entity under br0
.
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0
Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
add a comment |
As you have found out, from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
The routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap.
The advised solution for having more than one interface connected to the same network is to aggregate them together in a bridge interface.
The bridge interface will "own" the IP address, and the actual real interfaces are grouped as a virtual single entity under br0
.
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0
Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
add a comment |
As you have found out, from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
The routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap.
The advised solution for having more than one interface connected to the same network is to aggregate them together in a bridge interface.
The bridge interface will "own" the IP address, and the actual real interfaces are grouped as a virtual single entity under br0
.
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0
Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
As you have found out, from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
The routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap.
The advised solution for having more than one interface connected to the same network is to aggregate them together in a bridge interface.
The bridge interface will "own" the IP address, and the actual real interfaces are grouped as a virtual single entity under br0
.
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0
Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
edited May 1 '17 at 6:00
answered Apr 29 '17 at 21:54
Rui F RibeiroRui F Ribeiro
41.9k1483142
41.9k1483142
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
add a comment |
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
But still with the bridge, in most topologies, only one of them will wind up getting used because the other one will be shut down by spanning tree — or if spanning tree is turned off then you will have a devastating loop in the network.
– Celada
May 1 '17 at 8:55
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
@Celada They end up being a single entity, and work quite well. I have had such setup working for years to create a single entity out of my wireless and cabled network at home to be able to stream from wireless to my Apple TV (in the wired network), and it works beautifully.
– Rui F Ribeiro
May 1 '17 at 9:02
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
it talks stp by default, at home my switch is not smart enough to understand it.
– Rui F Ribeiro
May 1 '17 at 9:11
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f362133%2fpossible-to-have-both-wi-fi-and-ethernet-connected-to-the-same-network%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I assume IPv4? It works on my Ubuntu desktop after ARP starts working. What address are you pinging from? What address are you pinging? What does
arp
show on each side. What doestcpdump -i <interface> -v arp
show on all relevant interfaces on both sides? Can you get a packet capture on the switch/router?– Mikel
Apr 29 '17 at 16:25
Yes, I'm using IPv4. I'm pinging192.16.1.103 and 192.168.1.102, the two IP addresses assigned.
– rityzmon
Apr 29 '17 at 16:27
From another machine on
192.168.1.0/24
? Please addarp
output to your question.– Mikel
Apr 29 '17 at 16:28
1
See also lwn.net/Articles/45373
– Mikel
Apr 29 '17 at 16:36