Single Machine error - ARP

Can anyone help me troubleshoot an ARP error between a Windows & Linux machine? I’ve narrowed things down to I believe the ARP, however clearing cache/routes doesn’t resolve the issue. SSH works from a Linux machine behind the same NAT as the windows to the remote server.

Here’s the tcpdump where things fail:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ztzlgeqega, link-type EN10MB (Ethernet), capture size 262144 bytes
00:59:56.805636 IP 172.27.121.252.54536 > 172.27.24.40.22: Flags [S], seq 376332431, win 63480, options [mss 2760,nop,wscale 8,nop,nop,sackOK], length 0
00:59:56.805756 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
00:59:57.798019 IP 172.27.121.252.54536 > 172.27.24.40.22: Flags [S], seq 376332431, win 63480, options [mss 2760,nop,wscale 8,nop,nop,sackOK], length 0
00:59:57.798080 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
00:59:58.803347 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
00:59:59.816919 IP 172.27.121.252.54536 > 172.27.24.40.22: Flags [S], seq 376332431, win 63480, options [mss 2760,nop,wscale 8,nop,nop,sackOK], length 0
00:59:59.816990 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
01:00:01.637928 ARP, Request who-has 172.27.24.40 (a2:b9:4c:1d:ac:05) tell 172.27.121.252, length 28
01:00:01.637963 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28
01:00:01.843370 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
01:00:01.939349 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:02.626896 ARP, Request who-has 172.27.24.40 (a2:b9:4c:1d:ac:05) tell 172.27.121.252, length 28
01:00:02.626933 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28
01:00:02.963362 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:03.636286 ARP, Request who-has 172.27.24.40 (a2:b9:4c:1d:ac:05) tell 172.27.121.252, length 28
01:00:03.636330 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28
01:00:03.822692 IP 172.27.121.252.54536 > 172.27.24.40.22: Flags [S], seq 376332431, win 63480, options [mss 2760,nop,wscale 8,nop,nop,sackOK], length 0
01:00:03.822755 IP 172.27.24.40.22 > 172.27.121.252.54536: Flags [S.], seq 3537936805, ack 376332432, win 63480, options [mss 2760,nop,nop,sackOK,nop,wscale 7], length 0
01:00:03.987346 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:07.827419 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:08.851395 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:09.875399 ARP, Request who-has 172.27.121.252 tell 172.27.24.40, length 28
01:00:11.827644 ARP, Request who-has 172.27.24.40 tell 172.27.121.252, length 28
01:00:11.827685 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28
01:00:12.628201 ARP, Request who-has 172.27.24.40 tell 172.27.121.252, length 28
01:00:12.628233 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28
01:00:13.630207 ARP, Request who-has 172.27.24.40 tell 172.27.121.252, length 28
01:00:13.630242 ARP, Reply 172.27.24.40 is-at a2:b9:4c:1d:ac:05, length 28

Corresponding to this on SSH:

% ssh user@172.27.24.40                                                                                            20:55:01
ssh: connect to host 172.27.24.40 port 22: Resource temporarily unavailable

Hello,
make sure all your devices are updated to 1.6.5.
Do the steps here resolve it? Coma Bug Update
The arp thing might be a red herring.

1 Like

Hey,
Appreciate the suggestions, I saw the Coma Bug update but I don’t think it applies, none of my planets are relayed:

200 peers
<ztaddr>   <ver>  <role> <lat> <link> <lastTX> <lastRX> <path>
52ce82a3d9 1.6.4  LEAF      -1 RELAY
61d294b9cb -      PLANET  -832 DIRECT 7062     2750     50.7.73.34/9993
62f865ae71 -      PLANET  -540 DIRECT 12076    2458     50.7.252.138/9993
778cde7190 -      PLANET    49 DIRECT 50       1868     103.195.103.66/9993
93afae5963 1.6.4  LEAF      80 DIRECT 50       14686    35.222.83.92/59948
992fcf1db7 -      PLANET  -820 DIRECT 12048    2738     195.181.173.159/9993
aeaef52c73 1.6.5  LEAF       9 DIRECT 746      -148     10.0.1.117/27285
b1f48fc09e -      MOON      -1 RELAY

EDIT: Problem resolved after updating my node from 1.6.4 → 1.6.5… I’ll be sure to keep things updated in the future, this was a weird problem…

Thanks!