Please note that this page is still under construction.
Throughout this document, the command
PASSWORD is not a prompt to enter an actual password, it is a command that must be typed in order to gain sysop (administrator) access.
> characters define an action, such as pressing enter, or substitution with a user input, depending what is between them.
Per-port CTEXT (Connect Text)
As of 188.8.131.52:
CTEXT is read from files, with names of format PortnCTEXT.txt, where n is the port number. So for port 4 the filename is Port4CTEXT.txt. These are read from the same directory as bpq32.cfg. They are read when BPQ starts but can be re-read using the Node command GETPORTCTEXT so you can change the text without starting the node. Remember that on Linux names are case sensitive.
The file is sent to the user as input without any format change. Some clients, such as Winlink Express, don’t treat the normal Linux line terminator of LF as a new line, so if you are running on Linux you are best off creating the files with an editor that can write the normal Windows line terminator CR LF.
Reloading AXIP Table
As of 184.108.40.206
Reload the AXIP/AXUDP configuration while the node is running, especially useful on linbpq where this is not an obvious option available.
PASSWORD <hit enter> EXTRESTART <port number> 1
Reloading Telnet Port Users
As of 220.127.116.11
USERS: useful when adding new users to the telnet login system/BBS telnet mail forwarding.
ALL: Useful to reload the entire telnet port configuration without stopping the node.
PASSWORD <hit enter> TELRECONFIG <telnet port number> USERS Or TELRECONFIG <telnet port number> ALL
Reloading APRS configuration
As of 18.104.22.168
PASSWORD <hit enter> APRS RECONFIG
Delete All Nodes
Sometimes it’s necessary to kill an entire node table especially while experimenting and fine tuning links.
PASSWORD <hit enter> NODE DEL ALL
If you wish to remove only one node, the command can take the callsign and SSID as a parameter
PASSWORD <hit enter> NODE DEL <callsign-ssid>
BPQ Telnet Mail Forward
Using the BPQ BBS Connect Script (accessed via the HTTP interface)
Location: Mail Mgmt->Forwarding
To FBB (note the period (.) before the username is intentional):
ATTACH <axip port number> C <dns hostname or IP> <FBB port> .<username> <password>
ATTACH <axip port number> C <dns hostname or IP> <telnet port> <username> <password>
Connecting to a URONODE
URONODE apparently requires two different UDP ports- just remember to port forward whichever one becomes your incoming port on your ISP connected home router/gateway.
MAP <callsign(-ssid)> <hostname/IP> udp <outgoing port> SOURCEPORT <incoming port> B
The BBS has been configured to reject WP bulletins, but yet, WP bulletins are still arriving with status
BK (bulletin killed), but why? I asked John G8BPQ and was given a helpful insight into how the forwarding protocol of choice can affect the message filters:
The WP messages that aren’t being rejected are all arriving via B2 protocol (FC proposal). The standard FC message doesn’t include
VIA so the filters have to kill filtered messages instead of rejecting them.
Between BPQ BBS systems the FC proposal is extended. Many of those messages are rejected, but not all of them.
G8BPQ / John