From: benoit.marlas@sgcib.com
To: overseers@sourceware.org
Subject: pb accessing your website www.cygwin.com
Date: Tue, 03 Jul 2007 17:25:00 -0000 [thread overview]
Message-ID: <20070703172500.yGeg5ph6fOAb2q13LCyhhkoQtKDs0UZK-1wDYZ7a8AM@z> (raw)
Benoit MARLAS.
noc@redhat.com wrote:
The owners of that box have removed your access due to DOS is what I am
being told.
You can contact them at overseers@sourceware.org for more details and
for further problems.
Thanks
benoit.marlas@sgcib.com wrote:
Hi
I assume there must be a pb with your provider regarding our networks,
because we have several providers and the result is the same each time :
Paris Production : *UUNET (Verizon)*
Paris Test : *Global Crossing*
NY production* **AT&T WorldNet Services** *
Could you please check this with your provider as we have thousand users
here blocked for several weeks now.
We can even have a conference call if needed, so you can check online if
requests are arriving on your network, in order to determine why we do
not have the same behaviour while accesing ports 80 and 21.
Regards.
Benoit MARLAS
ITEC/GLS/APS/ESE
Tel.: 33 (0)1 58 98 10 90_
benoit.marlas@sgcib.com_ <mailto:benoit.marlas@sgcib.com>_
www.sgcib.com_ <http://www.sgcib.com/>
noc@redhat.com wrote:
We have checked are not blocking these IPs. You might check with your
provider for more detailed information on why you cannot reach these
sites. We do not currently have any additional information for you.
These sites are not being blocked in any manner.
benoit.marlas@sgcib.com wrote:
We first tought it may be a routing issue, but the following tests are
pretty clear :
/root/ # telnet www.cygwin.com 22
Trying 209.132.176.174...
Connected to www.cygwin.com.
Escape character is '^]'.
SSH-1.99-OpenSSH_3.9p1
/root/ # telnet www.cygwin.com 21
Trying 209.132.176.174...
Connected to www.cygwin.com.
Escape character is '^]'.
root@parese01:/root/ # telnet www.cygwin.com 53
Trying 209.132.176.174...
Connected to www.cygwin.com.
Escape character is '^]'.
/root/ # ping www.cygwin.com
www.cygwin.com is alive
root@parese01:/root/ # telnet www.cygwin.com 80
Trying 209.132.176.174...
telnet: Unable to connect to remote host: Connection timed out
As you can see, we only have a problem with port 80. On our firewalls,
we can see nothing is coming back
So it definately looks like something is going wrong on your side when
coming from our addresses.
For the moment, we don't have access to your products and it's panfull
for our users.
Regards.
Benoit.
benoit.marlas@sgcib.com wrote:
Hi
We are unable to access your websites (www.cygwin.com,
sources.redhat.com for instance) from our different proxies or even
socks servers located in Paris or New York.
Our public IP are the following :
- 207.45.248.17 to 207.45.248.36
- 207.45.240.17 to 207.45.240.24
Could you please check nothing is blocked on you side ?
Thx
*
Benoit MARLAS*
ITEC/GLS/APS/ESE
Tel.: 33 (0)1 58 98 10 90_
__benoit.marlas@sgcib.com_ <mailto:benoit.marlas@sgcib.com>_
__www.sgcib.com_ <http://www.sgcib.com/>
next reply other threads:[~2007-07-03 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 17:25 benoit.marlas [this message]
[not found] <20070703172515.12732.qmail@gossamer.airs.com>
2007-07-04 16:11 ` Ian Lance Taylor
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=20070703172500.yGeg5ph6fOAb2q13LCyhhkoQtKDs0UZK-1wDYZ7a8AM@z \
--to=benoit.marlas@sgcib.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).