After a fresh install (stage 3) of 2004.3 and compiling of mirrorselect (0.86 and 0.87) no mirrors are selected. Output of "mirrorselect -a -s4" is Downloading a list of mirrors... Netselect is currently unable to handle ipv6, stripping known ipv6 hosts... Removing IPV6 Only Servers... Running netselect to determine mirrors, this might take a moment... No mirrors have been selected. Exiting. Output of "mirrorselect -a -s4 -b10 -o" is Downloading a list of mirrors... Netselect is currently unable to handle ipv6, stripping known ipv6 hosts... Removing IPV6 Only Servers... Running netselect to determine mirrors, this might take a moment... Splitting into blocks of 10. Please note that the smaller the block size the longer this takes... Cleaning tmp files and preparing to select fastest servers... Usage: netselect [-v] [-vv] [-t min_tries] [-m max_ttl] host [host...] No mirrors have been selected. Exiting. Looks like a call to netselect goes wrong? Reproducible: Always Steps to Reproduce: 1. Install mirrorselect 0.86 or mirrorselect 0.87 with netselect 0.3-r1 2. run mirrorselect 3. Actual Results: No mirrors were selected Expected Results: Select mirrors
does this still happen in newer versions?
I am not sure what you mean with "newer versions". Newer versions of what? Mirrorselect is at 0.87 and netselect at 0.3-r which are the latest versions. Anyways, it still happens and thus I am reopening the bug.
can you please try with 0.89 and let me know how you get on.
Yes, it still happens with 0.89, but for some reason only on one machine which baffles me since this is basically a fresh install based on 2004.3 with some extra software (screen, vi, pure-ftpd). Any idea what the reason could be?
can you please tell me the output of: echo $LANG and attach your emerge info output please.
My LANG variable is unset and the output of `emerge info` is Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 VIA Samuel 2 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=c3 -Os -pipe -fomit-frame-pointer" CHOST="i586-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="crypt encode mad ncurses nls oggvorbis pam perl python readline ssl userlocales x86 xml2 zlib" Hope that helps.
could you give this a quick try: env LANG=C mirrorselect -a -s4 -b5 and tell me if you experience the same problems? Something I have noticed is that some routers (for example, the one I am currently borrowing) have a problem with netselect and dont actually route any traffic for it. for example: $ netselect -t2 -vv www.cisco.com Running netselect to choose 1 out of 1 address. www.cisco.com 9999 ms 30 hops 0% ok as you can see - no reply. $ ping www.cisco.com PING www.cisco.com (198.133.219.25) 56(84) bytes of data. 64 bytes from www.cisco.com (198.133.219.25): icmp_seq=1 ttl=115 time=165 ms --- www.cisco.com ping statistics --- 2 packets transmitted, 1 received, 50% packet loss, time 1001ms rtt min/avg/max/mdev = 165.287/165.287/165.287/0.000 ms as you can see, this works fine. $ tracepath www.cisco.com 1: 192.168.0.10 (192.168.0.10) 0.302ms pmtu 1500 1: 192.168.0.1 (192.168.0.1) asymm 101 10.099ms 2: no reply 3: no reply again, oddities. I need to investigate into what the difference is in packet structure for this.
Interesting indeed. I have exactly the same results as you are experiencing (ping works, netselect does not). Mirrorselect still does not work, ends with usage message of netselect.
yep the reason netselect doesnt work (and therefore mirrorselect as it uses netselect for non-deep automatic testing) is because its basically a modified traceroute, and for some reason some routers dont correctly route this information. Not being in a position where I can better test this however doesnt help. Any help is appreciated :) I need to know why the routers are dropping the returning packets from the traceroute. If you try adding your PC into a DMZ on the router, it will most likely work.
Unfortunatly it does not. The machine in question is already configures as a "DMZ host" although it is more of an exposed host. My router is a Draytek Vigor 2500 with the firmware 2.51. I'll go and check some German forums to see why this is happening.
did you manage to get any outcome from this?
closing for now
