From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bizarre SSH connection reset
Date: Tue, 11 Mar 2008 10:30:29 -0400 [thread overview]
Message-ID: <47D69785.7020901@kutulu.org> (raw)
In-Reply-To: <200803110649.24883.michaelkintzios@gmail.com>
Mick wrote:
> On Tuesday 11 March 2008, Dan Farrell wrote:
>> On Mon, 10 Mar 2008 22:51:42 +0000
>>
>> Mick <michaelkintzios@gmail.com> wrote:
>>> On Monday 10 March 2008, Dan Farrell wrote:
>>>> On Mon, 10 Mar 2008 15:43:55 -0400
>>>>
>>>> Mike Edenfield <kutulu@kutulu.org> wrote:
>>>>> Comcast?
>>>> I was on comcast for a long time (2.5 yrs) and never had a problem
>>>> like this. They might have blocked port 25 and squelched my
>>>> bittorrenting at times, but never anything like this. Of course,
>>>> ymmv.
>>> IIRC they also block port 80 for sure on their retail accounts. They
>>> don't want the average punter to run a webserver at home.
>> Even when they blocked port 25 for me bidirectionally (evidently
>> sending 6 gigs through that port made me look like a spammer, even if
>> it was all to the same address ;) ), and I called security assurance
>> and they listed that among all the open ports I wasn't allowed on a
>> residential account, even then, they still didn't block port 80 (or 26,
>> 22, 21, 110, 993, or any other port!).
>
> Hmm, I don't know . . . The particular address I was trying to connect was
> definitely blocked. Other than not beeing able to connect with a browser,
> nc, httping and tcptraceroute confirmed it). Could it be an area/account
> specific block perhaps? When I questioned the owner he said that this was
> common practice and that his ISP does not allow webservers to run.
When I was on Comcast, the only ports they blocked outright,
that I found, were mail related. Presumably this was a spam
prevention measure more than anything else.
However, they did *monitor* other common ports for traffic.
Occasionally I'd put some local service or another on my
firewall during development, or for testing, or whatnot. If
it happened to be on port 80, 443, or 21, I'd usually get a
nasty-gram from then within a day reminding me of their AUP.
--Mike
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-11 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 14:03 [gentoo-user] Bizarre SSH connection reset Collin Starkweather
2008-03-09 15:12 ` Mick
2008-03-09 15:32 ` Collin Starkweather
2008-03-09 16:03 ` Andrey Falko
2008-03-10 0:16 ` Mark Shields
2008-03-10 3:43 ` Dan Farrell
2008-03-10 4:42 ` Collin Starkweather
2008-03-10 19:43 ` Mike Edenfield
2008-03-10 20:06 ` Dan Farrell
2008-03-10 22:51 ` Mick
2008-03-10 23:04 ` Brian Marshall
2008-03-11 0:24 ` Dan Farrell
2008-03-11 6:49 ` Mick
2008-03-11 6:58 ` fire-eyes
2008-03-11 14:30 ` Mike Edenfield [this message]
2008-03-11 16:43 ` Mark Shields
2008-03-12 7:03 ` fire-eyes
2008-03-13 16:15 ` Chris Brennan
2008-04-04 2:43 ` [gentoo-user] " Hendrik Boom
-- strict thread matches above, loose matches on Subject: below --
2008-03-13 8:20 [gentoo-user] " Collin Starkweather
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=47D69785.7020901@kutulu.org \
--to=kutulu@kutulu.org \
--cc=gentoo-user@lists.gentoo.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