Jnos Operators Guideby John Martin KF8KK Converse and Telnet
|
|
| One of the more useful functions often found in Jnos nodes
is the Converse mode.
Converse allows multiple jnos users to talk amongst each other, whether the users are all logged into a particular jnos node, or if they are logged into a remote jnos node that is linked into the conference. You can look at the converse mode as the ham equivalent of a multi-room chat server. In 'CONV' you can select a 'CHANNEL' to use and converse with other hams in that 'CHANNEL' just as people do on any of the common internet chat systems (instant messaging, etc).
|
 |
| In Michigan, the ARPSC Jnos nodes are setup
to link their converse modes to a statewide converse server.
This allows multi-user conversations to take place statewide. It has been determined that the numbered county designator for the county a node is in determines the default 'channel' users from that node use. This is especially handy should there be an event in a particular county as officials from across the state will know what 'channel' to convene on in order to provide support for a particular county. It also allows for individual counties to organize their efforts without being disturbed by similar traffic from other counties if the event encompassed more than one county.. |
|
| To enter converse, issue the 'CONV' command.
As you can see from the listing in the above photo, the converse mode has it's own commands. '/w' lets you know who else is on converse. It does show users on all channels on the linked servers. '/L' will show any linked servers. Washtenaw is the main converse hub in Michigan. '/ch' shows a listing of just a few of the available channels. There are something like 36,000 channels available. This listing is created locally as a convenience to the users. As a 'thanks' to my friend Craig N8KMY I assigned him his very own converse channel #1002-- isn't that nice! '/ch <chnl #>' will change your station to using a different channel. '/b' exits the converse mode.
|
 |
Telnet via Jnos |
|
| Jnos provides a full Telnet client that allows you to
telnet to other computers across the internet.
You are NOT limited to Jnos computers-- you can telnet to any computer that accepts telnet connections. Telnet provides a handy method to make a connection to other packet hamgates across the world. It is via this telnet capability that a station can enter the Jnos node via the radio in one part of the state, telnet across the internet to another Jnos node elsewhere, and then come back out on the radio in that distant location. |
 |
| In the image above where I'm connecting to the HamGate.Washtenaw.AMPR.org via telnet, I am greeted by a normal Jnos login screen. Once I am connected I can use all the Jnos commands on the Washtenaw system. | |
 |
|
| As you can see from the image above, the look
of the Washtenaw jnos system is very much like that of Leelanau.
I issued the 'P' for 'PORTS' command and find that a 145.76 port is available. You will note there is no 'N' command, the 'N' command is only available if the NetRom function is available on that node. Once you get setup on Jnos you should send an email to Jay TKL and tell him he's missing out on all the NetRom action! [but please don't tell him I suggested you write him-- he'll have my head]. Below you can see the result of issuing the 'J' for 'J-HEARD' command that allows you to see what stations were heard by the system. You will note Ulrich, DH0GHU on the heard list. Ulrich certainly didn't enter the system via 145.76mhz, but he was able to telnet into the system via the internet and access our packet system from Germany. |
|
 |
|
Jnos Operators Guide:Introduction
|
|