Message-ID: <0c27edad-d696-5857-02ee-d2ef8e6286d1@...1227...> Date: Fri, 24 Jun 2022 13:15:05 +0200 MIME-Version: 1.0 Content-Language: en-GB References: <20181206171033.61310-1-gert@...1296...> <06dfe01b-95dd-ae08-4b30-96f85ac2bd9d@...1856...> <80e6882a-dd00-eeff-151b-1b67d6e61103@...2181...> From: Arne Schwabe In-Reply-To: Subject: Re: [Openvpn-devel] [PATCH] Rate-limit incoming P_CONTROL_HARD_RESET_* packets. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Gert Doering , Antonio Quartulli Cc: openvpn-devel@lists.sourceforge.net Am 24.06.22 um 12:26 schrieb Gert Doering: > Hi, > > On Fri, Jun 24, 2022 at 11:13:40AM +0200, Antonio Quartulli wrote: >> do we still need this patch after having merged Arne's HMAC feature? > > Yes and no. > > *This* patch won't apply anymore, but Arne said "we're now much faster > in replying to packets than ever before" so we might indeed need a > per-source-ip rate-limiter, to something like "10 per 10 seconds" or > so (inventing arbitrary number that should be more than enough even > for "5 users behind the same NAT reconnect at the same time", while > at the same time too low to cause harm as a reflector) for the > initial reply. Yeah. Keeping a per IP table is adding a lot of state to manage that. Maybe instead to a (configurable) overall limit like 100/s? Arne