[NTLUG:Discuss] Port forwarding question

[Courtney Grimland]

On Tue, 03 Jun 2003 20:30:06 -0500
"Paul Drew" <solarcurve at msn.com> wrote:

> Howdy,
> I am now on board the new comcast system via attbi transfer, and I
> have no issues at all with ports being blocked. I have been running
> a webserver out of my house since mid 1999 back with excite at home. I
> have been pretty fortunate overall, because I have been through all
> those transfers of service with really not any downtime and
> performance has actually been increased since them. So far
> everything I have tried with comcast is fine. All ports seem to be
> clear and open in FlowerMound that is. :) Good luck to you though
> sir.
> 
> Paul Drew

I can say pretty much the same thing here in Arlington.  I have also
ridden the wave of buyouts, from AT&T at Home to ATTBI and now Comcast,
and I have never had a problem running any network services - http,
ftp, ssh, pop, dns, whatever.  And all on standard ports.  I have
noticed that they seem to run some sort of bot that constantly checks
for DHCP server responses on my network segment, but other than that
there seems to be no restrictive filtering.

And I too have had a great experience with the service.  Other than my
cable modem frying in a storm about six weeks ago (along with three
NICs, two power supplies, a motherboard, and an 8-port switch - I got
hit HARD), and about a day and a half when it switched from @Home to
ATTBI, I have had zero downtime and wonderful speeds.  I've seen
download speeds as high as 2.4 Mb/s.   Now, the help desk
people...that's another story.  One mention of Linux gets a prompt "We
don't support that" and they let me go.  At least that's how it was
with ATTBI.  I haven't had to deal with Comcast's support yet, but I
now know how to pretend like I'm running winipcfg from Win98 while
checking /var/lib/dhcpc/dhcpcd-eth0.info on my firewall box. 
Muahahahah!!

Man, I'm a geek.

Interestingly enough, their DHCP server still gives me a domain of
attbi.com.