Linux does not reply to ARP request
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-1
down vote
favorite
I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).
I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):
# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2
When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0
and eth2
works fine.
This is the tcpdump
:
# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
What can cause that kind of problem?
linux networking linux-kernel arp
 |Â
show 4 more comments
up vote
-1
down vote
favorite
I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).
I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):
# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2
When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0
and eth2
works fine.
This is the tcpdump
:
# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
What can cause that kind of problem?
linux networking linux-kernel arp
1
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
e.g. usetdpdump -n -i any
inside the server. If you are talking in questions about such things astcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
â Rui F Ribeiro
Jul 19 at 13:26
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Its on different route table
â user1673206
Jul 19 at 13:49
 |Â
show 4 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).
I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):
# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2
When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0
and eth2
works fine.
This is the tcpdump
:
# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
What can cause that kind of problem?
linux networking linux-kernel arp
I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).
I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):
# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2
When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0
and eth2
works fine.
This is the tcpdump
:
# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
What can cause that kind of problem?
linux networking linux-kernel arp
edited Jul 19 at 13:33
asked Jul 19 at 13:09
user1673206
1021
1021
1
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
e.g. usetdpdump -n -i any
inside the server. If you are talking in questions about such things astcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
â Rui F Ribeiro
Jul 19 at 13:26
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Its on different route table
â user1673206
Jul 19 at 13:49
 |Â
show 4 more comments
1
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
e.g. usetdpdump -n -i any
inside the server. If you are talking in questions about such things astcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
â Rui F Ribeiro
Jul 19 at 13:26
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Its on different route table
â user1673206
Jul 19 at 13:49
1
1
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
e.g. use
tdpdump -n -i any
inside the server. If you are talking in questions about such things as tcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.â Rui F Ribeiro
Jul 19 at 13:26
e.g. use
tdpdump -n -i any
inside the server. If you are talking in questions about such things as tcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.â Rui F Ribeiro
Jul 19 at 13:26
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Its on different route table
â user1673206
Jul 19 at 13:49
Its on different route table
â user1673206
Jul 19 at 13:49
 |Â
show 4 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457215%2flinux-does-not-reply-to-arp-request%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
â slmâ¦
Jul 19 at 13:25
e.g. use
tdpdump -n -i any
inside the server. If you are talking in questions about such things astcpdump
or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.â Rui F Ribeiro
Jul 19 at 13:26
thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
â user1673206
Jul 19 at 13:34
Why is the route for eth0 missing?
â Isaac
Jul 19 at 13:45
Its on different route table
â user1673206
Jul 19 at 13:49