Linux AP does not route ping replies to final userUsing ip addr instead of ifconfig reports “RTNETLINK answers: File exists” on DebianRouting public ipv6 traffic through openvpn tunnelNetwork connectivity trouble to non-routing multi-homed hosts?Assymetric routing problems in LINUXOutgoing masquerade address changes after adding a second interface to the bridgeRouting to different subnet via single NIC to another boxMultiple clients/APs connected over wifiIPSec - src and dst mac don't change from encrypted to decrypted packetsIs it possible to force fwmark reflection in arbitrary-TCP reply packets?Configuring Linux Mint as a Gateway
The use of multiple foreign keys on same column in SQL Server
Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?
How to say job offer in Mandarin/Cantonese?
What are the differences between the usage of 'it' and 'they'?
Python: next in for loop
Can a Warlock become Neutral Good?
What typically incentivizes a professor to change jobs to a lower ranking university?
Why can't I see bouncing of a switch on an oscilloscope?
Prove that NP is closed under karp reduction?
Can I make popcorn with any corn?
Why are electrically insulating heatsinks so rare? Is it just cost?
A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?
Languages that we cannot (dis)prove to be Context-Free
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
Service Entrance Breakers Rain Shield
Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?
In Japanese, what’s the difference between “Tonari ni” (となりに) and “Tsugi” (つぎ)? When would you use one over the other?
How is it possible to have an ability score that is less than 3?
Risk of getting Chronic Wasting Disease (CWD) in the United States?
What do you call a Matrix-like slowdown and camera movement effect?
How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?
Why doesn't H₄O²⁺ exist?
How to write a macro that is braces sensitive?
can i play a electric guitar through a bass amp?
Linux AP does not route ping replies to final user
Using ip addr instead of ifconfig reports “RTNETLINK answers: File exists” on DebianRouting public ipv6 traffic through openvpn tunnelNetwork connectivity trouble to non-routing multi-homed hosts?Assymetric routing problems in LINUXOutgoing masquerade address changes after adding a second interface to the bridgeRouting to different subnet via single NIC to another boxMultiple clients/APs connected over wifiIPSec - src and dst mac don't change from encrypted to decrypted packetsIs it possible to force fwmark reflection in arbitrary-TCP reply packets?Configuring Linux Mint as a Gateway
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am struggling with the routing in my topology. In this topology I have the following structure with 2 PCs. Each one of them has 2 different interfaces configured in different subnets:
192.162.2.10/24 (A wifi user) <-(wlp2s0-AP1-192.168.2.1/24) |PC1| (ra0-192.168.1.2/24)-> <- (wlan1-192.168.1.1/24) |PC2| (wlan0-192.168.0.2)->
From here, let's say that a wifi user connects to AP1 (at wlp2s0 interface of PC1) and gets IP 192.168.2.10. Now, from the user I execute ping 192.168.0.2, which is the wlan0 interface of PC2. Given the following routing table at PC1,
and knowing that PC2 has another routing rule that enables the ping replies to come back (using Wireshark), I can see the ping requests and replies going out and coming back at PC1's wlp2s0. However, the final user (192.168.2.10) connected to wlps0 (192.168.2.1) is not getting the replies and therefore the ping fails.
Also, I think I enabled forwarding by executing:
sudo sysctl -w net.ipv4.ip_forward=1
linux networking routing
New contributor
|
show 1 more comment
I am struggling with the routing in my topology. In this topology I have the following structure with 2 PCs. Each one of them has 2 different interfaces configured in different subnets:
192.162.2.10/24 (A wifi user) <-(wlp2s0-AP1-192.168.2.1/24) |PC1| (ra0-192.168.1.2/24)-> <- (wlan1-192.168.1.1/24) |PC2| (wlan0-192.168.0.2)->
From here, let's say that a wifi user connects to AP1 (at wlp2s0 interface of PC1) and gets IP 192.168.2.10. Now, from the user I execute ping 192.168.0.2, which is the wlan0 interface of PC2. Given the following routing table at PC1,
and knowing that PC2 has another routing rule that enables the ping replies to come back (using Wireshark), I can see the ping requests and replies going out and coming back at PC1's wlp2s0. However, the final user (192.168.2.10) connected to wlps0 (192.168.2.1) is not getting the replies and therefore the ping fails.
Also, I think I enabled forwarding by executing:
sudo sysctl -w net.ipv4.ip_forward=1
linux networking routing
New contributor
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something liketcpdump
or Wireshark on that interface shows the packets going out?
– TooTea
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago
|
show 1 more comment
I am struggling with the routing in my topology. In this topology I have the following structure with 2 PCs. Each one of them has 2 different interfaces configured in different subnets:
192.162.2.10/24 (A wifi user) <-(wlp2s0-AP1-192.168.2.1/24) |PC1| (ra0-192.168.1.2/24)-> <- (wlan1-192.168.1.1/24) |PC2| (wlan0-192.168.0.2)->
From here, let's say that a wifi user connects to AP1 (at wlp2s0 interface of PC1) and gets IP 192.168.2.10. Now, from the user I execute ping 192.168.0.2, which is the wlan0 interface of PC2. Given the following routing table at PC1,
and knowing that PC2 has another routing rule that enables the ping replies to come back (using Wireshark), I can see the ping requests and replies going out and coming back at PC1's wlp2s0. However, the final user (192.168.2.10) connected to wlps0 (192.168.2.1) is not getting the replies and therefore the ping fails.
Also, I think I enabled forwarding by executing:
sudo sysctl -w net.ipv4.ip_forward=1
linux networking routing
New contributor
I am struggling with the routing in my topology. In this topology I have the following structure with 2 PCs. Each one of them has 2 different interfaces configured in different subnets:
192.162.2.10/24 (A wifi user) <-(wlp2s0-AP1-192.168.2.1/24) |PC1| (ra0-192.168.1.2/24)-> <- (wlan1-192.168.1.1/24) |PC2| (wlan0-192.168.0.2)->
From here, let's say that a wifi user connects to AP1 (at wlp2s0 interface of PC1) and gets IP 192.168.2.10. Now, from the user I execute ping 192.168.0.2, which is the wlan0 interface of PC2. Given the following routing table at PC1,
and knowing that PC2 has another routing rule that enables the ping replies to come back (using Wireshark), I can see the ping requests and replies going out and coming back at PC1's wlp2s0. However, the final user (192.168.2.10) connected to wlps0 (192.168.2.1) is not getting the replies and therefore the ping fails.
Also, I think I enabled forwarding by executing:
sudo sysctl -w net.ipv4.ip_forward=1
linux networking routing
linux networking routing
New contributor
New contributor
edited 2 days ago
Gabriel
New contributor
asked 2 days ago
GabrielGabriel
112
112
New contributor
New contributor
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something liketcpdump
or Wireshark on that interface shows the packets going out?
– TooTea
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago
|
show 1 more comment
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something liketcpdump
or Wireshark on that interface shows the packets going out?
– TooTea
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something like
tcpdump
or Wireshark on that interface shows the packets going out?– TooTea
2 days ago
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something like
tcpdump
or Wireshark on that interface shows the packets going out?– TooTea
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago
|
show 1 more comment
0
active
oldest
votes
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
);
);
Gabriel is a new contributor. Be nice, and check out our Code of Conduct.
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%2f510482%2flinux-ap-does-not-route-ping-replies-to-final-user%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Gabriel is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel is a new contributor. Be nice, and check out our Code of Conduct.
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%2f510482%2flinux-ap-does-not-route-ping-replies-to-final-user%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
When you say that you "can see the replies coming back at PC1's wlp2s0", do you mean that something like
tcpdump
or Wireshark on that interface shows the packets going out?– TooTea
2 days ago
Yes, I'm sorry. I can see ICMP requests and replies in wireshark. Maybe these are not routed because they come through ra0? However I can see them with Wireshark at wlp2s0...
– Gabriel
2 days ago
But a similar Wireshark on the "wifi user" doesn't show the replies coming in? Does pinging 192.168.2.1 from the "wifi user" work? Is the routing on the "wifi user" set up with the right prefix length and 192.168.2.1 as the default gw?
– TooTea
2 days ago
Wireshark on an interface shows exactly what's passing through that interface (what's being fed to/read from the HW), so if you see the packets there, it means that all the forwarding/routing/firewall setup inside PC1 works fine.
– TooTea
2 days ago
Pinging from the "wifi user" to 192.168.2.1 works fine and since the wifi user's ip is given by dhcp I assume that the prefix length and gw are ok. A Wireshark instance listening in the "wifi user" interface, shows the ICMP Requests to 192.168.0.2 but not the replies, these are stuck at PC1's wlp2s0, which shows both requests and replies. Weird...
– Gabriel
2 days ago