Re: Apt + Netselect Server choosing
On Thu, Oct 22, 1998 at 03:46:21PM -0400, Avery Pennarun wrote:
> On Thu, Oct 22, 1998 at 02:12:10PM -0400, Stephen J. Carpenter wrote:
>
> > netselect works now:
> > [sjc@lenny sjc]$netselect -vv helix stat1 stat3 hedwig
> > helix 2 ms 2 hops 100% ok (10/10) [ 2]
> > stat1 2 ms 2 hops 50% ok ( 5/10) [ 6]
> > stat3 3 ms 3 hops 100% ok (10/10) [ 3]
> > hedwig 2 ms 2 hops 50% ok ( 5/10) [ 4]
> > 2 helix
>
> Hmm, those 50% thruput ones are interesting. I don't see that effect on my
> network. Is your connectivity to those hosts really that bad?
hmmm
no...
stat1 is a Sparcstation 1 running Solaris 2.6 ;) and hedwig is a Sparcstation
10 running 2.6, a webserver, mailing lists ;)
traceroute to stat1.***.*******.*** (***.***.120.62), 30 hops max, 40 byte
packets
1 ccorer1.***.*******.*** (***.***.24.3) 1.709 ms 1.649 ms 1.588 ms
2 stat1.***.*******.*** (***.***.120.62) 6.61 ms * 2.652 ms
(hope you don't mind the blank outs....Net Eng might not apreciate IP
adresses and information involving their routers being posted in
public..not that it would be hard to figure out ;) )
The network here is also very busy at times (even if there are catalyst
5000's in allot of the closets) funny... stat1 and hedwig are in the same
room on a co-workers desk (on 4th floor...im on 10...stat3 is in another
building ;)
> > [sjc@lenny sjc]$netselect -vv helix www.debian.org
> > helix 1 ms 2 hops 100% ok (10/10) [ 1]
> > www.debian.org 9999 ms 30 hops 0% ok
> > 1 helix
> >
> > --- of course...traceroute doesn't work past our firewall either
>
> Oh. netselect uses exactly the same technique as traceroute to find the
> hopcount (although it uses a binary, rather than linear, search). If it
> can't find the hopcount, it won't work at all.
>
> There are two reasons traceroute might not work: problems with the TTL, and
> firewalled UDP ports. netselect does some pretty strange tricks with UDP
> ports, so it may not be easily fixable if that's the problem... hmm.
>
> If it's just a TTL thing, that should be easy enough to work on.
Well I have never heard of traceroute working...it always stops right at the
gateway:
traceroute to big.tits.are.not.lame.org (204.27.202.19), 30 hops max, 40 byte
packets
1 ccorer1.***.*******.*** (***.***.24.3) 1.81 ms 1.713 ms 1.71 ms
2 gw1021.********.*** (***.***.102.3) 4.594 ms 2.085 ms 2.062 ms
3 gw1013.***.*******.*** (***.***.1.250) 7.346 ms 5.942 ms 5.872 ms
4 * * *
> > Is there perhaps some other way this could work (maybe that the test could
> > fall back on in case there isa firewall problem)?
>
> Could you send me the netselect output if you use "-vvv" instead of "-vv"?
> Hopefully that will reveal something.
ok....
[sjc@lenny sjc]$netselect -vvv www.debian.org helix
helix 2 ms 15 hops - OK
helix 1 ms 8 hops - OK
helix 1 ms 4 hops - OK
helix 2 ms 2 hops - OK
helix 1 ms 1 hops - HIGHER
helix 1 ms 2 hops - OK
helix 1 ms 2 hops - OK
helix 2 ms 2 hops - OK
helix 1 ms 2 hops - OK
helix 1 ms 2 hops - OK
helix 2 ms 2 hops - OK
www.debian.org - TIMEOUT
www.debian.org - TIMEOUT
www.debian.org - TIMEOUT
www.debian.org - TIMEOUT
www.debian.org - TIMEOUT
www.debian.org 9999 ms 30 hops 0% ok
helix 1 ms 2 hops 100% ok (10/10) [ 1]
1 helix
-Steve
--
/* -- Stephen Carpenter <sjc@delphi.com> --- <sjc@debian.org>------------ */
E-mail "Bumper Stickers":
"A FREE America or a Drug-Free America: You can't have both!"
"honk if you Love Linux"
Reply to: