Comment # 7
on bug 10300
from [email protected]
Stephen,
Ok I think FCS was only part of it. I see what your saying but i think through
this thread the original problem was a bit diluted.
The purpose of the trace was to analyze a TLS negotiation issue.
TLS is not happening on the typical port 443 but instead 7547.
So for a controlled test:
Open the trace in 1.6.2
Select Packet 10, decode as -> SSL
Filter for SSL, you will see the full negotiation and failure
Open the trace in 1.10.18
Select Packet 10, decode as -> SSL
Filter for SSL, you will see only the Server Hello
We see in packet 13 in 1.10.18 multiple TCP errors under SEQ/ACK analysis and
the underlying protocol PPPoE we see a Payload Length Error. I believe this is
why the rest of the packet cannot be dissected properly to analyze the TLS
failure.
I personally do not believe this has anything to do with FCS, but this is not
my specialty so I hope to only guide you guys in the right direction.
Screen shots attached.
You are receiving this mail because:
- You are watching all bug changes.
