| |
ZL1ABS > XROUTE 19.11.07 11:47l 79 Lines 3103 Bytes #999 (0) @ WW
BID : 0C1260ZL1ABS
Read: OE3GMW GUEST
Subj: Xrouter PIPE & Callsign SSID
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<I4UKI<IR1UAW<IK1YPH<IW2OHX<OE6XPE<DB0RES<
ON0AR<ZL2BAU<ZL1AB
Sent: 071119/1027Z @:ZL1AB.#06.NZL.OC #:4932 [AUCKLAND] FBB7.00i $:0C1260ZL1ABS
From: ZL1ABS@ZL1AB.#06.NZL.OC
To : XROUTE@WW
Xrouter PIPE & Callsign SSID delimiters
After not finding the Information in the Xrouter.txt file (& lack of
replies to questions on the Xrouter user email list) concerning the use of
PORT PIPEs with Callsigns having SSIDs to restrict traffic down the PIPE,
some experimental work was done tonight (19/11/2007) on the Xrouter.cfg
file.
The object is to cut down the number of RX buffer overflow errors (seen in
the Xrouter STATS *) & REJ packets when the BBS is too slow to respond.
I just tried a modification of the port section of Xrouter.cfg
The new line works OK.
OLD= PIPE=5 ZL1AB
NEW= PIPE=5 ZL1AB-0,ZL1AB-5
Neil ZL1ANM came up on the 2m port (144.600 MHz) & did test connections &
BBS downloads to the following callsigns:
ZL1AB
ZL1AB-0
ZL1AB-5
All were successful in getting through to the F6FBB type ZL1AB BBS & being
able to do a list & download a message.
So Xrouter is PIPE-ing those SSID through to the Ethernet link OK.
It was able to pass those callsigns before the change was made.
Various user & other BBS stations use one or all of those SSID or the Node
Alias NSHORE to make connections.
Hopefully it isn't PIPE-ing any other traffic addressed to ZL1AB-1,
ZL1AB-2, ZL1AB-8 etc.
They are SSIDs in use by Xrouter or have NODES broadcasts etc being
sent/polled by ZL2AQY & other stations on the channel.
The PIPE (per port) is required so each of the three RF ports has access
to the Ethernet port that goes to the F6FBB type BBS separate PC. As far
as most BBS users are concerned, they hardly know the Xrouter is there as
the PIPE & Alias system passes them transparently through Xrouter to the
BBS.
It isn't required for them to do a connect to Xrouter first before the
BBS.
Also another BBS (ZL2BAU) came up & forwarded a message through the
NSHORE-1 Alias. It was good to see things still working as before.
So I'm hopeful I haven't "broken" anything & will have to see how the
error
stats & buffer overflows go.
The Xrouter PC is HP vectra 486/33N. Maybe it is a miserable 33 MHz?
I forgot to look what it's BIOS says this time.
The Tiny2 TNC manual says the terminal baud rate is set with jumpers
behind
the front panel. I think I will leave off changing them tonight & see how
things go. I've been told that using a terminal baud rate of 19.2 kb to
the three TNC involved "might be too ambitious" & that 9600 bauds is
better able to be handled by the UARTs on the serial COM cards (3 of them)
in the 486 PC.
Xrouter has been in use at ZL1AB for about five years, but there is always
room to see if it can be improved for better results.
Recently one 70cm port radio was improved by 10dB on RX with a front end
tune up on an RF generator. The other 70cm 9k6 radio is now due a similar
sensitivity check up. The 9k6 port works far better with a somewhat longer
TXDELAY setting than it used to have. APRS traffic is handled on 70cm &
"bridges" between the BBS network & the separate APRS network. Any APRS
beacons on the regular Packet network end up on the APRS network & get to
the internet.
73 de Michael ZL1ABS
Read previous mail | Read next mail
| |
