From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: dsl and the confusedness the howto brings about various protocols
Date: Sun, 10 Sep 2000 09:09:26 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009100857150.10006-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0009102301150.424-100000@data.home>
This is a new thing that ISPs have come up with in response to the media
coverage of danger in a permenant connection. Because the media has been
in a frenzy of the dangers involved in a full time connection, people who
know nothing and are in relatively little danger have cryed for protection
from the ISP.
Some ISPs offer NAT to resolve this problem. For most people that is fine,
but once again because of mass ignorance that wasn't a usable
solution. You see people who know something and wanted to run servers
pointed out that NAT has limitations (most of which don't effect the
average user at all) and so ignorant people cried again. They didn't want
the limitations of NAT, but they wanted protection.
So some bright person came up with "new" technology. They decided they
would use PPP over a standard ethernet connection and have the computer
establish a connection when active using the internet. Then after a period
of inactivity it would drop (or could be forced to drop when all internet
apps closed like a dial-up connection). This "new" technology offered the
speed and conveniance of DSL with the protection of dialup. The computer
would no longer be a sitting duck on the net all the time and would again
have a dynamic IP.
Now for many what I am describing sounds very much like VPN technology. I
personally don't know the details, but it sounds like it to me. Southwest
Bell offers it in this area with their USB DSL modems. While some would
say it is now hardware, I would point out that many VPN solutions exist in
hardware. Now for the long and short of it as I can see:
If the solution is in the hardware you shouldn't have any more trouble
then a full time connection. I would look to see if it is supported by
Windows NT and Macs. I doubt they would invest the time into software for
both NT and a Mac. If it can be supported in Win 3.x it is most certainly
able to work in Linux. But the ultimate way is to say no thanks and
specify you want a static IP address with full time connection. If one
provider doesn't offer that, call annother. Someone will sell you what you
want if they can.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
Brent Harding
` Geoff Shang
` Kirk Wood [this message]
` Brent Harding
[not found] ` <Pine.LNX.4.21.0009100857150.10006-100000@localhost.localdo main>
` Brent Harding
` Kirk Wood
` Terry D. Cudney
` Kirk Wood
` Kirk Wood
` Terry D. Cudney
[not found] ` <Pine.LNX.4.21.0009101603270.668-100000@localhost.localdoma in>
` Brent Harding
[not found] ` <Pine.LNX.4.21.0009101252140.668-100000@localhost.localdoma in>
` Brent Harding
` Kirk Wood
[not found] ` <Pine.LNX.4.21.0009101403500.668-100000@localhost.localdoma in>
` Brent Harding
` Frank J. Carmickle
[not found] ` <Pine.LNX.4.05.10009110240500.13558-100000@speech.braille.u wo.ca>
` Brent Harding
` Scott Howell
` Frank J. Carmickle
` Tommy Moore
` Kirk Wood
` Scott Howell
` Brent Harding
` Janina Sajka
` Tommy Moore
` Kirk Wood
` Janina Sajka
` Scott Howell
` dsl and the confusedness Kirk Wood
` dsl and the confusedness the howto brings about various protocols Brent Harding
` Janina Sajka
[not found] ` <Pine.LNX.4.21.0009121400310.20950-100000@adsl-151-200-20-2 9.bellatlantic.net>
` Brent Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0009100857150.10006-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).