13 Apr
2014
13 Apr
'14
10:38 a.m.
Good day to all,
Unfortunately my subscription options were set to nomail, so I have
not been following posts very reliably this past few months. Anyways,
just thought I would dig through the digest and comment on stuff.
Doing the routing on the NOS side of things seems a
bit backwards
these days (cough encap.txt)
You don't have to use encap.txt anymore, depending on your
configuration. Brian introduced AMPRnet RIP broadcasts a few
years ago. Some of us use those now to update our NOS routes.
Of course you cannot do that if you are still running
NOS
on an old DOS box.
Technically speaking you could always do encap.txt on a NOS
system running in DOS - I did it that way over 12 years ago.
Does such exist.... Has anyone created..... can said
code
be easily separated / compiled separately.....
The irony is (and there was a lot of criticism towards the authors
at the time, this was before I took it over in 2004), the original
NOS was actually 'hacked' to give it BBS functionality, as well as
a few other features. Anythings possible, but removing the NOS from
NOS (think about it, that's what it would come down to) would be a
big waste of time and all you would have left is a BBS 'hack'.
Sound to me perhaps FBB is more what you're looking for. It's a BBS
first and foremost. Actually, how about BCM (Baybox) or OpenBCM out
of Europe. It's pretty slick stuff actually, check it out.
don't say whether you're interested in a
Windows or a Linux based
Believe it or not I have a text (console) based Windows (yeah, true
native windows not a DOS compile) version of JNOS, experimental like
all of the NOS stuff is, even got WINMOR running B2F forwarding with
RMS stations in both my windows and linux versions. Again, I'm an
experimenter so the software (like usual NOS style) is not always
the most user friendly. I'm just going to say, I'm encouraged for
my own ham radio needs. Multipsk as a packet modem works too :)
This appears to be the only "maintained"
version of JNOS
I took over from James Dugal in 2004, and rebranded it as JNOS 2.0, you
can see it in the credits on my official site for JNOS 2.0. James passed
away years ago, passing the tourch so to speak, as others did to him as
well when they got tired of working on it, or just had to give it up.
My primary development platform for years was LINUX, it still is, just
that I feel I need to get moving into the Windows (very untapped user
base) domain. Just wish I had more time to devote to it, I'm a busy
family and working man too like a lot of the people on this group.
haven't looked at the code to see how deep into
the stack he's
getting but his dependence on winp cap indicates it still has some
degree of coupling to layer 3.
The windows version I started with WinPcap cause I wanted a quick way
to tie into the WIN32 tcp stack. I've tried to do raw sockets and it's
just plain ugly and I got frustrated. The WinPcap has turned out to be
pretty decent for what I need.
I use the original NOS ip stack code, no windows IP or TCP functions,
it's all NOS (yeah obsolete, exciting eh) code for ip routing, and
such.
Anyways, just thought I would try and clarify a few things. Feel free
to ask me if you have more questions about all of this.
With kind regards,
Maiko Langelaar / VE4KLM
* http://www.langelaar.net/projects/jnos2