| |
ZL1ABS > XROUTE 25.05.07 17:47l 120 Lines 5162 Bytes #999 (0) @ WW
BID : 6A0070ZL1ABS
Read: GUEST OE3GMW
Subj: Xrouter & APRS New Paradigm
Path: DB0FHN<DB0NOE<DB0GAP<DB0FSG<DB0MRW<DB0ERF<DB0FBB<DB0IUZ<DB0GOS<ON0AR<
ZL2BAU<ZL2UFW<ZL1AB
Sent: 070525/1457Z @:ZL1AB.#06.NZL.OC #:60830 [AUCKLAND] FBB7.00i $:6A0070ZL1AB
From: ZL1ABS@ZL1AB.#06.NZL.OC
To : XROUTE@WW
Hi Xrouter users,
The New APRS Paradigm requires mobile users to send their unproto Packets
with a Path of Wide1-1,Wide2-2 etc instead of using RELAY,WIDE or Similar
RELAY,WIDE2-2
Xrouter doesn't understand Wide1-1 in the present Xr1.87f version, so will
not do anything with APRS unproto packets addressed to Wide1-1
To work around this difficulty, until the next version of Xrouter updates
the APRS ability to the New Paradigm, I have added the following:
PORTALIAS2=WIDE1-1
line to each of my radio ports in my Xrouter.cfg
This will cause Xrouter to think that Wide1-1 is an Alias callsign of
itself & so digipeat the unproto Packet depending on the DIGIFLAG &
DIGIPORT settings that are equipped on that Radio port.
DIGIFLAG
Digipeater control flag. 0=no digipeat. Default=7
Add together required options from this list:
1 Digipeat UI frames
2 Digipeat non-UI frames
4 Enable RELAY generic APRS digipeating
8 Enable TRACE and TRACEn-N APRS digipeating.
16 Enable WIDE and WIDEn-N (Well sited stations
only!)
32 Enable L4 APRS tunnelling
64 Enable frames from RF to Igate
128 Enable frames from Igate to RF
Flag 1 needs to be set to allow UI Frames to be digipeated (at all) and
for the Wide1-1 work around to function. A digiflag value of 7 is a good
value for most stations to use. A value of 31 covers all the available
options in one go, but needs to be carefully used in case there are
already enough UI Digipeaters in the local area.
Of course if the internal Digipeater is not digipeating back to the same
radio port with a Digiport value of 0, it may be good to have the Digiflag
value of 31 in operation. If the UI Packet is received by port 1 and the
Digiport setting is Digiport=2, then the UI Packet is going to be sent out
of port 2 when digipeated.
Each radio port has only one internal digipeater available. The internal
digipeaters can be "daisy chained" so that for example:
incoming UI (APRS) on port 1 digipeats to port 2. Then port 2 digipeats to
port 3 etc. Xrouter is supposed to detect any accidental loops & not
digipeat around them, but be careful to check what happens if you make a
complete ring. I expect that the N value of a WideN-N path APRS UI Packet
would decrement one N each time it went through an internal Xrouter
digipeater. This cross port digipeater linking is useful to collect APRS
data on a main frequency & link it to an IGATE on another band.
Also any APRS heard on the BBS frequency can be digipeated to the APRS
frequency.
PORTALIAS2=WIDE1-1 will cause the unproto (WIDE1-1) Packet to be
digipeated as
WIDE1-1*> rather than having Alias substitution to the callsign of the
Xrouter that digipeated it. This is a small limitation in this "temporary
work around".
Xrouter also has PIPE (s) available for transferring data between ports.
There is a PIPEFLAG associated so that the type of traffic piped can be
determined.
Frame Pipes
The types of frame to be piped can be controlled using the optional
PIPEFLAG keyword, which is ignored unless piping is active.
If PIPEFLAG is not specified, the default value is 3. The value is
made up by adding together the following numbers:
1 - UI frames *not* addressed to nodecall/alias.
2 - Non-UI frames *not* addressed to nodecall/alias.
4 - UI frames addressed to nodecall/alias.
8 - Non-UI frames addressed to nodecall/alias.
16 - UI frames transmitted by the router.
32 - Non-UI frames transmitted by the router.
64 - Allow budlisted users to be piped.
128 - Netrom frames
256 - IP / ARP frames
512 - Bi-directional piping
e.g. PIPEFLAG=5 will pipe all received UI frames, but not those
which
are originated by the router itself.
"You are *STRONGLY* recommended to use the default value unless you
specifically need to see additional traffic".
That said from G8PZT, but to PIPE Wide1-1, I think Flag 4 would need to be
set. Flag 2 would not be needed in this use and Flag 1 maybe if any UI
APRS traffic heard needed to be PIPE (d). The would make a PIPEFLAG=5
value.
Some careful watch of what was sent on the destination port would be in
order to make sure that only the wanted Packet traffic was transferred to
the destination radio port.
PIPE (s) do not reduce the N value of a WIDEn-n UI APRS packet going
through them, a difference compared to the internal Digipeater.
Being able to link UI Packets from port to port caused one station to
convert to Xrouter from Flexnet. At the time there was no APRS Digipeater
module for Flexnet. Maybe there is now, but I was unable to obtain a copy
of it from the Flexnet web page. If anyone has a copy of that module I
would be interested.
73 de Michael ZL1ABS@ZL1AB.#06.nzl.oc
zl1abs@nzart.org.nz
Read previous mail | Read next mail
| |
