Can't fetch portsnap because of network problem
Hi, 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? -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
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. Having eliminated your own kit as a source of problems, try looking for network problems between the portsnap servers and you. mtr(8) is good for this purpose, but (of course) catch22: to install it, you'ld need a working ports tree... mtr will show up packet loss on intermediate network links, and various sorts of routing problems. If these are present, then you need to contact your ISP who should be able to sort things out on your behalf. Finally, one thing that can screw up portsnap is a poorly implemented transparent HTTP proxy. My advice: *don't use ISPs that force you to use transparent proxying*. However, if this is what you are lumbered with, then there is a simple work-around: use csup(1) instead of portsnap(8). csup doesn't run over HTTP, so it can't be mangled by broken proxies. Now, if you need help with any of this, you can certainly post here, but for best results you'll need to supply a lot more detail about exactly what it was you did and exactly what the result was. Cut'n'paste from the terminal is good, or use script(1) to save a transcript of a terminal session. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Can't fetch portsnap because of network problem
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 All my cabling is in good condition and all network plugs are correctly seated. I attached the output of '# netstat -i' command in netstat.log file. One can see there are 26 Oerrs in the file. Informations of my home LAN are: domain: excito gateway: 192.168.10.1 name server: 192.168.10.1 netmask: 255.255.255.0 Any advices will be appreciated! -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
2011-04-03 18:35 keltezéssel, Paul Chany írta: 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 All my cabling is in good condition and all network plugs are correctly seated. I attached the output of '# netstat -i' command in netstat.log file. Well, it seems that one can't to send mail with attached file onto list, right? Here is the output of netstat -i: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll plip0 1500 Link#1 0 0 0 0 0 0 lo0 16384 Link#2 0 0 0 0 0 0 lo0 16384 fe80:2::1 fe80:2::10 - - 0 - - lo0 16384 localhost ::1 0 - - 0 - - lo0 16384 your-net localhost0 - - 0 - - ue01500 Link#3 00:00:e8:00:11:f172968 0 0 4867126 0 ue01500 192.168.10.0 cspetoile.localdo72934 - - 48682 - - -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
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-OVRTX-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 lo16436 0 1193 0 0 0 1193 0 0 0 LRU -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
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 Well, maybe this does not cause the solution but: I change in /etc/portsnap.conf the server from: SERVERNAME=portsnap.FreeBSD.org to a portsnap mirror: SERVERNAME=portsnap1.FreeBSD.org and after that I can fetch ports. -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
