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.
RIGCONTROL no longer confined to PORT definitions – New RADIO definition.
As of 188.8.131.52* (*not quite exactly sure which)
The code is backward compatible, so you don’t need to change existing configuration. The new method allows you to define a rigcontol instance that isn’t associated with a port that allows rigcontrol – eg a KISS port that needs PTT via Serial or Hamlib.
Format is the same as with the old config, with RIGCONTROL replaced by RADIO n, where n is the interlock group, eg
RADIO 5 COM2 19200 PTTONLY HAMLIB=4534
COM40 19200 ICOM IC7100 88
FLRIG Support & HAMLib control emulator: Sharing BPQ Rig-controlled radios with WSJT-X
; FLRig is connected and configured to talk to my IC756
; BPQ is configured to talk to FLRig’s API on port 12345.
; WSJT-X is configured to talk to HamLib on port 4599
; BPQ is listens on 4599 as a Hamlib-emulator
; Issuing “radio 4 scanstop” will allow WSJT-X to take over control of the radio frequency.
FLRIG 127.0.0.1:12345 HAMLIB=4599
Per-port CTEXT (Connect Text)
As of 184.108.40.206:
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 220.127.116.11
Reload the AXIP/AXUDP configuration while the node is running, especially useful on linbpq where this is not an obvious option available. Note: If you, like myself have a huge number of AXIP wormholes, this command could result in stuck connections that eventually lose link and permanently die. For this situation, I prefer to do an actual node restart.
PASSWORD <hit enter> EXTRESTART <port number> 1
Reloading Telnet Port Users
As of 18.104.22.168
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 22.214.171.124
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