[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] automatically retrying network connections
From: |
Jimmy Yuen Ho Wong |
Subject: |
Re: [RFC] automatically retrying network connections |
Date: |
Mon, 23 Jul 2018 00:27:44 +0100 |
On Sun, Jul 22, 2018 at 2:32 PM, Andy Moreton <address@hidden> wrote:
> On Sun 22 Jul 2018, Lars Ingebrigtsen wrote:
>
>> Robert Pluim <address@hidden> writes:
>>
>>> one of the consequences of asking the user questions during network
>>> connection setup is that the server they're trying to connect to might
>>> have decided to close the connection by the time they've finished
>>> answering.
>>
>> Yes, the NSM should reconnect if the user says "go ahead" to the NSM
>> warning and the server has closed the connection. The reason that
>> landed on the back burner is that servers seem to mostly have long
>> timeouts, so this turned out to be less of a problem in practice than I
>> expected. (I.e., I don't recall seeing a bug report about this, which
>> is just plain weird.)
>>
>> We could also reverse the logic a bit and have the NSM always shut down
>> the connection before prompting. This will make network connections
>> (that prompt an NSM warning) be somewhat slower, but it shouldn't be a
>> big deal.
>
> Won't that cause problems for users of sites that use fail2ban to lock
> people out after failed login attempts ? It might be convenient, but
> would need a user option so it could be disabled.
>
I think exponential backoff and a max-retry is in order.
- Re: [RFC] automatically retrying network connections, (continued)
Re: [RFC] automatically retrying network connections, Lars Ingebrigtsen, 2018/07/22
Re: [RFC] automatically retrying network connections, Andy Moreton, 2018/07/22
Re: [RFC] automatically retrying network connections, Noam Postavsky, 2018/07/22