1
23.7 Legacy Series / Re: Random Timeout (Session TCP Dropped) - SOLVED
« on: September 10, 2023, 03:59:39 am »
It was a strange hardware/software fault.
The internet router configured in bridge was still running at the same time DHCP4 services.
Therefore, if you go on website.tld, two things can happen:
(1) -> The traffic is ok. Nothing seems amiss.
(2) -> The distant server will observe "closed connection" with RESET. If you are capturing packets on your local machine, you will see the TCP session resurrected with a different origin, like if the connection was initiated by the router itself (and NATed by the firewall).
Of course, the live packet capture ability from Opnsense do not give much, simply stating that the outgoing connection is following the rules, so in conclusion the "resurrected TCP connection" is the normal response.
I could only deduce the problem with a traffic analysis with Wireshark.
One thing to see for example is the dropped transmission from the local side, and the answer from given with a different distant origin. It also give the false assumption that it is a DNS issue, but when seeing the dropped connection, it is not.
The internet router configured in bridge was still running at the same time DHCP4 services.
Therefore, if you go on website.tld, two things can happen:
(1) -> The traffic is ok. Nothing seems amiss.
(2) -> The distant server will observe "closed connection" with RESET. If you are capturing packets on your local machine, you will see the TCP session resurrected with a different origin, like if the connection was initiated by the router itself (and NATed by the firewall).
Of course, the live packet capture ability from Opnsense do not give much, simply stating that the outgoing connection is following the rules, so in conclusion the "resurrected TCP connection" is the normal response.
I could only deduce the problem with a traffic analysis with Wireshark.
One thing to see for example is the dropped transmission from the local side, and the answer from given with a different distant origin. It also give the false assumption that it is a DNS issue, but when seeing the dropped connection, it is not.