From owner-freebsd-questions Fri Feb 14 14:13: 5 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F63E37B401 for ; Fri, 14 Feb 2003 14:13:01 -0800 (PST) Received: from madscience.volumen.net (hickey52.micro-mania.net [208.32.118.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9217943F3F for ; Fri, 14 Feb 2003 14:13:00 -0800 (PST) (envelope-from shane@howsyournetwork.com) Received: from farstar.volumen.net (farstar.volumen.net [10.252.238.71]) by madscience.volumen.net (8.11.6/8.11.6) with ESMTP id h1EMCuk32458 for ; Fri, 14 Feb 2003 15:12:56 -0700 Subject: Re: troubleshooting CVSUP failures From: Shane Hickey To: freebsd-questions@freebsd.org In-Reply-To: <1045248387.18621.8.camel@localhost> References: <1045248387.18621.8.camel@localhost> Content-Type: text/plain Organization: How's your network? Message-Id: <1045260775.18621.29.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1- Date: 14 Feb 2003 15:12:56 -0700 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 2003-02-14 at 11:46, Shane Hickey wrote: > Howdy all, > My ISP just put in a packetshaper and I am now having problems getting > CVSUP to work. I suppose it could be unrelated, but I wanted to see if > anyone could suggest good troubleshooting steps. I've tried several > cvsup servers (cvsup, cvsup2, cvsup7, cvsup8) and they all either fail > immediately, or shortly thereafter with one of the following errors. > > TreeList failed: Network write failure: ChannelMux.ProtocolError > > Detailer failed: Network read failure: Input/output error: zlib data > error I hadn't gotten any responses, but I just noticed something. I put my firewall's outside interface into promiscuous mode for Snort and shortly thereafter I started getting the following errors. Feb 14 15:00:37 elijah kernel: ed1: NIC memory corrupt - invalid packet length 4 Feb 14 15:00:48 elijah kernel: ed1: NIC memory corrupt - invalid packet length 3 Feb 14 15:00:52 elijah kernel: ed1: NIC memory corrupt - invalid packet length 4 Feb 14 15:00:53 elijah kernel: ed1: NIC memory corrupt - invalid packet length 3 Now, my question all along has been whether my ISP munged something up and packets are being corrupted. Might the errors that I'm seeing be evidence of that or is it only pointing to the fact that my firewalls ed1 interface might be screwy? Thanks, Shane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message