Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Apr 2011 19:23:48 +0200
From:      Paul Chany <csanyipal@stcable.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Can't fetch portsnap because of network problem
Message-ID:  <4D98AD24.7020003@stcable.net>
In-Reply-To: <4D9881EB.5010508@infracaninophile.co.uk>
References:  <4D9879E3.20508@stcable.net> <4D9881EB.5010508@infracaninophile.co.uk>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4D98AD24.7020003>