[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] ACK missing after SYN, strange high Ack Num
|
From: |
Jochen Strohbeck |
|
Subject: |
Re: [lwip-users] ACK missing after SYN, strange high Ack Num |
|
Date: |
Tue, 31 May 2022 08:39:54 +0200 |
No ideas?
I still wonder if ACK after SYN is a protocol error or not.
If it is an error, could this be an (probably well known) LWIP problem?
What also puzzles me: according to the info provided in the wireshark
trace, the ACK numbers reported in case of trouble seems not to be pure
random, if it is converted to a hex number it always starts 0xff..... or
0xffff....!
For example
200545 139.315584624 192.168.0.6 192.168.0.100 TCP 74 [TCP
Port numbers
reused] 44316 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1
TSval=1326542459 TSecr=0 WS=128
200546 139.316059194 192.168.0.100 192.168.0.6 TCP 60 80 →
44316 [ACK]
Seq=1 Ack=4279334007 Win=2764 Len=0
hex(4279334007) = '0xff117477'