Comment # 6
on bug 8173
from Kyle Cottongim
It seems that there is some confusion on my end regarding what was happening
here. This may just be an "acceptable" limitation of Wireshark.
Upon further investigation, it seems the TCP client is using the same initial
sequence number for all of their connections. This is why I see this behavior
when testing with that device but not when testing with a Linux laptop as the
TCP client. Since Linux does actually randomize the TCP sequence number, I
don't see this behavior when testing with it. (this is why there was so much
confusion on my end)
Sorry for the confusion.
You are receiving this mail because:
- You are watching all bug changes.