| |
PE1RRR > BPQ 11.05.23 22:34l 99 Lines 2852 Bytes #999 (0) @ WW
BID : 13326-PE1RRR
Read: DJ6UX GUEST
Subj: BPQ to QtTermTCP Mapping
Path: DB0FHN<DB0RBS<DB0ERF<DK0WUE<GB7CIP<VE3KPG<VE3CGR<VE7ASS<PE1RRR
Sent: 230511/2017Z @:PE1RRR.#NBW.NLD.EURO #:13326 [Rijen] $:13326-PE1RRR
From: PE1RRR@PE1RRR.#NBW.NLD.EURO
To : BPQ@WW
The last couple of days I have received requests for help with
the callsign-to-application mapping in BPQ, I've edited the original
email to fit better as a bulletin.
---
Summary:
Making your terminal connectable via RF/NETROM.
Audience:
For those logging into BPQ with QtTermTCP
----
You first need to define a user and callsign mapping in the
bpq32.cfg file, this must be done under the Telnet server port.
This will define your username, the callsign+SSID that you will
get after logging in, and the password.
Format:
USER=username,password,callsign,node command (optional),SYSOP flag
(optional)
It is important that the callsign+SSID number (none, or 1-15) you
set here will match a callsign mapped to an application that tells
BPQ to use the Telnet server to connect to QtTermTCPâ€Ös “Listen”
socket.
For example:
USER=jeff,mypassword,PD1NL,,SYSOP
Next is so configure an application mapping:
APPLICATION <a number, 1-32>,command,internal
command,callsign (optional),alias (optional),quality (optional)
Example:
Before we proceed, you need to know the port number of the Telnet
Server in BPQ for this. Below the example uses “10” for the Telnet
Server port.
APPLICATION 32,LIVECHAT,ATTACH 10 127.0.0.1 8015 S,PD1NL,,0
Ok, lets break this down:
32 - The application stream number, this must be unique and between
1-32.
LIVECHAT - This is the command added to the commands list on the
node, when you type “?”. It can be whatever you want, its
customisable.
ATTACH 10 - This is the beginning of the internal command, attach is
used to connect and lock on to a port. In this case, port 10 is the
Telnet Server.
127.0.0.1 8015 - The IP address and Port where you are running
QtTermTCP. In QtTermTCP go to the Listen menu and enable the feature.
S - The S means “Stay”, so if somebody is connected to your terminal
and you disconnect them, they will be connected back to your node
instead of losing the whole connection. It is optional.
PD1NL - This is obviously the callsign, but it must match the same
callsign and SSID number (if you want to use one) as the User line
in the Telnet Server configuration.
,, - This is an optional space for a NETROM alias.
0 - This is the quality setting. If you want your terminal to be
reachable across the whole NETROM network, set this to the same
quality as your BBS application. I prefer to keep it switched off
so my node does not broadcast my terminal availability to other
nodes.
----
To test that it works, you should be able to issue "C PD1NL" and it
will connect to a new tab in QtTermTCP (make sure QtTermTCP is not
in single-terminal mode, but in tabbed or MDI mode).
Someone on RF should be able to connect to "PD1NL" and arrive at
your terminal.
73 de Red PE1RRR
--
PE1RRR <PE1RRR@PE1RRR.#NBW.NLD.EURO>
Read previous mail | Read next mail
| |
