Differences

This shows you the differences between two versions of the page.

--- packet:bpqwhitelistrouteapproach [2023/07/27 12:28] – created m0ukf
+++ packet:bpqwhitelistrouteapproach [2023/07/27 14:06] (current) – m0ukf
@@ Line 11: / Line 11: @@
 To counter this node owners may want to consider curating which nodes are available and the paths they will follow
-This will provide a very smooth experience for local users, and more advance users who want to "surf the network" may still do so using a combination of MHEAD and CONNECT <PORT> command
+This will provide a very smooth experience for local users, and more advance users who want to "surf the network" may still do so using a combination of MHEARD and CONNECT <PORT> command
 ==== Ignoring Node Broadcasts ====
-The first step is to stop your node from paying attention to node broadcasts. This is done at a part level. For example. within MB7NMK's port definition for the NinoTNC interface on 144.950 i have added
+The first step is to stop your node from paying attention to node broadcasts. This is done at a PORT level within BPQ32.cfg. For example. within MB7NMK's port definition for the NinoTNC interface on 144.950 i have added
@@ Line 40: / Line 40: @@
 ==== Adding Specific Nodes  ====
+First - Stop BPQ from running [it automatically writes to various configs on close and will undo all your work]
 Find and open BPQNODES.dat
-When you start your node, it loads details of which nodes to use, and what routes to follow from this file. If you prune this down, your node will only display these as options.
+When you start your node, it loads details of which nodes it is aware of from this file. If you prune this down, your node will only display these as options.
 If you need to add new nodes, you can edit this and restart bpq