<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
Seems like good advise Bob.<BR>
THANKS! (topic expansion that does not require response follows)...<BR>
<BR>
On Wed, 2006-10-04 at 11:45 -0700, kd7nm wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hi Skip,</FONT>
<FONT COLOR="#000000">What you're talking about here are two different issues.</FONT>
</PRE>
</BLOCKQUOTE>
Actually it runs deeper than jnos and two issues, but jnos is probably destined to become a greater portion of the software mix.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> </FONT>
<FONT COLOR="#000000">SSID's were developed as a means, within the AX.25 protocol,</FONT>
<FONT COLOR="#000000">of supporting one ham having more than one station operating</FONT>
<FONT COLOR="#000000">on the same frequency and LAN at the same time.</FONT>
</PRE>
</BLOCKQUOTE>
Yes - I get the "one-licensee" mentality that we are breaking here. And I'd like to resolve it without using the thought of "go ahead with anything because it is an 'emergency' so anything goes". I also see how messy carrying the SSID everywhere can get...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Convers extracts the callsign from the connection to use as</FONT>
<FONT COLOR="#000000">a method of identifying a user. Converse wasn't designed to</FONT>
<FONT COLOR="#000000">sensibly interpret more than one connection under the same</FONT>
<FONT COLOR="#000000">call, since it's a relatively rare circumstance that one ham</FONT>
<FONT COLOR="#000000">will end up connecting via more than one TNC to the same</FONT>
<FONT COLOR="#000000">convers network. </FONT>
</PRE>
</BLOCKQUOTE>
Yes - and this seems to apply for other services as well. Mail for example... Now response mail ends up at a central mail queue and not at the station with the SSID.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">However, if memory serves, convers servers</FONT>
<FONT COLOR="#000000">can be told that a particular connection should use a</FONT>
<FONT COLOR="#000000">different nickname. That might be a way to handle multiple</FONT>
<FONT COLOR="#000000">sites with a common base callsign.</FONT>
</PRE>
</BLOCKQUOTE>
HMMM
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Another way to deal with the problem is to use tactical</FONT>
<FONT COLOR="#000000">callsigns in the "ax25 mycall" setting that uniquely</FONT>
<FONT COLOR="#000000">identify each workstation, something like CTYEOC and FIRE12,</FONT>
<FONT COLOR="#000000">then set up appropriate ID beacons, that contain the legal</FONT>
<FONT COLOR="#000000">ID text (the host amateur callsign) that is transmitted</FONT>
<FONT COLOR="#000000">every 9.9 minutes that the station is in use transmitting</FONT>
<FONT COLOR="#000000">packets using that tactical callsign. Not sure if JNOS</FONT>
<FONT COLOR="#000000">knows how to do that, but it's probably worthy of</FONT>
<FONT COLOR="#000000">consideration as an addition to the program, if not.</FONT>
</PRE>
</BLOCKQUOTE>
I like this thought - it seems to be a nice fit to our deployment planning. If it meets legal tests and software restraints, we could train users on this model. We have been developing toward a model using mailto: <A HREF="mailto:title@workstation">title@workstation</A> without having all the questions resolved...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">73, Bob, KD7NM</FONT>
<FONT COLOR="#000000">----- Original Message Follows -----</FONT>
<FONT COLOR="#000000">From: "(Skip) K8RRA" <<A HREF="mailto:k8rra@ameritech.net">k8rra@ameritech.net</A>></FONT>
<FONT COLOR="#000000">To: TAPR xNOS - Mail List <<A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A>></FONT>
<FONT COLOR="#000000">Subject: [nos-bbs] SSID issue detail</FONT>
<FONT COLOR="#000000">Date: Wed, 04 Oct 2006 10:56:37 -0400</FONT>
<FONT COLOR="#000000">>Greetings to all.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>I have a new-found issue going on with station ID at the</FONT>
<FONT COLOR="#000000">>root. My special situation is in configuring four portable</FONT>
<FONT COLOR="#000000">>workstations for event and emergency deployment.</FONT>
<FONT COLOR="#000000">>These are all held my the County of Ottawa with an FCC</FONT>
<FONT COLOR="#000000">>license to the organization.</FONT>
<FONT COLOR="#000000">>The planned strategy was to ID the stations with SSID</FONT>
<FONT COLOR="#000000">>series -10, -11, -12, -13.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>While an AX.25 connect is in effect and participating in a</FONT>
<FONT COLOR="#000000">>CONV session: At the sysop console - </FONT>
<FONT COLOR="#000000">>ax25 status shows ID of the type kc8lcp-11 and kc8clp-12 /</FONT>
<FONT COLOR="#000000">>appropriate to the configurations.</FONT>
<FONT COLOR="#000000">>converse /w shows ID of the type kc8lcp kc8lcp / missing</FONT>
<FONT COLOR="#000000">>the SSID detail thus unknown author.</FONT>
<FONT COLOR="#000000">>The sysop header shows ID of the type ^kc8lcp ^kc8lcp /</FONT>
<FONT COLOR="#000000">>missing the SSID.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>I did not go deeper at the moment, I conclude a revision is</FONT>
<FONT COLOR="#000000">>needed if our configuration is to be used in the intended</FONT>
<FONT COLOR="#000000">>manner. Clearly the SSID is used at the most basic level</FONT>
<FONT COLOR="#000000">>but in some places it is dropped.</FONT>
<FONT COLOR="#000000">>I presume multiple SSIDs with one call was not a planned</FONT>
<FONT COLOR="#000000">>network configuration during jnos design?</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>My question to this group is to ask for similar</FONT>
<FONT COLOR="#000000">>experiences. Would the adjustment to jnos source code to</FONT>
<FONT COLOR="#000000">>accommodate a group License be easier than instituting</FONT>
<FONT COLOR="#000000">>personal licenses at each station? Another slick solution</FONT>
<FONT COLOR="#000000">>already in hand somewhere?</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>73</FONT>
<FONT COLOR="#000000">>de [George (Skip) VerDuin] K8RRA k</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">>_______________________________________________</FONT>
<FONT COLOR="#000000">>nos-bbs mailing list</FONT>
<FONT COLOR="#000000">><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000">><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>