Calculating Net/Rom route quality - Revision history

Opadmin: /* Node A to Node C via Node B */

2011-12-17T11:45:54Z

Node A to Node C via Node B

← Older revision		Revision as of 07:45, 17 December 2011
Line 74:		Line 74:
	Given the route qualities of 200 across the board, this would then be		Given the route qualities of 200 across the board, this would then be

	200/256 * 200/256 * 256 = 156 or a route quality of ~~122~~ for Node C from Node A.		200/256 * 200/256 * 256 = 156 or a route quality of 156 for Node C from Node A.


	== Node A to Node D via Node B and Node C ==		== Node A to Node D via Node B and Node C ==

Opadmin at 20:09, 16 April 2010

2010-04-16T20:09:56Z

← Older revision		Revision as of 16:09, 16 April 2010
Line 23:		Line 23:
	'''r'''<br>		'''r'''<br>
	'''NODEA:KB8UVN-1} Routes:'''<br>		'''NODEA:KB8UVN-1} Routes:'''<br>
	'''> KB8UVN-2 200 1!'''<br>		'''> 1 KB8UVN-2 200 1!'''<br>

	The leading > indicates the route is presently active, followed by the neighbor callsign, quality and destination nodes.		The leading > indicates the route is presently active, followed by the port number, neighbor callsign, quality and destination nodes.

	For TheNet, this is		For TheNet, this is

Opadmin at 19:45, 16 April 2010

2010-04-16T19:45:01Z

← Older revision		Revision as of 15:45, 16 April 2010
Line 43:		Line 43:
	'''> 200 6 1 KB8UVN-2'''<br>		'''> 200 6 1 KB8UVN-2'''<br>

	The leading > indicates the route is presently active, followed by the obsolence counter, port number and neighbor callsign.		The leading > indicates the route is presently active, followed by the quality, obsolence counter, port number and neighbor callsign.

	For TheNet, this is		For TheNet, this is

Opadmin at 16:04, 16 April 2010

2010-04-16T16:04:51Z

← Older revision		Revision as of 12:04, 16 April 2010
Line 127:		Line 127:

	Another approach (BPQ only) is to set a port specific MINQUAL. In this instance, the MINQUAL dictates the minimum quality a route can be to be broadcast on a given port. To disable broadcasts of Node X from Node A, the node operator may set their MINQUAL for this port to 130. This will prohibit any neighboring node, regardless of their quality settings, from seeing the existence of Node X.		Another approach (BPQ only) is to set a port specific MINQUAL. In this instance, the MINQUAL dictates the minimum quality a route can be to be broadcast on a given port. To disable broadcasts of Node X from Node A, the node operator may set their MINQUAL for this port to 130. This will prohibit any neighboring node, regardless of their quality settings, from seeing the existence of Node X.



			== Closing ==

			These are just a few examples of how a node operator can set Net/Rom routing quality to achieve desired results. If you have questions which are not covered here, please feel free to email us and we will do our best to respond.

Opadmin at 16:03, 16 April 2010

2010-04-16T16:03:35Z

← Older revision		Revision as of 12:03, 16 April 2010
Line 98:		Line 98:
	When MINQUAL is specified on a port basis (BPQ), it sets a threshold of a given quality to broadcast to a port. This can allow a local nodes list to be large, but only share the higher quality nodes with your neighbor. This may be applicable in a situation where a multiport node may have marginal connections, such as on HF, but also have Net/Rom neighbors on VHF and UHF.		When MINQUAL is specified on a port basis (BPQ), it sets a threshold of a given quality to broadcast to a port. This can allow a local nodes list to be large, but only share the higher quality nodes with your neighbor. This may be applicable in a situation where a multiport node may have marginal connections, such as on HF, but also have Net/Rom neighbors on VHF and UHF.

	In some cases, it may be desirable to have locked routes to known systems, but not assign a high quality to new/uncoordinated systems. In this instance, you would set a port quality to something lower than the locked route quality, then set the MINQUAL to something at or below the port quality.		In some cases, it may be desirable to have locked routes to known systems, but not assign a high quality to new/uncoordinated systems. In this instance, you would set a port quality to something lower than the locked route quality, then set the MINQUAL to something at or below the port quality. In this instance, we will assume we have Nodes A and B once again with a locked route of quality 200 to one another. A new node operator shows up and establishes Node X on the same frequency. Only Node A can hear Node X. Both Node A and Node B have a default RF port quality of 128. As soon as Node X broadcasts it's presence, Node A will pick it up and automatically add it to it's routing table with a quality of 128.

			For BPQ, this is

			For BPQ, this is

			'''r'''<br>
			'''NODEA:KB8UVN-1} Routes:'''<br>
			'''> KB8UVN-2 200 1!'''<br>
			''' XX1XX-1 128 1'''<br>

			You can see the lack of ! after the destination count shows this route is not locked, so it has assumed the default port quality of 128.

			For TheNet, this is

			'''r'''<br>
			'''NODEA:KB8UVN-1} Routes:'''<br>
			'''> 0 NODEB:KB8UVN-2 200 1 !'''<br>
			''' 0 NODEX:XX1XX-1 128 1'''<br>

			Again, no trailing ! so this is not a locked route and inherits the default port quality.

			Now, the node operator of Node A and Node B does not wish to shut out any newcomers to the packet network arena, but they do wish to limit how far the broadcasts of this new/unknown node will go. To achieve this, they have set their global MINQUAL to 128. This means that Node A will add Node X to it's routing table, but when broadcast (to Node B), it's quality will be 128. Revisiting the calculations above, this will be:

			RouteQuality Node X-A/256 * RouteQuality Node A-B/256 * 256 = 100

			The route will be advertised by Node A, but because the quality is 100 for Node B, it will not show up on Node B's routing table.

			Another approach (BPQ only) is to set a port specific MINQUAL. In this instance, the MINQUAL dictates the minimum quality a route can be to be broadcast on a given port. To disable broadcasts of Node X from Node A, the node operator may set their MINQUAL for this port to 130. This will prohibit any neighboring node, regardless of their quality settings, from seeing the existence of Node X.

Opadmin at 15:54, 16 April 2010

2010-04-16T15:54:47Z

@@ Line 2: / Line 2: @@
-== Node A to Node B ==
+== Why have quality? ==
 For this example, we will assume there are two single port nodes running on the same frequency.  The alias/callsigns are:
@@ Line 50: / Line 52: @@
 The leading > indicates the route is presently active, followed by the quality,  obsolence counter, port (0 = RF, 1 = RS-232/Diode Matrix) and lastly neighbor alias:callsign.
 The route calculation here is straight forward:
-RouteQuality/256 * 256 = Node Quality
+RouteQuality Node A-B/256 * 256 = Node Quality
 Plugging in the above values, this will be:
 /256 * 256 = 200 or a route quality of 200.

Opadmin: New page: Once you start building packet nodes, you may be faced with the question of how to setup the routing quality between them. This may be your node and then a node of a neighbor, or they may...

2010-04-16T15:35:52Z

New page: Once you start building packet nodes, you may be faced with the question of how to setup the routing quality between them. This may be your node and then a node of a neighbor, or they may...

New page

Once you start building packet nodes, you may be faced with the question of how to setup the routing quality between them. This may be your node and then a node of a neighbor, or they may be both your nodes. We aim to give examples of real world routing with both TheNet (X1J4/Plus) as well as G8BPQ.

== Node A to Node B ==

For this example, we will assume there are two single port nodes running on the same frequency. The alias/callsigns are:

NODEA:KB8UVN-1
NODEB:KB8UVN-2

Both sides have locked routes of a quality 200 to one another. You can check the nodes tables on node A with the "n" command.

'''n''' 
'''NODEA:KB8UVN-1} Nodes:''' 
'''NODEB:KB8UVN-2''' 

Next, you can list the nodes routing table with the "r" command (or "nr" with most *NOS systems).

For BPQ, this is

'''r''' 
'''NODEA:KB8UVN-1} Routes:''' 
'''> KB8UVN-2 200 1!''' 

The leading > indicates the route is presently active, followed by the neighbor callsign, quality and destination nodes.

For TheNet, this is

'''r''' 
'''NODEA:KB8UVN-1} Routes:''' 
'''> 0 NODEB:KB8UVN-2 200 1 !''' 

The leading > also indicates the route is presently active, followed by the port (0 = RF, 1 = RS-232/Diode Matrix), neighbor alias:callsign, quality, destination nodes.

Lastly, you can see available routes for a target node with the "n nodename" command.

For BPQ, this is

'''n nodeb''' 
'''NODEA:KB8UVN-1} Routes to: NODEB:KB8UVN-2''' 
'''> 200 6 1 KB8UVN-2''' 

The leading > indicates the route is presently active, followed by the obsolence counter, port number and neighbor callsign.

For TheNet, this is

'''n nodeb''' 
'''NODEA:KB8UVN-1} Routes to: NODEB:KB8UVN-2''' 
'''> 200 5 0 NODEB:KB8UVN-2''' 

The leading > indicates the route is presently active, followed by the quality, obsolence counter, port (0 = RF, 1 = RS-232/Diode Matrix) and lastly neighbor alias:callsign.

The route calculation here is straight forward:

RouteQuality/256 * 256 = Node Quality

Plugging in the above values, this will be:

200/256 * 256 = 200 or a route quality of 200.