| |
ZL3AI > APRDIG 02.10.03 10:10l 101 Lines 3419 Bytes #999 (0) @ WW
BID : 2056-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 29, 12/12
Path: DB0FHN<DB0RGB<DB0MRW<DB0SON<DB0ERF<DB0FBB<DB0BI<DB0NOS<DB0EA<DB0RES<
ON0AR<IW8PGT<SP7MGD<ZL2TZE<VK3KAY<ZL2BAU<ZL3VML
Sent: 031001/1419Z @:ZL3VML.#80.NZL.OC #:9456 [Chch-NZ] FBB7.00i $:2056-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Take Control of your DIGI part 4
From: "Dick Stanich" <dick@kb7zva.com>
Date: Mon, 29 Sep 2003 22:1:4
X-Message-Number: 65
>I think DIGI's should only run ONE (1) of the three common 'names' (being
>RELAY or WIDE or TRACE).
>In other words, in your local network, if you are going to be a WIDE, then
>be a WIDE and do not be a RELAY. If you are a RELAY, then you are not a
>WIDE, so don't be one. Define them. Use them to take advantage of
>coverage!
>
>Now with that thinking, you think that might reduce the copies of packet
>flying around if a guy was set to RELAY,WIDE,TRACE? Comments?
>
>Jim, WA6OFT
I'm working on another 'new' proposal. If we can get digis to understand
5-5EDIW could they suck back eveything?
Seriously, when is WIDE5-5 Day <g>
Dick
APRSWest
----------------------------------------------------------------------
Subject: Re: Take Control of your DIGI (3)
From: "Tim Cunningham" <tim_cunningham@mindspring.com>
Date: Mon, 29 Sep 2003 22:07:31 -0500
X-Message-Number: 66
>The problem is that not even the sysops are marching to the same tune,
>because some of them think that the ideal network should be able to see
>500 uers from the surrouding 500 miles. This is killing APRS...
I would say in most cases it is because they do not understand or it
has not been communicated effectively.
>>My proposal would be the following:
>>
>>1. Eliminate callsign substitution immediately. It causes more
>> duplication than any good until digi firmware and FindU can
>> recognize the duplication.
>
>Totally a wrong approach. Callsign substituion ELIMINATES dupes
>completely an djust as effectively as WIDEn-N filtering given that we
>want first hop identification...
Callsign substitution does not eleiminate any dupes in todays network where
UIDIGI or Kantronics is employed. This is the reality and the reason for the
conclusion based on how the network is working today, not how it should
or will work in the future. With your plan, we must tolerate dupes now.
>>2. Digi owners need to implement NOID now or turn off WIDEn-N
>> support. We can identify the ID digi's very easily and contact
>> them to make the necessary change.
>
>Agree.
>
>>3. Educate users and digi owners at club meetings, through club
>> newsletters, through QST, hamfests, etc.
>
>To WHAT? I say to these simple rules:
>
> Mobiles RELAY,WIDE
> Homes WIDE,WIDE
> All home stations disable RELAY Alias unless their QTH is ideal
> All old MYALIAS TNC's tht do not do callsign substitution should
> be upgraded.
> Using WIDE,WIDEn-N will continue to work and may be used, but its
> long distance propogation will only go where the network thinks
> it CAN go without damage
> Find out what the LANn-N name is for your group or area and use it.
For a UIDIGI node today RELAY,WIDEn-N will create fewer dupes
than RELAY,WIDE or RELAY,WIDE,WIDE.
Keep in mind that dupe checking is broken on UIDIGI and Kantronics
when you use the tradional RELAY and WIDE designators.
>>4. Educate weather stations and fixed users to remove RELAY from
>> their path if they can hit a WIDE directly.
>
>Yes. Furhter, decide where the weather data needs to go, and set up
>a SKY path to match. Thus, all the skywarn data all goes wehre it
>needs to go, but does not add unnecessary QRM...
Good idea.
Thanks again,
Tim - N8DEU
---
END OF DIGEST
Read previous mail | Read next mail
| |
