| |
ZL3AI > APRDIG 16.08.03 23:57l 161 Lines 6214 Bytes #999 (0) @ WW
BID : 1782-ZL3AI
Read: GUEST
Subj: TAPR Digest, Aug 14, 1/2
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<ZL2TZE<ZL3VML
Sent: 030816/1116Z @:ZL3VML.#80.NZL.OC #:6622 [Chch-NZ] FBB7.00i $:1782-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Thursday, August 14, 2003.
1. RE: emergency comms?
2. Re: Duplicate Packets on RF/Inet Station
3. RE: emergency comms?
4. DSC operation
5. Re: Duplicate Packets on RF/Inet Station
6. Re: BMW MOA Forums - The Iron Butt Rally (11,000 miles/11 days)
7. Re: Duplicate Packets on RF/Inet Station
8. MNAPRS...
----------------------------------------------------------------------
Subject: RE: emergency comms?
From: "Herb Gerhardt" <hgerhardt@charter.net>
Date: Wed, 13 Aug 2003 21:00:35 -0700
X-Message-Number: 1
No, it is not offensive. This is the real use for APRS messaging.
In Washington State, we have conducted a test in the use of our APRS Network
for State Emergency Communications. Yes, it works and YES it should be used
for Emergency Communications. We have full blown full time APRS stations in
several of our County EOC's and also a full time station in our Washington
State EOC! We also have several counties using APRS during our local SAR
(Search and Rescue) activities.
During an emergency, please use the APRS Network for your emergency
communications and don't worry if anyone is offended by such use!
Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site: www.nwaprs.org
----------------------------------------------------------------------
Subject: Re: Duplicate Packets on RF/Inet Station
From: "Dick Stanich" <dick@kb7zva.com>
Date: Wed, 13 Aug 2003 23:26:20
X-Message-Number: 2
>There is nothing misconfigured, two one
>way connects does not result in any risk of looping. If it is occurring (and
>other than the javAPRServ counter, I see no evidence of any loop now), Gregs
>IGate is not the cause.
4 core servers times 2 connects each for a single Igate can't result in
potential looping? The loops were mostly 'detected' on the system by
SECOND. None of the lower level servers saw them. The fact is the looping
occurred. Probably has little to do with the APRServe software he is using.
There are much better programs being used by Igates and unfortunately, my
opinion is that WinAPRS is not my choice.
I'm not sure what happened and only saw the RF coming from Greg to my
location a few hundred miles away. Several months ago I asked Greg if he
would reduce his Igate path, he did. Not much has changed, I still see his
packets, at my own Igate on RF. I've gotten used to living with the issue
because I see 5 other Igates trying to send to me on RF. I don't see the
problem with Igates using Ui-View. There is more control over smart Igate
programs that use KISS mode with their TNC's. Not sure if that's a plug for
Ui-View or just my opinion :)
Phils question was more or less about... is there a way for Igates to
understand that if 2 users are communicating on the Inet, their packets not
be sent to RF. Kinda the opposite of NOGATE, RFONLY. What do you think
about that?
Dick
----------------------------------------------------------------------
Subject: RE: emergency comms?
From: "Scott Miller" <scott@home.miller.org>
Date: Wed, 13 Aug 2003 21:39:25 -0700
X-Message-Number: 3
What about for dissemination of weather data directly to fire crews? Is
there any APRS format for a weather forecast? I've only seen actual live
telemetry from sensors. Seems to me a ruggedized PDA or something similar
capable of receiving forecasts and sensor data would be valuable. Just
check out an account of the Storm King fire that killed 14 firefighters in
part because they didn't get timely weather data.
http://www.yakima-herald.com/newsfeatures/Thirtymile/thirtymile.html$happen.
html
Scott
N1VG
----------------------------------------------------------------------
Subject: DSC operation
From: WB4GQK@aol.com
Date: Tnswer, though
I understand coordination can be a difficult thing. In an area with
100+ APRS stations within 75 miles and solid coverage by WIDEn-n digis,
we can even coordinate path reductions to WIDE2-2 or equivalent.
</soapbox>
73,
Pete Loveall AE5PL
http://www.ae5pl.net
mailto:pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: BMW MOA Forums - The Iron Butt Rally (11,000 miles/11 days)
From: "Spider" <spider@rivcom.net>
Date: Thu, 14 Aug 2003 05:38:45 -0700
X-Message-Number: 6
Karen Bolin (MRF), a friend of mine, has been sending me messages on her
husbands journey in the IronButt Rally.
I have about 3 megs of pictures from her and one shows a bike with a nice
GPS setup. Can't help with the call but they are all heading for Florida at
this time!
Jim, WA6OFT
BMW, R1100RT
----------------------------------------------------------------------
Subject: Re: Duplicate Packets on RF/Inet Station
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 14 Aug 2003 09:07:27 -0400
X-Message-Number: 7
On 8/13/03 at 11:26 PM Dick Stanich <dick@kb7zva.com> sent:
>>There is nothing misconfigured, two one
>>way connects does not result in any risk of looping. If it is occurring (and
>>other than the javAPRServ counter, I see no evidence of any loop now), Gregs
>>IGate is not the cause.
>
>4 core servers times 2 connects each for a single Igate can't result in
>potential looping?
That is correct. What you are missing is these are one-way connects, and
pull data from port 1313. Remember that 1313 only had data which enters the
APRS IS at that IGate or hub. So, given that HUB connects to IGate, nothing
that travels on that connection will travel on the 1313 connection that
IGate makes to HUB. This is by definition of 1313, and has been correctly
implemented in every version of hub software ever released.
This is a much safer way than the present system, of everyone initiating
bidirectional connects at will. The old way, no matter how misconfigured
the IGate, the hub only got the data it asked for. It also left the hub in
complete control over its connection, in the event that the IGate caused
problems. The only problems ever caused by the IGate were security, looping
didn't occur in the good ol' days! It was more work though than anyone is
willing to do now...
Steve K4HG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
