| |
WA4ZKO > PACKET 11.10.11 20:14l 43 Lines 1717 Bytes #999 (0) @ USA
BID : 8102_WA4ZKO
Read: GUEST
Subj: Attention Winlink RMS gateway sysops
Path: IZ3LSV<IK6IHL<IK6ZDE<VE2PKT<N9PMO<ZL2BAU<N4JOA<N4ZKF<N9LYA<WA4ZKO
Sent: 111011/1737Z 8102@WA4ZKO.#NKY.KY.USA.NOAM BPQ1.0.4
If you have your gateway "type" set as "EMCOMM" then you need to be
aware of some recent changes the Winlink Development Team (WDT) made
in the latest versions of RMS Express. BPQ32 based gateway operators
do not need to read any further as their gateway should be unaffected
by any of this.
As of RMS Express version v1.1.2.0 and newer the typical user will
NOT see "EMCOMM" gateways in the updated channel listings unless they
have taken some additional steps. The channel lists in the newest
versions of RMS Express will normally only show "PUBLIC" RMS gateways.
I suspect that many well intentioned VHF/UHF RMS Packet sysops chose
"EMCOMM" instead of "public" simply because the gateway is at/run by
an EMCOMM oriented site/group yet it is available 24x7 and open to
"public" use. Apparently this has not mattered much...until now ;-)
I'm sure there are cases (especially on HF) where the ability to hide
your gateway from most users is a good thing. On VHF/UHF something
tells me that many of sysops listing their gateways as "EMCOMM"
probably don't want to be hidden from their users ;-)
You can check how your RMS gateway is listed via one of these links:
http://www.winlink.org/dotnet/status/PacketStatus.aspx
or by clicking on the map "pins" of this page:
http://www.winlink.org/RMSPacketPositions
If your RMS gateway is not showing up on the list or map (many are not)
then you are probably running an outdated version of the RMS software.
73
Jeff
WA4ZKO
"Packet Radio never died, it just evolved."
Packet: WA4ZKO@WA4ZKO.#NKY.KY.USA.NOAM
http://groups.yahoo.com/group/robustpacket/ HF Robust Packet Group
http://groups.yahoo.com/group/hspacket/ High Speed Packet Group
Read previous mail | Read next mail
| |
