[nSLUG] Re: freshclam not getting answers today

Mike Spencer mspencer at tallships.ca
Sun Jan 27 16:18:11 AST 2008


> Does anyone else notice problems reaching clamav.net from a home
> eastlink connection?

Almost but not quite what you asked for: I DO NOT connect via Eastlink
but my ISP is downstream of Eastlink.  And I get to clamav.net with
fast response.   FWIW, here's the traceroute:

traceroute to 194.109.142.194 (194.109.142.194), 30 hops max, 38 byte packets
 1 pm3-1.glinx.com (24.222.77.239) 167.263 ms 159.235 ms 159.314 ms
 2 bw-gw.glinx.com (24.222.77.252) 160.010 ms 160.225 ms 159.532 ms
 3 blk-222-25-21.eastlink.ca (24.222.25.21) 159.040 ms 160.387 ms 149.283 ms
 4 hlfx-br1.eastlink.ca (24.215.101.197) 158.998 ms 160.339 ms 149.277 ms
 5 hlfx-br2.eastlink.ca (24.222.79.238) 158.972 ms 160.330 ms 159.320 ms
 6 if-12-1.icore1.MTT-Montreal.teleglobe.net (206.82.135.5) 178.652 ms 170.213 ms 179.199 ms
 7 if-10-0-0-19.mcore3.MTT-Montreal.teleglobe.net (216.6.114.13) 169.093 ms 170.144 ms 169.169 ms
 8 if-13-0.mcore4.NQT-NewYork.teleglobe.net (216.6.87.21) 209.009 ms 200.080 ms 199.189 ms
 9 if-5-0.mcore3.NYY-NewYork.teleglobe.net (216.6.87.54) 198.909 ms 200.053 ms 199.188 ms
10 216.6.97.41 (216.6.97.41) 198.647 ms 199.176 ms 199.367 ms
11 216.6.97.6 (216.6.97.6) 178.451 ms 189.508 ms 178.988 ms
12 209.58.26.30 (209.58.26.30) 178.637 ms 180.022 ms 179.096 ms
13 XS4ALL.so-7-0-0.nar1.AMS1.gblx.net (146.82.33.178) 258.802 ms 249.949 ms 349.022 ms
14 0.so-1-0-0.xr3.3d12.xs4all.net (194.109.5.5) 258.616 ms 249.944 ms 249.067 ms
15 0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94) 258.334 ms 250.146 ms 249.196 ms
16 ds049.xs4all.nl (194.109.142.194) 268.820 ms 260.111 ms 259.349 ms


I note that both our routes go through hlfx-br2.eastlink.ca but with
different IP addresses in different /24s reported.  Huh.


Tangent: I hit a problem similar to this recently.  My ISP has to
machines, A & B, that handle dialup connections.  Which one you get is
(apparently) random.  There was a period of some months when, if
connected through A, everything was normal but when connected through
B, I could not reach port 110 on a different ISP's POP3 server.  In
the second case (connect through B) everything was normal EXCEPT for
"no route to host" when attempting connections to POP3/port-110 on the
other ISP's machine.  This was true using Emacs RMAIL/movemail,
homebrew Perl script using IO::Socket and manual telnet to 110.

The problem went away last week.  The admins at both my local ISP and
the remote ISP claim to be baffled.

Ho hum.  Ain't technology wunnerful? :-)

- Mike

-- 
Michael Spencer                  Nova Scotia, Canada       .~. 
                                                           /V\ 
mspencer at tallships.ca                                     /( )\
http://home.tallships.ca/mspencer/                        ^^-^^



More information about the nSLUG mailing list