JNOS, Packet and More

to JavAPRS@Yahoogroups
---

It was so easy. Seattle makes available .gif files showing the traffic
conditions. A bit of messing with the lat/long values and now JavAPRS
is mapping stations on top of the current traffic conditions.

Here's the official traffic page:

http://www.wsdot.wa.gov/PugetSoundTraffic/

And here it is with APRS stations.

http://www.jnos.org/cgi-bin/ja?wadot

Calibration isn't great. The traffic "picture" is a graphic representation,
not a true map so it isn't linear across the whole picture.

73,
Bill - WA7NWP

to HTSIG...

---
At 06:20 PM 6/27/02 -0400, Alan Crosswell wrote:

Does anybody know if KISS mode is fully implemented in the TH-D7? I put mine
into KISS mode (KISS ON and RESTART) and it appears to receive packets fine
but I wasn't able to get it to transmit. Could be some other problem as I was
using a Linux kernel revision that I had not previously used with a KISS TNC-2....
---

The G version fixed some issues with KISS mode but not all. The small receive buffer
in the D7 prevents it from being very useful in Kiss mode on a busy channel.

Bill, WA7NWP

At 04:21 PM 6/25/02 -0700, Harold Kinchelow wrote:
What's LDAP and IMAP?
Harold

LDAP is Lightweight Directory Access Protocol

An Internet standard for names, addresses and other information. Outlook (Express)
and Eudora can both use it.

http://www.kingsmountain.com/ldapRoadmap.shtml


IMAP is Internet Message Access Protocol. It is a method of accessing electronic mail or bulletin board messages that are kept on a (possibly shared) mail server. In other words, it permits a "client" email program to access remote message stores as if they were local. It allows multiple systems
to access the same mail messages.

This is very attractive when considering the slow data transfer on amateur circuits. It makes
good sense to look at the headers and download for viewing only the messages necessary
rather then downloading everything and deleting the fluff.

More info: http://www.imap.org/about/whatisIMAP.html

73,
Bill - WA7NWP

A couple notes here on BBSSIG and NETSIG last week started me
thinking about my goals and reasons for playing with packet. At least to
the point of organizing my thoughts and getting it written down. Why
am I spending so much time and energy on this and what's here that
makes it valuable to others? What reasons can I give to encourage
folks to dig out their packet stations and get them on the air.


First reason it's fun and a challenge. Ok - I know it happens millions
of times a day in the real world but I still get a real kick seeing an Email
message delivered by Amateur Systems on RF. The thrill of seeing some
technology newly turned on start to work is even better. Like watching the
Internet News messages starting to flow via NNTP to a neighbor's system.

Continuing education is the second reason. At 1200 baud, you see and feel and
begin to understand how the Internet works. The data is slow enough to watch
the protocol exchanges and see where the message content fits in. Like building
a radio from scratch, you gain an understanding of what is going on to make it work.

Third reason is the potential personal usefulness of the system. I admit it. I'm
hooked. I start to shake and sweat if I don't get to check my Email every couple
hours. The second thing I do in the morning (after kissing the YL) is check the
Email. It's the second to the last thing (before kissing the YL) I do every evening.
The idea that my ISP may disappear or some device in the long line of equipment
that it takes to make this work may break has me concerned. I want my Email and
other Internet applications running. I want an alternate route from the Internet back
to my computer. Being on the local Amateur TCP/IP network gives me this. It's not
fast enough (yet) to deal with web services like Yahoo, but it's more then adequate for
the basic Email and instant messaging.

Fourth and final reason is that, when this is all setup and running, it just may be needed
someday for community needs. The premise of our local group regarding Emergency
Communications is that the Internet outside of the area of an event will probably be
unaffected. It's making that hop from the still functioning infrastructure in to the area of
an event where Amateur Communications has real usefulness. My final goal for the home
system is to have the capabilities and robustness to be on line, running and providing
communication and data warehousing services for local community organizations if
something big ever happens.


I know this is a view very centered on the Internet style applications. It's what we're
using here and what I believe, is a reasonable future for Amateur Radio digital (packet)
applications. It makes far more sense in this age then going back to the packet BBS
systems which are essentially relatives of the land line BBS systems.

Enough rambling. Back to working on the system. I'm trying to get LDAP and IMAP
working by the end of the month.

73,
Bill - WA7NWP

posted to Northwest APRS group.

--

I had an idea to grab and use the Seattle traffic maps for JavAPRS. When I
started to look in to it - I found it would work even better then expected. Their
maps can be handled just like the Wx maps. So JavAPRS will use the traffic
map and both it and the APRS stations being overlayed will be updated
automatically on a regular basis.

www.jnos.org/cgi-bin/ja?wadot

The DOT map doesn't appear to be extremely accurate as far as lat/long locations
go. I've calibrated it against several of the major freeway intersections so it's close
but not exact. They are probably more concerned with the visual display then being
completely accurate with the map positions.

73,
Bill WA7NWP

to TAPR's NETSIG

Subject: [netsig] Re: [bbssig]


> >>n5pvl@tsarc.net wrote:
> >>
> >> I have no interest in participating in a flame war, on this or any
> >>other reflector. My interest is in discussion of RF networking.
> >>
> >> Will that be possible on the NET SIG?

These days Charles is the lone voice in the wilderness calling for a better
terrestrial packet network. His evangelism of a better node system (FlexNet)
and of the far more sensible broadcast technology like W2FS's Radio Mirror
should be commended and supported. He is preaching when our amateur
organizations are snoozing.

The lack of activity on this SIG is evidence that much of what he's saying is true.

No - I don't agree with him that we should totally turn off the wire line (telephone/Internet)
links. On the other hand, maybe that would have been better then what's actually
happened where it was many of the Amateur RF links that were turned off.

Ok fellow Netsig'ers. How many here have packet systems on the air right now? Can
you connect to the local network (nodes or whatever) and link around a bit? Will
your computer automatically send a message using Amateur resources to somebody
at least one town away? If not - turn it on...

The phone companies are in serious debt trouble, ISP's are rolling over, dirty bombs
are in the news. It may well be that our amateur resources and technology could soon
become far more relevant then it currently is.

At no time have we had better equipment. Computers are dirt cheap. RF boxes are
available off the shelf. There's some incredible stuff out there. It's the 802.11b
groups that are doing the fun networking. The amateurs are sitting on the sidelines this
time.

73,
Bill - WA7NWP

to Northwest APRS Sig:

> On the tinytrak I have smart beaconing enabled and set the digi path to RELAY,WIDE (good, bad, or ok?) and plan to
> experiment with lowering the TXD from the default of 250. Comments or suggestions?
> Ray KV4K

Hi Ray,

You're probably being a little too conservative. A TinyTrak is a set it and forget system that you
want to work anywhere you go. It's not like a home system where you have a known environment
that allows you to customize and tune the setup.

If you're staying in the PNW area and aren't beaconing too often, you'll want a bit longer
path. RELAY,WIDE3-3 is recommended.

I'd leave the TXD at 250 ms. If you go lower there may be digi's that can't respond fast
enough and your packets will be lost. It might work faster in your area - but you never know
if it'll still work when you're out on a drive being picked up by other digi's.

Speaking of TXD's - have any of the D7 owners on the list tried cutting back from the
default HALF SECOND to see how short a TXD can be used and still work? It would
be interesting to get that info for all of the local major WIDE nodes.

73,
Bill - WA7NWP

Another BBSSIG posting

>At 09:55 AM 6/20/02 +1000, Barry White wrote:
>Allright, I'll be the mug, "What is NewQPSK ?
>73 Barry VK2AAB

A multi-tone modem protocol that gives very good performance on HF
in a reasonable channel width. Performance can be up to twice what's
available on a 1200 baud packet system.

A full description taken from: http://www.qsl.net/zl1bpu/FUZZY/digital.html

---
NEWQPSK
Half Duplex, multi-tone QPSK, synchronous, linked, error correcting.
Developed by Pawel SP9VRC, NEWQPSK is a KISS/AX25 packet protocol with awesome performance. 15 individual tones are used, and each has QPSK modulation at 83.333 baud. The raw throughput is an impressive 2500 bits/sec. Each packet has a two phase preamble for fast synchronisation and frequency error correction. Data is spread in time and frequency, using a Walsh function, which provides redundancy, forward error correction and therefore significant robustness with respect to impulse noise and interference.
There are three FEC modes, none, light and strong, and the use of FEC significantly reduces the requirement for ARQ message repeat requests. In light FEC mode the throughput is 1833 bits/sec, while in strong FEC mode the throughput is an impressive 833 bits/sec, with the ability to correct up to three bit errors per character without requiring a repeat.
NEWQPSK operates on the Motorola DSP56002 EVM, which it operates just like a TNC. The unit will operate with any KISS interface packet software. NEWQPSK is suitable for HF or VHF, and on HF is capable of a throughput far in excess of conventional packet modes.
---


In addition to being good for HF, it fits transparently in to the Linux system. Thus there
are NO changes required for the application software.

Here's another web note on how some folks are going to be using this for HF messaging.
It's too long to copy the full note here - check it out:

http://lists.debian.org/debian-hams/2002/debian-hams-200203/msg00007.html


After a couple years of talking about this locally, we have a real opportunity to try it out. Next
month I'll be heading back to the Montana Glacier Waterton hamfest. http://www.gwhamfest.org
The goal is to maintain contact with the local Puget Sound network using a NewQPSK link.

Picture this - sitting at the picnic table (near) Glacier Park, enjoying a cold one, chatting with
old friends, and reading BBSSIG postings. The laptop on the table will be connected by
802.11b to the server in the car. That server is running TCP/IP over NewQPSK to pick up
mail and bulletins from another server near Seattle. Now that I think about it, it'll probably
be easy to chat real time over the Amateur Converse server at the same time.

73,
Bill - WA7NWP

Posted to BBSSIG...

---

At 08:56 AM 6/19/02 -0500, n5pvl@tsarc.net wrote:
My interest is in discussion of RF networking.


What is RF networking?

a) RELAY and WIDEN-N digipeaters used by APRS
b) NetRom/TheNet networks
c) Next generation Netrom systems such as FPAC and FlexNet
d) Nodeless systems using newer schemes such as NewQPSK
e) Nodeless systems using digital regenerators
...
z) all of the above


Personally I vote "z".

My Wetnet Linux box has 3 RF ports. One on a 9600 baud
digital regenerator. One on a two meter simplex frequency. The third is on
a second 9600 channel to feed a different network. It's not currently on the
local nor worldwide Node networks. Yet I'd still like to think I'm somewhat
involved in Amateur RF Networking.

(Near Future plans: get on the Netrom network, both locally on RF and on the
Internet system. Get NewQPSK running for HF connectivity.)

-----

BBSSIG group: What is a BBS?

a) legacy packet system running on DOS
b) current packet systems such as JNOS/TNOS/FBB
c) JNOS on an HP-95 palmtop
d) Linux/NetBSD box bringing Internet style Mail and News to RF
but with no legacy packet bulletins
...
z) all of the above


I vote Z again. There's an incredible array of technology to be discussed and implemented.

I recently turned off my TNOS BBS simply so I could focus on setting
up Internet tools on our local networks. There are 5 TNOS BBS's in the Puget Sound
area (that I know of) and they're doing a great job. I wish I had the time to
run a full TNOS system. It's an incredible piece of software with vastly under used
capabilities.

My (Wetnet) Linux system has no stand alone BBS program. An example
of how it's used would be changes yesterday to the News system so
mail discussions, like this one, will be available on the local RF network using
legacy Internet NewsGroups technology such as Pine, Forte Agent, Netscape, or
Outlook Express.

Today I plan to ask one of the local TNOS SYSOP's to start forwarding me some PBBS
traffic to be similarly mirrored as newsgroups. Is this a BBS? Is it relevant on
this discussion group? With the bandwidth available on a 9600 baud digital
repeater - it's trivial to pass even this quantity of traffic. (Broadcast mode
- like Radio Mirror - would be even better.) I believe it's all part of an evolving BBS world...

73,
Bill - WA7NWP

Progress on the Wetnet network front. Several of the mailing lists I subscribe to are now
being automatically posted to the INN news server on the Wetnet computer. It would have been
much simpler if my Eudora mailer didn't have a hidden feature that prevented automatically
sending mailing list Email via a filter. They were preventing mail loops. A good thing - but it was
tricky to find, and then tricky to disable.

That's the way it is with these computer projects. Every little 10 minute project ends up
taking two or three hours.

Another BBSSIG posting.

At 12:17 AM 6/18/02 -0500, n5pvl@tsarc.net wrote:
>You must have missed the part of my "Intro to FlexNet" article that mentions
>ethernet and IP drivers for the system. Lots of Hams in Europe use IP over
>FlexNet, and the FlexNetwork in the N.E. US has numerous IP routers built in
>to the system.

Ok.

IP runs over AX25 (legacy packet). AX25 runs over IP.

IP runs over Netrom. Netrom runs over IP.

IP runs over FlexNet.

...

Can FlexNet run over IP?

Bill

Another BBSSIG posting.

----- Original Message -----
From: "Jerome M. Kutche"


> Huh... Yes pvl is right... If it isn't R (Radio) F(frequency) it isn't
> Amateur RADIO...

What Bill is talking about is the "IP only" paradigm that emerged shortly
after Internet access became generally available.

bv: Who said "IP only"? Wasn't me. In fact I've never heard anybody say it.

This is the paradigm that
I have mentioned before that has dominated most Packet Radio conferences in
the U.S. for the past decade and has produced no significant ( Ham Radio )
network.

bv: In addition to the two non-significant Ham Radio networks I mentioned in a previous message
using the paradigm of local RF and world wide TCP/IP connections - APRS and WinLink -
I forgot to mention the DXCluster folks. They're doing the same. We also shouldn't
forget the existing BBS structure which still exists and handles a large volume of traffic.

Using non-Ham links has been illegal in most of Europe during the last
decade, which goes far in explaining why their digital RF network is 10-15
years ahead of anything we have here. They never quit using radio, and so
were able to develop their RF net into something truly advanced, truly
remarkable.

bv: If all we had was Morse Code, those few of us left would be truly remarkable
Morse Code operators.

bv: Other issues, such as population densities, available frequencies and amount
of terrain to be covered are involved in explaining the differences between the
existing European and American networks.

bv: They've done some great work to be proud of and there are lessons we can
learn, but I sure wouldn't give them 10-15 years. Maybe 1 or 2.

there is nothing about it which advances our ability to build Ham Radio
digital network, either. What you can do over non-Ham links is basically
irrelevant to Packet Radio networking.

bv: Are you saying that the only thing that's relevant to a Ham Radio digital
network is AX25 traffic using re-invented custom AX25 programs?

bv: Are you saying that because I Telnet (an Internet TCP tool/protocol) to a
computer at the University in Vancouver BC it's not a Ham Radio digital
network. That it's not relevant. Even if the 150 mile circuit is three
or four different RF links on various frequencies and baud rates - including
a 56K digital repeater? The routing is automatic and transparent. The
software is standard on Windows and Linux systems.

bv: Are you saying we should purposefully disconnect this system from the Internet
so nobody else from around the world can use it? That would be progress?

bv: That disconnecting it so we can't use it to get to the rest of the world through
it would be progress?

I think we would be wasting our time and raising the noise level here to no
purpose, by debating the relative merits of the two paradigm. What Bill does
may not be relevant to digital Ham Radio networking, but since it does not
use Ham Radio for network, it doesn't do any harm either.

bv: There is nothing to debate. The Internet "technology" and paradigm is here to stay.
Horse drawn carriages are fun but they'll never take the place of modern transportation.

bv: What's truly relevant is turning on packet systems. We have to get stations and
networks on the air. There is no bad "packet" system. Turn it on today - make
it better tomorrow. Make packets! Try new systems. Improve the old ones. Let
the system as a whole evolve to better performance and increased usefulness.

Charles, N5PVL

bv: Bill, WA7NWP

# posted by Bill @ 10:30 AM

Attended Redmond A.R.E.S. meeting last night. Small group but it's looking better. Web Page This should be a good digital opportunity.

A posting made to BBSSIG in response to Charles comments.

> > telnet n4xeo.ampr.org
>
>Sorry, Bill, you must have gotten confused as to which reflector you are on.
>This one is concerned with Ham Radio issues, I'm sure there are plenty of
>others that cover Internet related stuff. Amateur Radio operators work with
>and are primarily concerned with ( surprise! ) Amateur Radio.
>
>Charles, N5PVL


AMPR.ORG ==> AMateur Packet Radio (dot) Org..


That's Amateur (packet) Radio leveraging the power and connectivity of the Internet
and related tools. Great stuff!


http://www.ampr.org


Here's an interesting story of one advantage to running AX25 and having an .AMPR.ORG
connection. A local fellow, at work, goofed up the routing on his home computer hooked
to the Internet via DSL. The routing was broke and he couldn't connect to it - via DSL. Since
he was also on .ampr.org - he made a connection home on that alternate circuit, fixed
the problem and was back on line. This took minutes instead of waiting for hours until
getting home from work. Not bad for a 1200 baud connection on two meters.

73,
Bill - WA7NWP

Much of my time and energy is devoted to Amateur Radio activities. Too much to keep it grouped with other work and personal commentary. So now we'll have a unique, WA7NWP, amateur radio blog.