Ubuntu 22.04 TCP Retransmission After Successful Socket ARP

Ubuntu Support Template

Ubuntu Version:
22.04 LTS

Problem Description:
I attempted to connect to the lower-level machine using a socket. However, after about ten minutes of connection, the lower-level machine requested an ARP. After successfully responding to the ARP request, when I subsequently requested data from the lower-level machine, it triggered a retransmission, causing the lower-level machine to remain unresponsive. When testing on Windows, I observed that Windows also triggers an ARP request, but it continues to function normally.

Screenshots or Error Messages:
This is the report I obtained after executing tcpdump.

14:03:04.794499 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863859:863881, ack 41104299, win 63867, length 22 
14:03:04.794510 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863859:863881, ack 41104299, win 63867, length 22 
14:03:04.795042 enp3s0 P IP 192.168.1.11.cisco-sccp > rubik.36371: Flags [P.], seq 41104299:41105346, ack 863881, win 2810, length 1047 
14:03:04.795042 bridge0 In IP 192.168.1.11.cisco-sccp > rubik.36371: Flags [P.], seq 41104299:41105346, ack 863881, win 2810, length 1047 
14:03:04.824835 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863881:863903, ack 41105346, win 63867, length 22 
14:03:04.824844 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863881:863903, ack 41105346, win 63867, length 22 
14:03:04.825422 enp3s0 B ARP, Request who-has rubik tell 192.168.1.11, length 46 14:03:04.825428 wlx1c4bd681b57e Out ARP, Request who-has rubik tell 192.168.1.11, length 46 
14:03:04.825435 enp4s0 Out ARP, Request who-has rubik tell 192.168.1.11, length 46 14:03:04.825422 bridge0 B ARP, Request who-has rubik tell 192.168.1.11, length 46 14:03:04.825449 bridge0 Out ARP, Reply rubik is-at 2e:92:39:cd:15:bb (oui Unknown), length 28 14:03:04.825452 enp3s0 Out ARP, Reply rubik is-at 2e:92:39:cd:15:bb (oui Unknown), length 28 14:03:04.825608 enp3s0 P IP 192.168.1.11.cisco-sccp > rubik.36371: Flags [P.], seq 41105346:41106393, ack 863903, win 2788, length 1047 
14:03:04.825608 bridge0 In IP 192.168.1.11.cisco-sccp > rubik.36371: Flags [P.], seq 41105346:41106393, ack 863903, win 2788, length 1047 
14:03:04.852365 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:04.852375 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:05.058882 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:05.058885 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:05.474879 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:05.474881 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:06.306882 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:06.306885 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:07.970882 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:07.970887 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [P.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:09.905975 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [F.], seq 863925, ack 41106393, win 63867, length 0 
14:03:09.905986 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [F.], seq 863925, ack 41106393, win 63867, length 0 
14:03:10.432989 bridge0 Out IP rubik.44333 > 192.168.1.11.cisco-sccp: Flags [S], seq 1668980638, win 64240, options [mss 1460,sackOK,TS val 1798273288 ecr 0,nop,wscale 0], length 0 
14:03:10.432999 enp3s0 Out IP rubik.44333 > 192.168.1.11.cisco-sccp: Flags [S], seq 1668980638, win 64240, options [mss 1460,sackOK,TS val 1798273288 ecr 0,nop,wscale 0], length 0 
14:03:11.426884 bridge0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [FP.], seq 863903:863925, ack 41106393, win 63867, length 22 
14:03:11.426889 enp3s0 Out IP rubik.36371 > 192.168.1.11.cisco-sccp: Flags [FP.], seq 863903:863925, ack 41106393, win 63867, length 22

What I’ve Tried:
ip neigh replace 192.168.1.11 lladdr 00:05:05:06:07:00 dev bridge0 nud permanent

net.ipv4.neigh.bridge.base_reachable_time_ms = 600000
net.ipv4.neigh.bridge.gc_stale_time = 600

net.ipv4.neigh.default.gc_thresh1 = 4096
net.ipv4.neigh.default.gc_thresh2 = 8192
net.ipv4.neigh.default.gc_thresh3 = 16384
I may have tried other methods suggested by AI, but none of them worked.

Is it the correct MAC address? Does it match the MAC address of the interface used to talk to the remote host? Or any interface on your host?

This topic was automatically closed after 30 days. New replies are no longer allowed.