[NTLUG:Discuss] Summary of port blockage

[Steve Egbert]

Appears that port is blocked at "mckiny1.tx.home.com" router, but no other
ports are blocked yet (i.e. SMTP, DNS, FTP).

Gee whiz,  talk about A Patchy Network.  I'd imagine the AT&T NOC is running
ragged with fragmented and inconsistent policy and it's a matter of time
before they close it all (out of simplicity) unless we voice our opinion to
noc at home.net.  No need to include your account name/number.

If they block DNS, they it's no network at all because MS-NT requires port
52 to 52 to communicate.  Not true for Linux (correct me, if I'm wrong).
If they block SMTP, then mail won't get transfered (this one is a service
killer for me for I'll get lowly IDSL/ISDN before long).
If they block FTP, won't matter to me because it is the biggest bandwidth
hog
If they re-block VPN, as they have before, the telecommuter will be forced
to re-evaluate keeping @Home.
If they block game server ports, then you got the wrong service due to
ridiculous latency.

Now, can anyone tell me that LimeWire or BearShare requires port 80 or not
for optimal uses?

[soapbox]
Basically, cable modem is a poor-growth path due to bandwidth sharing
DSL is making CO-distance inroads with ADSL/SDSL repeaters coming in the
market

Looks like DSL will win out in the long run, provided that 802.11a doesn't
suffer the same DOCSISv2 bandwidth-sharing.

I'm telling you that Telecommunication Act of 1999 is a CLEC-killer.  What
we need is a RLEC (Rural Local Exchange Carrier) so that non-profit
organization (like NTLUG?) can set up DSLAM using weatherized PC and
multiple DSL PCI cards.  Or should that be 802.11b cell network like Seattle
and SF are sprouting?  I've got one in my neighborhood, it's not bad.
[/soapbox]

Steve




-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2656 bytes
Desc: not available
Url : http://ntlug.org/pipermail/discuss/attachments/20010826/f99556d0/winmail.bin