Jnos Operators Guideby John Martin KF8KK Ports and Outbound Connections
|
|
| Now that you've successfully logged into the Jnos node, you
need to figure out what the system has to offer.
The I or INFO command should display a text file that the system operator created that describes what capabilities this jnos system has to offer. Hopefully, this file is accurate and not too large in size for the link you are using to connect (I can see that I need to update mine!).
|
 |
| After you have read the INFO provided by the
I command,
you should issue the 'P' command to get a readout of the available
PORTS.
Jnos allows for the connection of many different 'ports' for connecting into and out of the system. Many Jnos systems are equipped with more than one radio port, and therefore are not just BBS's with an internet gateway, but actual RF crossband gateways too. When you issue the 'P' command it shows the available 'AX.25' (that's 'packet radio' if you're new to this) ports that are connected to the Jnos node.
|
 |
Standard AX.25 connections: |
|
| You need to know the ports available in order to make an
outbound packet connection.
If you just type 'C' for 'Connect' you will get some helpful hints as to how to properly format your connect request command. |
 |
| For example, I will enter the command to connect via the
145.09 port to the COLBBS mailbox.
To make this connection I type the following: C 145.09 colbbs
|
 |
| As you can see above, the connection was successful. If there was a problem and I needed to abort the connection, I could have typed the CTRL-T (hold down the 'control' key and hit T at the same time). | |
| If I wanted to use a digipeater in the path I would issue
the following command:
C 145.09 colbbs v grtr00 Whereas 'grtr00' is the digi. |
 |
NetRom / TheNet connections: |
|
| In areas where NetRom is in use
[TheNet X1j nodes function
as NetRom] the connections are a bit easier to make in Jnos as you don't
have to specify the port.
NetRom nodes exchange routing information amongst the nodes that allow the users to make connections without having to worry about the underlying network paths. |
 |
| In the case of my jnos system, issuing the
'N'
command for 'Nodes' shows a short list of the available nodes I can
connect through.
You can see there are four nodes shown. The node 'alias' is shown first, then a colon, then the callsign of the node. |
|
| I know that the BEN11 node is the main 145.07 node in the
area and I can connect to it by issuing the simple command:
C BEN11
|
 |
| Ancillary
Comment:
NetRom is a wonderful mode. 'BEN11' is accessible as one of the ports on the three port node stack in Empire, MI. My Jnos system uses a 433.1mhz UHF transceiver to connect to the node via the 'BEN12' port. Access to the BENQMN, BEN11, is via the internal wiring of the Empire node. If I were to connect to the 'BEN00' node in Benzonia,MI. The NetRom system would connect me automatically through BEN12, then to BEN11 and then across 145.07 to BEN00 which is about 20 miles south of the Empire node. All I would need to do is issue the 'C BEN00' command and all the connections would be setup automatically for me. |
|
| When I issued the 'B' command to the
BEN11 node I was
returned to my 'KKBBS' jnos system.
Please note in the 'alphabet soup' line the word EMPIRE near the beginning.
|
 |
| EMPIRE is a special 'alias' command that will
make the NetRom connection to the BEN11 node. It's been added as
an operator convenience.
If a user forgets the route to the primary local frequency of 145.07, or to BEN11, they can just type 'EMPIRE' and the jnos system will take them there. Any commands shown BEFORE the '?' in the list are 'alias commands' created by the system operator for the convenience of the system users. |
|
Jnos Operators Guide:Introduction
|
|