On some systems in case where remote is not responding, socket could
remain in SYN_SENT state for a really long time without errors waiting
for connection. This leads to situations where vconn connection hangs
for a few minutes waiting for connection to the DOWN remote.
For example, this situation
On Wed, Dec 26, 2018 at 06:23:56PM +0300, Ilya Maximets wrote:
> On some systems in case where remote is not responding, socket could
> remain in SYN_SENT state for a really long time without errors waiting
> for connection. This leads to situations where vconn connection hangs
> for a few minutes
On Wed, Jan 09, 2019 at 08:28:54PM +0300, Ilya Maximets wrote:
> On 27.12.2018 20:36, Ben Pfaff wrote:
> > On Wed, Dec 26, 2018 at 06:23:56PM +0300, Ilya Maximets wrote:
> >> On some systems in case where remote is not responding, socket could
> >> remain in SYN_SENT state for a really long time wi
On 27.12.2018 20:36, Ben Pfaff wrote:
> On Wed, Dec 26, 2018 at 06:23:56PM +0300, Ilya Maximets wrote:
>> On some systems in case where remote is not responding, socket could
>> remain in SYN_SENT state for a really long time without errors waiting
>> for connection. This leads to situations where
On 09.01.2019 23:27, Ben Pfaff wrote:
> On Wed, Jan 09, 2019 at 08:28:54PM +0300, Ilya Maximets wrote:
>> On 27.12.2018 20:36, Ben Pfaff wrote:
>>> On Wed, Dec 26, 2018 at 06:23:56PM +0300, Ilya Maximets wrote:
On some systems in case where remote is not responding, socket could
remain in
On Thu, Jan 10, 2019 at 11:44:05AM +0300, Ilya Maximets wrote:
> On 09.01.2019 23:27, Ben Pfaff wrote:
> > On Wed, Jan 09, 2019 at 08:28:54PM +0300, Ilya Maximets wrote:
> >> On 27.12.2018 20:36, Ben Pfaff wrote:
> >>> On Wed, Dec 26, 2018 at 06:23:56PM +0300, Ilya Maximets wrote:
> On some sy
