This page contains the basic reference information a network mapper needs.
In the following, the "typewriter text" is text that is input or output of a TNC. Text that is colored Red is text that is written TO the TNC. The character "C/R" represents an end-of-line generated by pressing the "return" key on a Macintosh keyboard or the "enter" key on a PC keyboard.
The types that will be described are:
Check the G8BQP entry first for initial information. If anyone would like help decoding any other type of NET/ROM-based node data, you are welcome to contact the author for assistance.
U<C/R>
WSALEM:N7IFJ-6} G8BPQ Packet Switch V4.07a for Data Engine (142)
Uplink 1(KA7EHK)
I<C/R>
WSALEM:N7IFJ-6} N7IFJ WSALEM Packet Switch located on Popcorn Hill, West Salem,
Oregon
Sponsored by Mid-Valley ARES.
Running on a Kantronics Data Engine. To connect to another station (not
another NODE), you must specify a port number before the callsign. Use
the format C # XXXXXX, where # is the port number and XXXXXX is the callsign
to which you wish to connect. Use the PORTS command to list the available
ports.
R<C/R>
WSALEM:N7IFJ-6} Routes:
1 W7OSU-1 192 1
> 3 N7IFJ-5 224 79
1 KA7UPD-1 192 78
1 N7PDX-3 192 16
P<C/R>
WSALEM:N7IFJ-6} Ports:
1 144.970 (1200)
2 70cm North (9600)
3 70cm South (9600)
If we look at the contents of this response from the node, it can be seen that there is one line for every neighbor in direct radio contact with this node. This particular node type tells us only the callsign of the node; others give the node name, or both the call and the name. In this case, their are four immediate neighbors.
Just to the right of each call, there is a number. This number can vary from 1 to 255. It is the "quality" of the link; the bigger the number, the higher the quality. Three of the neighbors have a quality of 192 and one has a quality of 224. The quality is set by the person who tends the node. Usually, there is a default quality that is assigned to any node heard from; in this case, it is probably 192. If appropriate, the quality can be set differently on a node-by-node basis; this was likely done for the N7IFJ-5 neighbor and we will see the probable reason in a bit.
The last number tells how large the node list is for each of the neighbors. For example, W7OSU-1 only has one node listed in its node list while KA7UPD-1 has 79.
Lets go back to the beginning of each line. Immediately ahead of each node call is a number. For this node, those numbers are "1" and "3". Generally, this number tells which "port" the connection is on. There is a big difference how this is denoted in different node types. In G8BPQ nodes, one node can connect to several radios. Each radio is a "port" and they are numbered. We can tell which is which by sending a "P" (again, no quotes and followed by a carriage return) to the node to request the ports-list. Here is the list from that node:
Now, we can see that all of the 192-quality links are on 144.970MHz while the 224-quality link is on a 9600-baud backbone.
Finally, one entry in the route list begins with a ".>". This simply indicates that that link is in use
Oh, how do you find out the node type in order to know how to interpret these list? Send a ".U". (for Users) to the node. In this case it returns:
The identification of the node software should be quite clear.
U<C/R>
#WALK2:W7SLA-11} TheNet X-1J4 (615
Circuit(LYONS:KA7UPD-1 KA7EHK)
R<C/R>
#WALK2:W7SLA-11} Routes:
1 WALKER:W7SLA-1 255 70
> 1 #WALK4:W7SLA-10 255
0 KB7DBD-12 0 0
> 0 #LNEC:W7EUG-11 224 11
> 0 LYONS:KA7UPD-1 224 11
0 #FLO:W7FLO-11 224 7
I<C/R>
#WALK2:W7SLA-11}
Site Location is Walker Point, 2400 AMSL, West of Eugene, OR
Backbone Node, 223 MH
Access LAN = WALKER W7SLA-1 on 145.06 MHz
Sysop contact: joeb@clipper.net
The User response, as in G8BPQ, told us the node type. The route list includes both the node call and the node name. The route quality numbers and the node list count numbers are interpreted the same. The ">" at the beginning of the line has the same meaning. But, the port number is interpreted differently. And, as will be seen, that is the reason the Info response is included.
TheNet nodes are different from G8BPQ in that there is a separate TNC for each radio. The TNCs are all interconnected in a "ring". To any TNC on the ring, any other TNC on the ring is a port "1". Any station heard over the radio is a port "0" station. Thus, we can tell in this node-stack that #WALK2 (the node that provided the information), #WALK4, and WALKER, are all part of the same node-stack. The nodes #LNEC, LYONS, and #FLO are heard from this TNC's own radio.
TheNet has no ports list. So, there is nothing designed to provide information about the different ports. You can only hope that the node-op put in something in the information response to tell about the operating frequency. If there is nothing, then perhaps one of the other nodes heard by radio will say something.
U<C/R>
GORGE:KB7DRX-5} K-net Packet Switch v1.0 (48)
Circuit(JENNE:N7QDN-1 KA7EHK)
I<C/R>
GORGE:KB7DRX-5}
GORGE User Port and Western Link
R<C/R>
GORGE:KB7DRX-5} Routes:
0 KC7KCQ-10 250 19
1 KB7DRX-6 192 1
1 WA7V-7 192 1
> 2 N7QDN-1 224 37
1 KF7LN-2 192 2
1 N7PDX-3 192 3
P<C/R>
GORGE:KB7DRX-5} Ports:
Port 1: 144.970 1200 Baud
Port 2: 424.850 9600 Baud
This node has two radio ports, numbered 1 and 2. Port 0 is a wired connection to another TNC in the node stack.
ESALEM:N7IFJ-4} Connected to IFJNOD:N7IFJ-2
U<C/R>
AX.25 node connections:
Node Call Channel Port
N7IFJ-4 3 0
Node cmd?
i<C/R>
IFJNOD:N7IFJ-2} MSYS Node in Salem OR 97301 [BBS call is N7IFJ]
Node cmd?
r<C/R>
IFJNOD:N7IFJ-2} Routes:
Port Neighbor Node Call Quality Dests Heard Digipeater(s)
0 ESALEM:N7IFJ-4 200 99 02:31
Node cmd?
P<C/R>
Port 0 is HARDWIRE
Port 1 is TOR
Node cmd?
With MSYS nodes, the word "MSYS" usually seems to appear in the Info response. The Route list should be familiar now, assisted by the Ports list that follows.
ESALEM:N7IFJ-4} Connected to ORCAP:KD7HAH-2
ORCAP:KD7HAH-2 Welcome to kd7hah.ampr.org network node
- ORCAP - Help: ?
*** Welcome to system ****
Location: Salem Oregon USA
Now in WEST Salem
email: kd7hah@kd7hah.or.usa.noam or kevin@kd7hah.com
**** Have fun ***--
U<C/R>
ORCAP:KD7HAH-2 Users:
Circuit (KA7EHK ESALEM:N7IFJ-4) -> Idle (0:00:00:00)
R<C/R>
Routes
ORCAP:KD7HAH-2 Routes:
Link Port Callsign Quality Destinations Lock
> 2 W7NTF-8 230 889 !
2 WB7AWL-15 230 85 !
> 2 VK6HGR-15 230 163 !
> 2 WB0TAX-7 230 494 !
4 KD7HAH-10 230 1 !
> 2 GW3UWS-14 230 8 !
2 VK7HDM-6 230 113 !
2 GB7CIP-5 230 16 !
> 2 PU2TIY-10 230 437 !
2 VK3TE-9 230 308 !
> 1 N7IFJ-4 192 108
P<C/R>
ORCAP:KD7HAH-2 Ports:
Port Description
1 145.010 MHz (Link to ESALEM - 1200 Baud)
2 AXIP Link
4 Link To TNOS
I<C/R>
ORCAP:KD7HAH-2 LinuxNode v0.3.0
Welcome To The KD7HAH Linux Node In Salem, OR 97304
________________________________________________________
This system is open to the general amatuer community and
you're free to use it, look around and make use of it.
(That's why it's here..!!!)
Type help or ? for info on how to use this thing.
To connect to the BBS type "BBS".
To connect to World Wide Conference Bridge type "CONV".
You can make ax25, netrom or telnet connections to
other systems in the local community and around the
world..!!!!
This node is accesable via ax25, netrom or telnet
connection to 44.26.2.10 or to kd7hah.ampr.org.
The port number is 3694.
________________________________________________________
73's es Enjoy!
Kevin - KD7HAH
The first real surprise is the routes list. There are a number of stations listed in the routs list that simply could NOT have radio connections, on VHF, anyway. The ports list tells you what is happening. In this case, Port 1 is the radio link. Port 2 is the link via internet and that is the port that the strange calls appear on. Port 4 is a local connection, probably ethernet, to bbs software. The Info response finally tells you what the software is.
KAMLPS:VE7TSI-3 Connected to SFU:VE7SFU
Welcome ka7ehk,
to the VE7SFU TCP/IP Server (JNOS 1.11f (Linux)).
Currently 2 users.
********************************************************
Welcome to the VE7SFU gateway.
To connect to the VE7CC DX Cluster please disconnect from
here and telnet to dxc.ve7cc.net or else enter "DXC2"
********************************************************
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
nr<C/R>
Routes :
Neighbour Port Qual Obs Dest Tries Retries Perc Irtt
YVRASS:VE7ASS-3 ax1 200 5 8 14 75 15 %
YVRCC:VE7CC-4 ax0 200 5 1 18 6 75 %
YVRKIT:VE7KIT-10 (BPQ) ax0 200 5 10 87 26 76 %
NSARC:VE7NSR-3 ax1 200 5 7 20 9 68 %
WADG:WA7DG Nev 200 5 3 22 0 100 %
YVRVBS:VE7VBS-3 (BPQ) ax1 200 4 14 27 23 54 %
HAMS:VE3MCH-6 ve3 200 5 641 335 17 95 %
KAMLPS:VE7TSI-3 Kam 200 5 92 5 2 71 %
YVRIHL:VE7IHL-3 ax1 200 5 1 12 23 34 %
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
ports<C/R>
Available ports:
Edm : Edmonton Ab ve6dxx
Utah : Utah nc7j
py5 : Brazil py5mcb
Mel : Melbourne Aust vk3rpa
ve5 : Saskatoon Sk ve5us
Kam : Kamloops BC ve7tsi
Nev : Reno Nevada n7rh
kl7 : Anchorage Ak nl7nc-9
yyc : Calgary Ab ve6yyc
ve6 : Calgary Ab ve6ipg
ve3 : Hamilton On ve3mch
w5 : Louisianna wu3v
w6 : SF Ca ka6eyh-6
w7 : Talent Ore wb7awl
Spok : Spokane Wa ws7i
Sea : Seattle Wa n7nei
Tax : wb0tax-7
ax1 : 440.775 +5 - 9600 baud
ax0 : 441.05 MHz - 9600 baud
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
User<C/R>
Huh?
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
U<C/R>
Usage: U
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
info<C/R>
JNOS version 1.11f (Linux)
Welcome to hamgate.ve7sfu.ampr.org The system is remotely maintained by
Lee, VE7CC and Lane, VE7IHL. It is currently a JNOS server with AX25
tunneling, NET/ROM, Telnet, SMTP and Finger. Note that it is not possible
to send messages from this system.
To get help, type 'H' (without the quotes).
Equipment:
50 MHz 486DX PC, 10G Hard Disk
one radio on 441.050 MHz 9600Bd
one radio on 440.775+ MHz 9600Bd
If you are interested in learning more or have questions
regarding the use of the system, tcpip services etc...
Telnet to ve7cc and send a message to 've7cc'.
Please remember to leave a reply address so he can answer.
73 de VE7CC/VE7IHL
DXC2,BBS,DXC,?,B,C,D,E,H,I,IH,IP,J,M,N,NR,P,PI,T,U,W,X,Z >
There are several important things to note about JNOS. There is no "routes" command; instead the command is "nr" which stands for "netrom routes". Second, the ports are named differently. Third, the routes list looks a little different. Here is how to interpret the route list:
There is another notable thing about this route list. There are ports listed for a lot of nodes that are not present in the route list. Apparently, the route list has not been updated in some time and the absent nodes are simply not functioning any more.
TACOMA:W7NTF-8 Connected to KAMLPS:VE7TSI-3 (Escape: CTRL-T)
[TNOS-2.40-BFHIMW$]
Welcome to VE7TSI.
Please note. I have been having problems with spammers using VE7TSI as a mail
relay recently. If you are having problems with internet email, it is
probably related to that. I hope to have this fixed soon so please bear with
me.
Sending the ? will get a short list of available commands while H will get the
complete list. INFO will get you into the TNOS info center. Please leave a
message for ve7eje@ve7tsi or ve7eje@ve7rxd if you have any questions.
Welcome ka7ehk, to the VE7TSI-5 TCP/IP BBS (KO4KS-TNOS/Unix v2.40/ELF)
Last on the BBS: Fri Nov 7 23:02:23 2003
You are the only user currently on the BBS
For help on using this system type 'TUTOR'. For other information type 'INFO'
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
routes<C/R>
Huh?
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
nr<C/R>
Routes :
Neighbour Port PQual Obsocnt Dest Tries Retries Perc
#MONTE:VE7RXX-1 uhf 193 6 5 4 3 57 %
> BOSCTY:WB0TAX-7 wh7 230 6 834 240 23 91 %
#YKAL:VE7RKA-4 uhf 193 6 1 0 0 0 %
> VARPA:VE7VPR wh5 230 6 11 147 2 98 %
EDGATE:VE6UOA-7 wh18 230 6 1 6 0 100 %
VDAGW:N5VDA-3 wh2 230 6 89 393 83 82 %
HAMS:VE3MCH-6 wh30 230 6 946 561 17 97 %
> RXD:VE7RXD-3 uhf 193 6 7 87 13 87 %
> TACOMA:W7NTF-8 wh19 230 6 283 1305 533 71 %
HARGW:VE2HAR-9 wh29 230 6 18 0 0 0 %
SWANIP:GW3UWS-14 wh8 230 6 8 40 0 100 %
EAGLES:VE1ATT-7 wh14 230 6 820 225 81 73 %
SFU:VE7SFU wh10 230 6 36 41 0 100 %
MONTE:VE7RXX vhf 192 6 5 0 0 0 %
PMF:HA3PMF-4 wh21 230 6 657 2 22 8 %
NBGATE:VE9EMO-8 wh15 230 5 11 0 0 0 %
ALWGW:WA7V-8 wh12 230 6 650 32 0 100 %
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
ports<C/R>
Available ports:
wh29 : AXIP/Netrom link to Quebec - VE2HAR
wh22 : AXUDP/Netrom link to Quebec - VE2PKT
wh30 : AXIP/Netrom link to Hamilton, On - VE3MCH
wh28 : AXIP/Netrom link to Trois-Rivieres - VA2TRG
wh27 : AXIP/Netrom link to Melbourne, Aus. - VK3RPA
wh26 : AXIP/Netrom link to Brazil - PP5AQ
wh25 : AXIP/Netrom link to Melbourne, Aus. - VK3FRS
wh24 : AXIP/Netrom link to Belgium - ON6DP-9
wh23 : AXIP/Netrom link to Romania - YO7JYL
wh21 : AXIP/Netrom link to Pecs, Hungary - HA3PMF
wh20 : AXIP/Netrom link to Calgary, AB - VE6YYC
wh19 : AXIP/Netrom link to Spanaway, Wa - W7NTF
wh18 : AXIP/Netrom link to Edmonton, AB - VE6UOA
wh17 : AXIP/Netrom link to Minnisota - KB0KQA
wh16 : AXIP/Netrom link to Toronto, Ontario - VE3THA
wh15 : AXIP/Netrom link to New Brunswick - VE9EMO
wh14 : AXIP/Netrom link to Sheffield Mills, NS - VE1ATT
wh13 : AXIP/Netrom link to Montreal, PQ - VE2CEV
wh12 : AXIP/Netrom link to Walla Walla, WA - WA7V
wh11 : AXIP/Netrom link to Quebec - VE2HAR
wh10 : AXIP only link to SFU Vancouver, BC - VE7SFU
wh9 : AXIP/Netrom link to Oregon - WB7AWL
wh8 : AXIP/Netrom link to Swansea, Wales - GW3UWS
wh7 : AXIP/Netrom link to Louisiana - WB0TAX
wh6 : AXIP/Netrom link to - VE1JOT
wh5 : AXIP/Netrom link to Victoria, BC - VE7VPR
wh4 : AXIP/Netrom link to Calgary, AB - VE6IPG
wh3 : AXIP/Netrom link to Palm Springs, CA - AA6HF
wh2 : AXIP/Netrom link to Houston, Texas - N5VDA
wh1 : AXIP/Netrom link to Lethbridge, AB - VE6LIP
uhf : 447.475/442.475 Mhz. -9600 bd.
vhf : 145.050 Mhz. -1200 bd.
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
info<C/R>
Welcome to the TNOS Information Center at ve7tsi.ampr.org
0 - Exit Information Center
C - Enable ANSI Color Graphics
Enter Selection:
0<C/R>
Thanks for using the TNOS Information Center at ve7tsi.ampr.org
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
User<C/R>
Past users:
User Logins Time since last User Logins Time since last
ve7rxd 11 0:00:03:07 : ka7ehk 1 0:00:05:59
ve7lll 1 0:00:32:51 : guenterve7lll 1 0:00:34:19
ve7die 10 0:00:47:13 : dh7vsj 1 0:04:31:34
dj2rt 1 0:05:09:01 : w7ntf 1 0:05:13:26
ve1att 1 0:05:13:27 : gw3uws 1 0:05:15:03
Area: 'ka7ehk' Current msg# 0 of 0.
?,A,APRS,B,BBS,C,D,DX,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y>
Again, we see a route list that is very much like that of JNOS. Here, however, the "routes" command is valid! And, there is a user command. There is no information return that is usable by packet users via RF; tcp/ip users should be able to get the info return.
ESALEM:N7IFJ-4} Connected to CEDAR:K7IQI-1
U<C/R>
CEDAR:K7IQI-1} SNOS 8.2 by W0RLI cedar.k7iqi.ampr.org. 44.116.3.16 DOS 6.22
Port Mode Local Remote
ax4 AX25 K7IQI-1 W7ZQD-9
ax7 AX25 K7IQI-1 N7IFJ-4
ax4 AX25 K7IQI-1 KB7ZPJ-6
ax2 AX25 K7IQI-1 N7OGM-1
ax3 AX25 K7IQI-1 W0RLI-1
ax11 AX25 K7IQI-1 KB7OGD-1
netrom NETROM K7IQI-1 KA7EHK@N7IFJ-4
I<C/R>
CEDAR:K7IQI-1} SNOS 8.2 by W0RLI cedar.k7iqi.ampr.org. 44.116.3.16 DOS 6.22
Located at 650 feet altitude, on the West side of Portland's West Hills,
in Cedar Mill, Oregon, an unincorporated area of Washington County,
just West of Portland, and north of Beaverton.
1200 baud VHF/UHF:
144.980 User Freq
145.630 User Freq and Link to LINK (W7ZQD-9)
9600 baud VHF/UHF:
423.250 Mhz Link to PARET (WORLI-1) and BVRTN (N7QME-1)
439.000 Mhz Link to ALOHA (KB7OGD-1), WCEOC (WC7EOC-1), and ARESWC (N7QQU-1)
441.0125 Mhz Link to ESALEM (N7IFJ-4)
441.500 Mhz User Freq
R<C/R>
CEDAR:K7IQI-1} Routes:
Iface Neighbor Qual Dest Try Retry Perc Last BC
> ax2 ECWASH:N7OGM-1 192 12 1573 392 19.9% 20:16:04 B
> ax3 PARET:W0RLI-1 224 80 3044 328 9.7% 19:44:50 B
ax3 BVRTN:N7QME-1 224 36 2 0 0.0% 20:11:59
> ax4 LINK:W7ZQD-9 192 62 5240 2941 35.9% 20:00:48 B
> ax4 BVRCRK:KB7ZPJ-6 192 91 1039 245 19.0% 19:57:26 B
> ax7 ESALEM:N7IFJ-4 224 21 3612 322 8.1% 20:17:12
> ax11 ALOHA:KB7OGD-1 224 28 1712 264 13.3% 20:02:30 B
P<C/R>
CEDAR:K7IQI-1} Ports:
ax2 144.98 Mhz - 1200 Baud
ax3 Link to BVRTN & PARET, 423.250 Mhz, 9600 Baud
ax4 145.630 Mhz - 1200 Baud
ax5 441.500 Mhz - 9600
ax6 No Radio - 1200
ax7 Link to SRA (W7SRA-2), 441.0125 Mhz, 9600 Baud
ax8 No Radio - 1200
ax9 441.500 -- 9600 Baud
ax10 No Radio - 1200
ax11 Link to ALOHA 439.000 Mhz, 9600 Baud
SNOS routes list and ports list both look rather like JNOS and TNOS. The User reponse is quite different, however, but thats not crucial to map making. The User response DOES tell you that the software is SNOS.
CVO:W7OSU-1} Connected to TANGNT
###CONNECTED TO NODE TANGNT(KA7EHK) CHANNEL A
ENTER COMMAND: B,C,J,N, or Help ?
N L<C/R>
DALLAS (W7PLK) 01/10/03 08:28:36
HOPE* (WB7BZT) 14/11/03 20:21:26
VIA *CVO
WSALEM (N7IFJ-6) 21/11/03 22:26:48
CVO (W7OSU-1) 21/11/03 22:26:59
LYONS (KA7UPD-1) 21/11/03 22:27:35
ENTER COMMAND: B,C,J,N, or Help ?
J L<C/R>
KD7THQ-15 > N7IFJ 20/11/03 16:18:14
KD7THQ > W7OSU-1 20/11/03 16:29:09
N8GFO-7 > KC7QAE-8 20/11/03 22:53:50
KC7QAE-8 > N8GFO-7 20/11/03 22:53:50
N8GFO > LYONS 21/11/03 08:37:55
WB7BZT* > BEACON 21/11/03 08:44:09
VIA *CVO
WB7BZT-15 > N7FGF-5 21/11/03 09:59:11
KC7EGF-15 > WB7BZT-4 21/11/03 19:20:59
WSALEM > KA7EHK 21/11/03 21:13:36
KC7EGF* > BEACON 21/11/03 22:04:14
VIA LYONS,*CVO
N7FGF-5 > N7NFS-15 21/11/03 22:18:11
N7NFS-15 > N7FGF-5 21/11/03 22:18:12
N7FGF-1 > ID 21/11/03 22:23:19
W7OSU-1 > ID 21/11/03 22:26:59
KA7UPD-1 > N7IFJ-6 21/11/03 22:32:03
LYONS > KC7EGF 21/11/03 22:32:03
N7IFJ-6 > KA7UPD-1 21/11/03 22:32:14
CVO > KA7EHK 21/11/03 22:32:39
KA7EHK-15 > TANGNT 21/11/03 22:33:12
ENTER COMMAND: B,C,J,N, or Help ?
There are two important commands, "J" which stands for "Just heard", and "N", which stands for "Nodes". Each of these has a short version and a long version. Adding an "L" to either, as shown, gives you the long version. In particular, the long version gives you more information about the path by which each station was heard. This is especially important if the station used a digipeater.
The heard list shows each station heard and the station that its packet was directed to. the Node list shows both NET/Rom nodes and KaNodes. Again, if the station was heard via digipeating, the digipeater is shown.
KaNodes do not have routing services like NET/Rom nodes do. You have to figure out from one of these lists, what the next station is that you need to connect to.
Updated November 21, 2003