[PROXYPER] need a non-TCP/IP personal proxy

Messenger, Mark MMessenger at DIRECTV.com
Mon Jul 22 14:35:45 EDT 2002


According to  http://www.davesite.com/webstation/net-history2.shtml
TCP/IP replaced NCP on the net in 1983, roughly 20 years ago :)

The original ARPANet (the Internet's early name) was created circa 1968
wayyyyyy before TCP was even thought up.

A quick google search for "Internet history TCP/IP" should yield you a fair
bit of background reading.


Hope this helps ya.



-----Original Message-----
From: waldo kitty [mailto:wkitty42 at alltel.net]
Sent: Monday, July 22, 2002 1:57 PM
To: proxyper at lists.distributed.net
Subject: Re: [PROXYPER] need a non-TCP/IP personal proxy



TCP/IP is not just internet oriented... TCP/IP has been used for a lot
of networking stuff long before the internet came about... remember, the
internet (as we know it today) has only been around for a decade or
so... anyway, TCP/IP is not limited just to the internet and one would
be foolish to restrict one's self from using it whenever they can...
look around you... look at the other networks and their protocols...
where are they today? in many cases, they are defunct and obsolete if
they are even still being used at all...

Patcat88 wrote:
> 
> I can easily make a NAT using Linux or my copy of Advanced Server. A
> DHCP server will work. I just think that TCP/IP is a internet thing
> and should stay exactly that, a Internet thing.
> 
> "Messenger, Mark" wrote:
> 
> >
> >
> > Your first concern would be addressed by NAT-ing your computers
> > behind your DSL computer/router.  Private IP ranges are considered
> > non-routable, and thusly, not attackable from the outside world
> > (generally speaking. Yes, I know there are ways to fool some
> > routers/NAT daemons into faking a session to an internal host.  This
> > is a rare case, as I understand it).
> >
> > As far as Dnet goes, the lack of incoming connections is not a
> > problem.  I have verified that the Dnet client (and the Dnetd
> > personal proxy) will work just fine on NAT-ed IP addresses.  I run
> > this at home on my 5-odd working machines.
> >
> > Does this answer your question?  If not, let me know :)
> >
> >
> > -----Original Message-----
> > From: Patcat88 [mailto:patcat88 at SNET.Net]
> > Sent: Saturday, July 20, 2002 6:55 PM
> > To: proxyper at lists.distributed.net
> > Subject: Re: [PROXYPER] need a non-TCP/IP personal proxy
> >
> > I don't want people to be able to send packets directly to a
> > unprotected
> > windows 3.11 WFW system. Yes I know about NAT but I'm afraid that
> > NAT
> > won't map the DATA back to the originating computer properly. Also
> > NAT
> > doesn't allow incoming connections which I think will be a problem.
> >
> > --
> > To unsubscribe, send 'unsubscribe proxyper' to
> > majordomo at lists.distributed.net
> 
> -- To unsubscribe, send 'unsubscribe proxyper' to
> majordomo at lists.distributed.net

-- 
       _\/
      (@@)                      Waldo Kitty, Waldo's Place USA
__ooO_( )_Ooo_____________________ telnet://bbs.wpusa.dynip.com
_|_____|_____|_____|_____|_____|_____ http://www.wpusa.dynip.com
____|_____|_____|_____|_____|_____|_____ ftp://ftp.wpusa.dynip.com
_|_Eat_SPAM_to_email_me!_YUM!__|_____|_____ wkitty42 (at) alltel.net
--
To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.distributed.net/pipermail/proxyper/attachments/20020722/5d4cf0b8/attachment-0001.htm


More information about the proxyper mailing list