| |
PE1RRR > SYSOP 31.01.19 13:08l 32 Lines 1261 Bytes #999 (0) @ WW
BID : 4068_PE1RRR
Read: GUEST
Subj: BPQ Chat Node Issue + Workaround
Path: IW8PGT<IR2UBX<SR1BSZ<OK0NBR<IW0QNL<IK6ZDE<VE2PKT<N3HYM<N8RJP<PE1RRR
Sent: 190131/1059Z 4068@PE1RRR.NLD.EURO LinBPQ6.0.18
Hi all,
Due to the surge in new chat nodes appearing and linking into the BPQ global chat net, there have been
some unexpected situations where more than two link partners are being defined per node, this is manifesting
a glitch which causes QSOs to be broken, as well as a lot of excessive traffic.
I have decided to shut my own chat node down, so if you were one of the chat-node link partners (not node link, that
is different), then you will have to remove RRRCHT:PE1RRR-4 from your configs as of now.
Instead, as a workaround I have installed an 'application' line in BPQ which redirects connections on RF
to my chatnode callsign/alias, as well as the CHAT command on the node to connect to a node that was online
before mine. So I decided to use GYBCHT, my friend Steve, for mine.
Below is an example of the application line which includes the return-to-node on disconnect.
APPLICATION 2,CHAT,C 11 EI2GYB-4,PE1RRR-4 S,RRRCHT,203
Fields:
Application keyword
Application number (2)
Application command (CHAT)
Node Command Performed (C 11 EI2GYB-4), Port 11 is my AXIP Port.
My RF/NETROM Callsign for chat (PE1RRR-4)
My RF/NETROM Alias for chat (RRRCHT)
Quality (203, on my system this represents LAN/WAN).
Hope this helps!
73s
Red
www.red-heat.com
Read previous mail | Read next mail
| |
