Comcast blocks port 25 incoming, yet again

[John Abreau]

Yes, I'm using a Linux server as my router. Once I noticed the
DNS-related behavior, I power-cycled the DSL modem so I could
test it thoroughly to confirm it. After that, I set up an hourly
cron job on the routing server that asks the DSL modem to resolve
"www.google.com":

    host www.google.com dsl.abreau.net

(where "abreau.net" is my internal DNS zone, not the external
abreau.net zone on the BLU server).



On Fri, May 2, 2008 9:47 am, Jerry Feldman said:
> On Thu, 1 May 2008 15:28:28 -0400 (EDT)
> "John Abreau" <jabr at blu.org> wrote:
>
>> I have a DSL connection with a modem that is designed to allow only
>> a single machine to access it. It worked fine with MacOS when I first
>> installed it, but it didn't work with Linux until I discovered that
>> it authorizes a machine when that machine uses the DSL modem to
>> resolve a DNS query.
>>
>> Tech support was completely useless, and I only found out about it
>> when I listed all the differences in network configurations between
>> the Mac and the Linux box and then experimented with the results.
>
>
> So, while this has nothing to do with Comcast, how did you eventually
> resolve it? Are you using Linux as a router? Additionally, Comcast's


-- 
John Abreau / Executive Director, Boston Linux & Unix
IM: jabr at jabber.blu.org / abreauj at AIM / abreauj at Yahoo / zusa_it_mgr at Skype
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.