Oh no! Your node table is full- this usually means the
MINQUAL setting is likely too low on the port receiving broadcasts. The following is a good starting point, but may still need tweaking depending upon your wants and desires.
MINQUAL is also adjustable as sysop. First send the word ‘
password’ from the BPQ console then use
MINQUAL 143 to make a realtime adjustment. Note: this adjustment will not survive a node restart.
The node will begin to prune low quality nodes from the table that are too many hops away, pruning could take up to 30 minutes to have an effect depending on what the
NODESINTERVAL= parameter is set to on the upstream sender’s side. In the case of
PE1RRR-7, the nodes broadcast interval is 30 minutes.
MINQUAL and MINQUAL
MINQUAL should not to be confused with the same-named parameter under the
PORT definition, they do not share anything in common. The main configuration MINQUAL determines the quality cut-off limit for the retention of nodes within the node table, whereas the
MINQUAL listed under an individual PORT determines which nodes from your table are sent out (broadcast) on that port.
Sometimes it’s not ideal to broadcast hundreds of nodes over RF, so often a sysop will limit this using port MINQUAL to only send the nodes that are local to the system.
192 - AXIP Link or RF Link 203 - LAN Link (Local) 254 - Applications on the node 255 - The Node Itself
RIJEN/PE1RRR-7 is mapped to many many others in order to stress test BPQ AX25 stack,
RIJEN presents at least 2-6 nodes per link and there are about 95 links in total.
Protip: BPQ supports a maximum of 120 AXIP/AXUDP mapped links.
Nodes linked to PE1RRR-7 will receive between ~250-300 legit nodes that are only 1 hop away, so a linked node’s table size (
MAXNODES=) needs to be sufficiently large enough otherwise nodes will unexpectedly drop off at seemingly random intervals.
The table of this node should not reach anywhere near 1000, but the table needs some breathing room.
The Other MINQUAL – Port:
QUALITY=192 MINQUAL=100 ; only send nodes out on this port that are above quality 100.
To The Max
Here are the absolute maximum possible parameters for the BPQ network stack:
MAXCIRCUITS=160; If all 64 application streams are allocated = 128. + 32 (16 Node hopper people) MAXLINKS=192; MAXCIRCUITS + 32 more for individual AX25 Up and down linkers MAXNODES=1000; Max nodes in nodes table MAXROUTES=144; Number of AXIP MAP neighbours (max 128) + Potential RF routes MINQUAL=146; calibrated for 192: 146 = 1 hops. 144 = 2 hop. Minimum quality to add to nodes table (finely tuned!)
BPQ is capable of handling a maximum of 64 application streams which are constructed from two NETROM circuits. One circuit for the inbound link and one for outbound link.
Each connection into the node utilizes a stream. The maximum possible number of NETROM circuits in a node is determined by how these applications streams are divided up between programs such as BPQ Mail, BPQ Chat, the Node etc.
The following is a breakdown of how resources are allocated for
PE1RRR-7/RIJEN which is primarily an AX/IP node maximized for such usage:
Maximum possible streams = 64
Converted into Complete NETROM Circuits: 64 x 2 = 128
Max. Links Possible = Max. Complete NETROM Circuits + 16 Complete Circuits for Arbitrary (non-NETROM) AX25 Connections:
MAXCIRCUITS = (64 x 2) + (16 x 2) = 160
MAXLINKS = MAXCIRCUITS + (16 x 2) = 192
MAXROUTES = MAX-AXIP-MAPS (Max. 120) + 24 (Max. Remaining Allocation) = 144
For a node with a large number of RF ports doing NETROM activity, these parameters would need to be adjusted slightly to cater for less AXIP mappings in exchange for a larger number of NETROM circuits.
MAXROUTES has an upper hard limit of 144 due to how memory is allocated in BPQ32.
For further troubleshooting: Try the Groups
If you find the articles, or content in general posted here useful, enjoyable or maybe even something else, please consider making a small contribution towards my hosting fund so that I may continue to provide my services for free to as many people as possible.