[nos-bbs] SSID issue detail
(Skip) K8RRA
k8rra at ameritech.net
Wed Oct 4 18:02:58 EDT 2006
Seems like good advise Bob.
THANKS! (topic expansion that does not require response follows)...
On Wed, 2006-10-04 at 11:45 -0700, kd7nm wrote:
> Hi Skip,
>
> What you're talking about here are two different issues.
Actually it runs deeper than jnos and two issues, but jnos is probably
destined to become a greater portion of the software mix.
>
>
> SSID's were developed as a means, within the AX.25 protocol,
> of supporting one ham having more than one station operating
> on the same frequency and LAN at the same time.
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...
>
> Convers extracts the callsign from the connection to use as
> a method of identifying a user. Converse wasn't designed to
> sensibly interpret more than one connection under the same
> call, since it's a relatively rare circumstance that one ham
> will end up connecting via more than one TNC to the same
> convers network.
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.
> However, if memory serves, convers servers
> can be told that a particular connection should use a
> different nickname. That might be a way to handle multiple
> sites with a common base callsign.
HMMM
>
> Another way to deal with the problem is to use tactical
> callsigns in the "ax25 mycall" setting that uniquely
> identify each workstation, something like CTYEOC and FIRE12,
> then set up appropriate ID beacons, that contain the legal
> ID text (the host amateur callsign) that is transmitted
> every 9.9 minutes that the station is in use transmitting
> packets using that tactical callsign. Not sure if JNOS
> knows how to do that, but it's probably worthy of
> consideration as an addition to the program, if not.
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: title at workstation without having all the questions resolved...
>
> 73, Bob, KD7NM
>
> ----- Original Message Follows -----
> From: "(Skip) K8RRA" <k8rra at ameritech.net>
> To: TAPR xNOS - Mail List <nos-bbs at lists.tapr.org>
> Subject: [nos-bbs] SSID issue detail
> Date: Wed, 04 Oct 2006 10:56:37 -0400
>
> >Greetings to all.
> >
> >I have a new-found issue going on with station ID at the
> >root. My special situation is in configuring four portable
> >workstations for event and emergency deployment.
> >These are all held my the County of Ottawa with an FCC
> >license to the organization.
> >The planned strategy was to ID the stations with SSID
> >series -10, -11, -12, -13.
> >
> >While an AX.25 connect is in effect and participating in a
> >CONV session: At the sysop console -
> >ax25 status shows ID of the type kc8lcp-11 and kc8clp-12 /
> >appropriate to the configurations.
> >converse /w shows ID of the type kc8lcp kc8lcp / missing
> >the SSID detail thus unknown author.
> >The sysop header shows ID of the type ^kc8lcp ^kc8lcp /
> >missing the SSID.
> >
> >I did not go deeper at the moment, I conclude a revision is
> >needed if our configuration is to be used in the intended
> >manner. Clearly the SSID is used at the most basic level
> >but in some places it is dropped.
> >I presume multiple SSIDs with one call was not a planned
> >network configuration during jnos design?
> >
> >My question to this group is to ask for similar
> >experiences. Would the adjustment to jnos source code to
> >accommodate a group License be easier than instituting
> >personal licenses at each station? Another slick solution
> >already in hand somewhere?
> >
> >73
> >de [George (Skip) VerDuin] K8RRA k
> >
> >
> >_______________________________________________
> >nos-bbs mailing list
> >nos-bbs at lists.tapr.org
> >https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> >
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
73
de [George (Skip) VerDuin] K8RRA k
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20061004/d9e74499/attachment.html>
More information about the nos-bbs
mailing list