From owner-freebsd-hubs@FreeBSD.ORG Sun Jul 19 14:25:51 2009 Return-Path: Delivered-To: hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD426106564A for ; Sun, 19 Jul 2009 14:25:51 +0000 (UTC) (envelope-from simon@nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC958FC0C for ; Sun, 19 Jul 2009 14:25:51 +0000 (UTC) (envelope-from simon@nitro.dk) Received: from arthur.nitro.dk (arthur.bofh [192.168.2.3]) by mx.nitro.dk (Postfix) with ESMTP id CDB6A2D4893; Sun, 19 Jul 2009 14:25:50 +0000 (UTC) Received: by arthur.nitro.dk (Postfix, from userid 1000) id C72EC5C14; Sun, 19 Jul 2009 16:25:50 +0200 (CEST) Date: Sun, 19 Jul 2009 16:25:50 +0200 From: "Simon L. Nielsen" To: John Hay Message-ID: <20090719142550.GC1164@arthur.nitro.dk> References: <20090701080110.GA51364@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090701080110.GA51364@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: hubs@freebsd.org Subject: Re: cvsup-master.freebsd.org ipv6 limits X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2009 14:25:52 -0000 On 2009.07.01 10:01:10 +0200, John Hay wrote: > Are the limits for ipv6 cvsup access to cvsup-master.freebsd.org > different from ipv4 access? I have been using ipv6 to access > cvsup-master.freebsd.org from cvsup.za.freebsd.org, but lately I have > seen a lot more "Rejected by server: Access limit exceeded; try again > later" in its logs. cvsupd does not support IPv6 natively, so IPv6 access works by making nc(1) proxy the IPv6 TCP connection to an localhost IPv4 connection. This means that all IPv6 connections are seen as comming from localhost. Looking at the config it actually seems like we only allow one IPv6 connection at the time since we allow from from each IP... There probably just hasn't been enough IPv6 connections for anyone to notice before. I tried bumping the number of IPv6 (localhost) connections to 5. Could you check if this has fixed the problem? Oh, and I just noticed that some of the internal FreeBSD.org syncs seems to have started using IPv6 - that means there is at least an IPv6 connection every 30 minute to collide with. -- Simon L. Nielsen