| |
ZL3AI > APRDIG 31.08.03 10:23l 134 Lines 5630 Bytes #999 (0) @ WW
BID : 1849-ZL3AI
Read: GUEST
Subj: TAPR Digest, Aug 28, 2/4
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<DB0RES<ON0AR<7M3TJZ<ZL2TZE<ZL3VML
Sent: 030830/1019Z @:ZL3VML.#80.NZL.OC #:7361 [Chch-NZ] FBB7.00i $:1849-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: [ Bob Bruninga ] Re: Pleasantville, revisited.. .
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Thu, 28 Aug 2003 10:21:21 -0400
X-Message-Number: 9
<QUOTE>
One of the, perhaps easiest, non-direct solutions might be to create an
additional set of pages on findu, related to the digis. For each digi, the
bandwidth users on that digi should be placed in rank order. Their % use
of the digi should be visible for the past hour, day, week and month. This
would allow people to see what is happening, they could be directed to the
information if needed, and those pages could enumerate the issues and
provide nice explanitory text...
</QUOTE>
This would be nice, but still requires the digi owner to go and look at
something that he/she might not do as long as they are showing up on
findU... I still like the idea of having findU not display station
information for stations that are using a huge path. Maybe set it up with a
watchdog timer so that after so many minutes of the station using the long
path it will just stop showing up. That would definately get the point
across. IMO.
----------------------------------------------------------------------
Subject: Re: Pleasantville, revisited...
From: Mark Cheavens <mcheavens@usa.net>
Date: Thu, 28 Aug 2003 09:27:45 -0500
X-Message-Number: 10
There are two other ways.
1. In EXTREME cases (or in cases of abuse) the budlist in all digi's can be
used to get the point across.
2. OR at key wides (especially on the backbone) run Digi-Ned and change
peoples paths for the area involved. I have not had to go to this in our
metro market yet, but at some point I think it will be required. When
someone drives into town with TRACE7-7, WIDE7-7 as the path it will just be
changed to come out of the Digi as Wide3-3 or more likely as Wide3-2!
I have had to use the budlist on two occasions on the Wide digi in Downtown
Houston that I run. The worst offender was a weather station that was not
in my area but insisted on running a path of trace7-7,wide7-7 and put out
weather data once a minute.
Just my $.02 worth.
Mark Cheavens
KC5EVE
----------------------------------------------------------------------
Subject: Re: [ Bob Bruninga ] Re: Pleasantville, revisited...
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 28 Aug 2003 13:19:27 -0400 (EDT)
X-Message-Number: 11
On Thu, 28 Aug 2003, Gregg G. Wonderly wrote:
>When this bandwidth factor exceeds the limits that Bob has suggested (50
>stations per digi), then action should be taken.
Gregg, good words in your post, but I would rather elaborate a bit on the
above sentence to better clarify what I meant by the 50 user area so that
it cannot be missinterpreted..
Statistically, a 1200 baud channel can just about support 50 APRS users
with some measure of reliability. Now, in some areas, all 50 could be
local to one digipeater as you suggest. In rural areas, it might take 3
or more digis to cover enough area to find 50 users. SO my post was not
that the ideal hop distance was 1 per 50 users, but that the ideal hop
distance was whatever number of digipeaters it took to cover the
geographical area around the sender such that his packet would reach his
50 nearest neighbors.
And I would not suggest that that is the not-to-exceed hop limit. I was
only suggesting that that was the "optimum" hop setting. I would not
start contacting people and suggesting that they change their hop lenght
unless they "significantly" exceeded that optimum. Say if it took 3 hops,
I would not start bothering people unless they were uising say 5 or more.
So there needs to be a margin for error..
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Subject: Re: Some Interesting Numbers
From: Richard Garcia <k4gps@bellsouth.net>
Date: 28 Aug 2003 13:20:47 -0400
X-Message-Number: 12
Quite interesting statistics.Which brings to mind something I had
mentioned a couple of years ago. If it were notike the idea of having findU not
>display station information for stations that are using a huge path.
AH, But the mechanism is in place and already is in FINDU for assessing
-anyone-anywhere's optimum path: Here is how:
Enter http://map.findu.com/wb4apr-9 <== enter anyone's call
Then select "click here to find nearby stations". The result is the 50
surrounding stations around WB4APR-9. Notice that there are 3 digis in
that list of 50 stations around me. THus, there is little reason for me
to go beyond 3 hops.
Now the astute observer will note that I may be at the center of all 3
digis and can actually hit all 50 of those users probably with just one
hop. This is perfectly true. But I only use the 3 hop as the worst case
scenario and as a means of suggesting a limit.
Now the second astute observer might note that in some areas there might
be 5 or 7 digis within the 50 user area. In Wyoming, this might be the
case, and so that many hops might be needed. But if you got that answer
in Florida, then one might consider whether maybe there might be too many
digis?
Notice that my 50 user area (What I call my ALOHA range) is about 23
miles. If I try to make my packets go much further than that, I may be
interferring with my neighbors more than they want to see...
So everything takes some thought. But the FINDU process above is a
PERFECT first order assessment of the network AS-IS around any user on the
planet that can be used to give a quick look assessment.
de WB4APR
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
