[nos-bbs] IP config for tun device

[Barry Siegfried]

["George (Skip) VerDuin" <k8rra at ameritech.net> wrote]:

> sorry to have "sucked you into" my confusion... While our "chat" has
> not answered my detail issue it HAS been informative.
>
> On Thu, 2006-07-27 at 01:37 -0400, Barry Siegfried wrote:
>
> > >SNIP<  I also have the "feeling" that you are possibly
> > and needlessly complicating what really isn't quite that complicated.
>
> Perhaps I'm pursuing "thorough" too deeply?  I hope you are correct...

Perhaps.

> > This notion of having "two telnet servers" to which you refer... do
> > you mean opening two instances of the same server to two different
> > users, or do you mean running listeners for the same service at two
> > distinct transport service access points (i.e. ports)?  By "same
> > service", I mean, the identical service in the *same* machine.  If
> > you want to run these listeners for the same service in the same
> > machine at two (or more) distinct ports, then simply start the server
> > as many times as you need on as many ports as you want to use.
>
> To bring closure to this question:
>
> My Linux workstation platform offers "telnet" server services - If you
> were so inclined you could "...$ telnet 67..." and log on my box.  That
> opens the command line processor and you could then do stuff like "list
> directory", "edit file", "print", and even "compile and execute".

Now why would you let me do that on your box?  :)

> Now this scenario dates back to the 1960s when Bell Labs "invented"
> unix and telnet has now fallen out of general use in favor of ssh like
> servers.

They both produce a shell application when connected to so for all intents
and purposes, they are identical.  You just have fiddle with SSH a bit
more because it is harder to get "authorized" and you have to use a
special client.  Well ok.

> Likewise nos was invented on the telnet model to process the amateur BBS
> vocabulary of commands.

Not quite.  NET/NOS was "invented" by KA9Q to bring a TCP/IP stack to
DOS.  At that time, everybody said, "What's TCP/IP?", to which KA9Q
replied (paraphrased of course), "It's something you'll have on your
computers in about 10 years and it will allow you to communicate
digitally with other computers globally over something called the
internet.  But in the meantime, I've got it in this here NET program
so you can practice with it over packet radio before the internet
becomes available to you."

The telnet client came as an original tool to use for the NET/NOS
user.  The PBBS application didn't come until later when SM0RGV
thought it would increase the "appeal" of NOS because packet radio
enthusiasts were already used to connecting to these new things
called PBBSs.  WG7J then started to do serious development of it.
And the rest is history...

> Again if you were so inclined you could "...telnet k8rra..." to do
> jnos kinds of stuff.  I don't mean to insult your knowledge of history
> Barry, but this is the basis for my "two telnet servers" statement.

Ok, so one telnet server on your Linux box which is a shell app, and
one telnet server on your JNOS box which is a mailbox app.  Very well
then.  And the question is?

> When combined with computer clusters, another aspect to all of this
> is that this level of technology is available on "dumb terminal"
> hardware that is "dirt cheap".  As is aptly discussed, the path to
> k8rra.ampr.org has rules and limitation applied it in keeping with
> ham radio - but once you get here my poor box needs to sort out how
> to answer the incoming packet and send the response on it's way.

Right.  It does that according to its outgoing IP routing list and
what, if any packet filtering, you are doing to limit access to your
machine...

> How I configure my workstation, what services I permit from Internet
> and LAN sources, (and more) is the topic I'm pursuing here - and have
> made significant progress with in the past days.

Ok, understood and I am delighted that you are making progress.  :)

> [and] I have a library copy of the Comer book on it's way...

That is a great book.  You will love it.  It should make everything
crystal clear.  I suggest watching packet header traces while you
read that book as well.  :)  It will explain a LOT.  Just remember
it is late 1980s vintage, though TCP/IP itself has actually changed
so little since then, most of it still applies.

> In the neighborhood later?  Stop by if you are inclined...

I wasn't planning on traveling to Michigan today, but I will be sure
to do that when I am there.  :)

73, de Barry, K2MF >>
           o
          <|>      Barry Siegfried
+---------/-\---------------------------+
| Internet | bgs at mfnos.net              |
| HomePage | http://www.mfnos.net/~bgs  |
+----------+----------------------------+
| Amprnet  | k2mf at nnj.k2mf.ampr.org     |
| PBBS     | k2mf at k2ge.#cnj.nj.usa.noam |
+----------+----------------------------+