[unisog] no-ip.com etc.

Ben Curran bdc1 at humboldt.edu
Mon Oct 27 17:34:00 GMT 2003

Funny the twists and turns a post can take.....

On 27 Oct 2003 at 11:09, Valdis.Kletnieks at vt.edu wrote:

> On Mon, 27 Oct 2003 07:31:28 PST, Ben Curran said:
> > > Hmm.. Killing the network, and doing something illegal.  
> > 
> > They do this all the time. Another reason to minimize exposure.
> Best way to minimize your exposure is to not provide access at all.  Is that
> what direction you want to go?

Well that would be the other extreme wouldn't it.  But forbidding access wouldn't be 
any fun. We wouldn't be having this wonderful interchange!

> Remember that for a TCP connection, one end or the other is going to
> send a SYN packet.  Sure, you can block ad-hoc servers easily enough by
> just stomping all the inbound SYN packets.  But then you manage to break
> everything from FTP (if it doesn't use PASV) to irc DCC CHAT to most
> programs that have a peer-to-peer feature (including most IM services).

We haven't broken FTP for the students. That would be a sad fate indeed.

-- ¥«¤»§«¤»¥««¤»§«¤»¥«¤»§«¤»¥
Network Specialist
Humboldt State University 
Telecommunications & Network Services 
Phone: 707.826.5000 fax: 707.826.6161 
pgp key-- 2048/1024, 0x619015B2

More information about the unisog mailing list