From owner-freebsd-questions@FreeBSD.ORG Sun Apr 3 17:23:52 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 785E81065674 for ; Sun, 3 Apr 2011 17:23:52 +0000 (UTC) (envelope-from csanyipal@stcable.net) Received: from mx2.stcable.net (mx2.stcable.net [91.102.225.7]) by mx1.freebsd.org (Postfix) with ESMTP id 2E1C38FC08 for ; Sun, 3 Apr 2011 17:23:51 +0000 (UTC) Received: from mx2.stcable.net (localhost [127.0.0.1]) by mx2.stcable.net (Proxmox) with ESMTP id 3E831C810D for ; Sun, 3 Apr 2011 19:23:51 +0200 (CEST) Received: from smtp.stcable.net (smtp.stcable.net [91.102.225.5]) by mx2.stcable.net (Proxmox) with ESMTP id 21B2DC80F1 for ; Sun, 3 Apr 2011 19:23:51 +0200 (CEST) Received: from [192.168.10.77] (194-170-85-95.dynamic.stcable.net [95.85.170.194]) by smtp.stcable.net (Postfix) with ESMTPA id 0E3E1364F9 for ; Sun, 3 Apr 2011 19:23:51 +0200 (CEST) Message-ID: <4D98AD24.7020003@stcable.net> Date: Sun, 03 Apr 2011 19:23:48 +0200 From: Paul Chany User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110307 Icedove/3.0.11 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4D9879E3.20508@stcable.net> <4D9881EB.5010508@infracaninophile.co.uk> In-Reply-To: <4D9881EB.5010508@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Can't fetch portsnap because of network problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2011 17:23:52 -0000 2011-04-03 16:19 keltezéssel, Matthew Seaman írta: > On 03/04/2011 14:45, Paul Chany wrote: > >> I'm trying to fetch portsnap but can't because probably of network problem. >> >> Whenever I try to run command >> # portsnap fetch extract >> >> the process stall and never reach 20%. It is sad. :( >> >> The computer on wich I try to run this command is on my home LAN >> that has a gateway/router. >> >> What can I do to solve this problem? >> > You need to diagnose why your fetch is bombing out. Start by checking > over your own equipment and try to eliminate that as a source of > problems. Make sure all your cabling is in good condition and that all > network plugs are correctly seated. Check for packet errors: > > # netstat -i > > Anything non-zero in the Ierrs or Oerrs columns is a cause for concern, > especially if the error counters are going up over time. If your > gateway/router has the capability, check for the same sort of errors there. > On my gateway/router the output of 'netstat -i' command is_ Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 7914770 0 0 0 3427615 0 0 0 BRU eth1 1500 0 3369182 0 0 0 5234370 0 0 0 ABMRU lo 16436 0 1193 0 0 0 1193 0 0 0 LRU -- Best Regards, Paul