Forwarding Mail to PE1RRR BBS

To configure PE1RRR BBS in your forwarding.

First Add a new User in the Users part

Location: Mail Mgmt (HTTP interface)->Users 

Create the new user by filling out the “NEW” field with PE1RRR and clicking ADD.

Then click on the list of callsigns on the left hand side, PE1RRR should be there. Click it and you will be shown an empty New User edit form.

Using the checkboxes, set the newly created user as:

  • BBS
  • Expert
  • Allow Sending Bulls

Fill out the H-ROUTE field for PE1RRR with the correct route as follows:

PE1RRR.#NBW.NLD.EURO

Next up is Forwarding

Location: Mail Mgmt->Forwarding

Select PE1RRR from the list, it will show all fields empty.

Fill out the BBS-HA field for PE1RRR with the correct route as follows:

PE1RRR.#NBW.NLD.EURO

Under the Hierarchical Routes (Flood Bulls):

NLD
EURO
WW

Note: Many, if not all of the above entries are gathered from the Global Aliases list below, the aliases won’t readdress the messages but they will help the system direct the flood-bulls to the correct delivery queues. You may add other bull “areas” that bulls are sent @<wherever> in your local system to this list above. I prefer to use the Global Aliases to keep this section relatively easy to read, having assigned most @XXX topics to a regional suffix.

Basic – Under HR (Personals and Directed Bulls):

#NBW.NLD.EURO
WW

Important: Be super careful not to add any blank white-spaces (invisible gaps) after these lines, make sure to backspace at the end of each line if you have copied and pasted from this page to be certain.

If your bulletins aren’t forwarding, this is probably one of the things to look out for.

Additional Advanced Routing

These are the routes currently available via PE1RRR.

Under HR (Personals and Directed Bulls), updated: 2021/07/11 append:


GBR.EURO
USA.NOAM
CAN.NOAM
DGL.IRL.EURO
NLD.EURO
ITA.EURO
PRT.EURO
KOU.FIN.EURO
#NE.NSW.AUS.AUNZ
#SYD.NSW.AUS.AUNZ
BA.ARG.SOAM
SAL.URY.SOAM
PAN.NOAM
SP.BRA.SOAM

Forwarding Options:

  • Enable Forwarding Interval (Secs): 3600
  • Request Reverse Interval (Secs) : 3600
  • Send new messages without waiting for poll timer [ON]
  • FBB Blocked [ON] Max Block: 10000
  • Allow Binary  [ON]
  • Use B1 Protocol [ON]
  • Use B2 Protocol [OFF]
  • Send ctrl/Z instead of /ex in text mode forwarding [OFF]

Connection Script

Inter-node routing

Preferable if you already have an AXUDP link with RIJEN.

The call-sign RIJEN:PE1RRR-7 or MATRIX:PE1RRR-3 MUST be in your node table for this to work.

C <axudp port> PE1RRR-7
C PE1RRR-3
ELSE
C RIJEN
C MATRIX
ELSE
C PE1RRR-7
BBS

Telnet/FBB Telnet

Contact pe1rrr[][]a[][]t[][]amsat.org for a login and password.

ATTACH <TELNET PORT= number from bpq32.cfg>
C <hostname will be provided> <port> .<username> <password>

Important: The “.” period before <username> is intentional and instructs the port to behave as a transparent connection after authentication. This allows binary to flow without breaking the “normal” telnet protocol.

Advanced: It is possible to combine both strategies to form a redundant backup route for mail forwarding using the ELSE statement to extend the Inter-Node routing script above to include telnet. Should the first two attempts across the nodes fail, it will try telnet.

C <port> PE1RRR-7
C PE1RRR-3
ELSE
C RIJEN
C MATRIX
ELSE
ATTACH <TELNET PORT= number from bpq32.cfg>
C <hostname will be provided> <port> .<username> <password>

Extras

Global Aliases

AMSAT:WW
ALLUS:NOAM
ALLCANADA:CAN
ALLMI:NOAM
ALLUSA:NOAM
ARL:WW
ARRL:WW
BRANET:SOAM
CALIF:NOAM
CANADA:CAN
DL:DEU
EU:EURO
GBR:WW
ITA:ITA
JAPAN:JPN
LATNET:SOAM
LUNET:SOAM
NLDNET:NLD
NLNET:NLD
SYSOP:WW
USBBS:NOAM
USA:NOAM
VKNET:AUNZ

BPQ32 Notes

Please note that this page is still under construction.

Commands

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.

The < and > 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 6.0.21.40* (*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
RADIO 4
COM40 19200 ICOM IC7100 88
5,14.102,USB,VN
5,10.1473,USB,VN
****

Per-port CTEXT (Connect Text)

As of 6.0.21.21:

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 6.0.20.1

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 6.0.20.1

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 6.0.20.1

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>

Configuration

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>

To Other:

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 

Whitepages Notes

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 FROM, TO or 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