Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Dave Platt <dplatt@radagast.org>
To: linux-hams@vger.kernel.org
Subject: Re: Qsl.net availability
Date: Wed, 14 Apr 2004 15:40:16 -0700 (PDT)	[thread overview]
Message-ID: <20040414224016.30670.qmail@radagast.org> (raw)
In-Reply-To: <20040414192725.482d515a.john@jcoppens.com>

John Coppens <john@jcoppens.com> wrote:
> Hello people.
> 
> Since a few months, I cannot connect to www.qsl.net from where I live
> (Argentina). I can connect with FTP, but not in HTTP (webpages). I can
> ping www.qsl.net, Not only I can't connect to my own page, but I cannot
> connect to any of the webpages at QSL.NET.

This site comes up just fine for me, here in California.

> I am not ruling out a configuration problem in my Linux machine, but I
> cannot find out why this is the _only_ site I cannot connect to.

One possibility is that the WWW.QSL.NET server machine is blocking
TCP connections from your IP address range.

I'm sorry to say that Argentina's ISPs are in very bad odor with
quite a few system administrators in North America.  This is due
to the large number of spammers, spammers' web sites, virus- and
trojan-horse-infected client systems, "script kiddies" probing
for security vulnerabilities, etc. found on Argentina's networks,
and to the apparent unwillingness of the ISPs involved to respond
to reports of these abuses or to take any visible steps to clean
up their networks.

A fair number of fed-up administrators have started blocking all
inbound email from the LACNIC IP space assigned to Argentina.  Some
have even blocked all inbound TCP traffic from Argentina at their
border routers.  This may, possibly, be what is affecting you.

Argentina's not alone in this sort of treatment.  Quite a few
USA ISPs (in particular, some of the big cable-modem and DSL
providers) are facing similar forms of "prophylactic blocking"
by sysadmins who are fed up with floods of abuse from
slackly-managed ISPs.

Another possibility is that there's some sort of fairly selective
routing problem involved.  What do you see if you run the command
"/usr/sbin/traceroute www.qsl.net" from your Linux system?




  reply	other threads:[~2004-04-14 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 22:27 Qsl.net availability John Coppens
2004-04-14 22:40 ` Dave Platt [this message]
2004-04-15  1:12   ` John Coppens
2004-04-14 22:56 ` John R. Marshall
2004-04-15  4:00   ` Scott Lambert
2004-04-15 12:02     ` Ralf Baechle DL5RB
  -- strict thread matches above, loose matches on Subject: below --
2004-05-07  2:10 Ariel Graneros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040414224016.30670.qmail@radagast.org \
    --to=dplatt@radagast.org \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox