| |
ZL3AI > APRDIG 04.10.03 11:16l 235 Lines 9456 Bytes #999 (0) @ WW
BID : 2078-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 01, 3/11
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 031003/1344Z @:ZL3VML.#80.NZL.OC #:9638 [Chch-NZ] FBB7.00i $:2078-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: PERL APRS split stream
From: "Andrew Rich" <vk4tec@hotmail.com>
Date: Wed, 01 Oct 2003 21:42:12 +1000
X-Message-Number: 13
For those interested in learning more about APRS, here is my latest code in
PERL.
Splits the APRS stream up into relevant bits, callsign, dest, digis,
payload, email, webpage.
For those interested in learning more about APRS, here is my latest code in
PERL.
Splits the APRS stream up into relevant bits, callsign, dest, digis,
payload, email, webpage.
--------------------------------------------------------------------------------
------------------------
calls:
VK3XJB>APU250,VK3RMG-1,VK3CV-1*,TRACE3-1,qAO,VK3SB:@011126z3622.50S/14524.33E_1/
01004g008t051r000P067h97b09980/
Shepparton. Ulyssian {UIV32N}
dest : APU250
digis: VK3RMG-1,VK3CV-1*,TRACE3-1,qAO,VK3SB
payld: @011126z3622.50S/14524.33E_101/004g008t051r000P067h97b09980/
Shepparton. Ulyssian {UIV32N}
email:
webpg:
--------------------------------------------------------------------------------
------------------------
#!/usr/bin/perl
use Net::Telnet;
my $host = "aprs.net.au";
my (@data, $line);
my $t = new Net::Telnet(Timeout=> '5', port => '10153');
$t->errmode('return');
$t->Net::Telnet::open($host);
sleep 5;
print $t "user VK4TEC pass <pass> vers XASTIR \n";
while (<$t>)
{
chop;
$email="";
$webpg="";
if (m/.*\s+([a-zA-Z0-9\+_.-]+)\@([a-zA-Z0-9.-]+)\s+/)
{
$email = $1."@".$2;
}
if (m/http:\/\/([a-zA-Z0-9.-]+)\s+/)
{
$webpg = $1;
}
($callsign, $rest) = split(/>/,$_,2);
($dest, $rest) = split(/,/,$rest,2);
($digis, $payload) = split(/:/,$rest,2);
$payload =~ s/'/\\'/g,$payload;
print
"-------------------------------------------------------------------------------
-------------------------\n";
print "data : $_";
print "calls: $callsign\n";
print "dest : $dest\n";
print "digis: $digis\n";
print "payld: $payload\n";
print "email: $email\n";
print "webpg: $webpg\n";
}
----------------------------------------------------------------------
Subject: Re: Take Control of your DIGI (3)
From: "Tim Cunningham" <tim_cunningham@mindspring.com>
Date: Wed, 1 Oct 2003 06:56:50 -0500
X-Message-Number: 14
>>Callsign substitution does not eleiminate any dupes in todays network
>>where UIDIGI or Kantronics is employed.
>
>Sorry, tim, this is just plain wrong. Callsign substitution correctly and
>ALWAYS will not duplicate a packet that the same digipeatr has already
>digipeated. This is fundamental dupe elimination.
Back to the example and please do not say this is plain wrong. It is the
reality. Of course, there are may things to fix, but the fact remains there
are a whole lot of dupes in this scenario. To say dupe checking really
works meams we really closing our eyes to the reality of what is happening
here.
KE4ROC-9>BEACON,RELAY,WIDE,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,RELAY*,WIDE,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,W4GPS-7*,WIDE,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,W4GPS-7,WIDE*,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,WC4ADG*,WIDE,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,WC4ADG,WIDE*,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX Station
KE4ROC-9>BEACON,RELAY,W4SBO-7*,WIDE/1:!3440.31N/08633.13W_Remote U2000 WX
StationKE4ROC-9>BEACON,WC4ADG,W4GPS-7*,WIDE/1:!3440.31N/08633.13W_Remote U2000
WX Station
KE4ROC-9>BEACON,RELAY,W4SBO-7,W4GPS-7*/1:!3440.31N/08633.13W_Remote U2000 WX
Station
KE4ROC-9>BEACON,WC4ADG,W4SBO-7,W4GPS-7*/1:!3440.31N/08633.13W_Remote U2000 WX
Station
KE4ROC-9>BEACON,WC4ADG,W4GPS-7,WIDE*/1:!3440.31N/08633.13W_Remote U2000 WX
Station
These are the WIDE digipetesr involved since WC4ADG is a RELAY:
KE4ROC-7 using no callsign substitution digipeated 4 times.
W4GPS-7 using callsign substitution digipeated 4 times.
W4SBO-7 using callsign substitution digipeated 2 times.
This shows 7 dupes from digpeaters along not count any from the RELAY
station.
....and this is all we can see as you ususally say. Who knows what happens
way out on the DX network.
This is what I have surmized so far that is wrong from the comments:
1. DWAIT needs to be set to 0 because we do not care about packet collisions
2. WC4ADG has already halted RELAY service.
3. Persist and Slot are bad on a UI network and we do not need that integrity
4. If a digi cannot control DWAIT, then set Persist=255 and Slot=1
5. We are obsoleting any system that does not perform callsign substitution
6. You are advocating RELAY,WIDE and no more for mobile operation.
7. The sending station is fixed and should never be using RELAY in the path
since it can hit the WIDE direct anyway.
8. The path of the sending station is one hop to long.
Number 5 relies on the digiowner to fix it. That is not happening in the
short term so we have to deal with the reality.
To use DWAIT=0 seems archaic, but that will be implemeneted in a UI network
regardless of what we think is logical in losing data on a network. We do
not want that kind of reliability, we want real time communications. This
is what I have heard is important even if it causes a loss of data.
Tim - N8DEU
----------------------------------------------------------------------
Subject: RE: ***New*** TRACEn-N (LANn-N) Paradigm
From: "Cap Pennell" <cap@cruzio.com>
Date: Wed, 1 Oct 2003 05:09:51 -0700
X-Message-Number: 15
>From: Bob Bruninga
>To: TAPR APRS Special Interest Group
>Sent: Tuesday, September 30, 2003 15:10 PM
<snip>
>Have you seen the MAP by James Jefferson on my FIX-144.39 web page? It
>shows that a 1 or 2 hop path will get you to an IGAte almost ALL the time
>in California. The path of RELAY,WIDE or WIDE,WIDE is a 2 hop path and
>should work for anyone anywhere...
>
>http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
That CAlifornia map's a bit dated already. We're ready for an updated
version <grin>, and thanks, James KB0THN, for all your www.aprsworld.net
work.
>But guess what? In a lot of california, local hacks have disabled RELAY
>and WIDE. THus the only thing that works is WIDE2-2. BUT users think,
>duh, if 2-2 is good, then 3-3 must be better! And since 5-5 should get
>me to all of california, then Ill just use that instead.
Things are not _that_ bad in California, APRS-wise anyway. Yes, WIDE2-2 is
usually a good enough path here, even for most mobiles and WX stations, and
that's pretty much true across the Western US (you'll either hit a high digi
or you won't hit anything), but RELAY can help some mobiles in the fringes,
and there are plenty of 'em around our mountains. Only a few digis
overlooking LA Basin have disabled RELAY and WIDE. But that's okay, there
are other stations making their use fairly effective even there. North of
the Tehachapis, almost all the digis are Kantronics _full_ WIDEn-N, and
there are plenty of 'em. Yes, there are too many in some spots, but every
populated valley wants its own WIDEn-N to sample the high altitude digi
traffic passing by.
Considering how many stations we have on 2 Meter APRS, it's amazing how well
144.39 _does_ work for all these stations, even as is.
73, Cap KE6AFE
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: Re: The bottom line, simply [was:***New*** TRACEn-N...]
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 10:16:57 -0400 (EDT)
X-Message-Number: 19
On Tue, 30 Sep 2003, Ev Tupis (W2EV) wrote:
>===== Tier 1 ----- Everyone agrees to use RELAY,TRACE2-2. No figuring
>if you're a car, a house a digi, etc. This alone will reduce traffic
>overall...hands down.
Wow, BAD idea. FIVE BIG problems with this:
1) This has the problem that Tim is fixated on, that is, when
it hits multiple RELAYS, then some additional dupes result.
2) MOST fixed stations hit multiple digis compounding this effect
3) It is not network self-limiting. There is nothing that prevents the
user from using RELAY,TRACE4-4, or 7-7. And the DAMAGE is horrendous
4) Local SYSOPS have no control over limiting the damage
5) ONly mobiles need to start with RELAY
My proposal solves all these problems:
1) FIXED stations use simply LAN3-3 in their local LAN. One copy per digi
2) It is network self-limiting. It only goes to X digis in the named
"LAN"n-N set of digis
3) The limit is imposed by the network design and the sysops, not
vulnerable to the users choice of N.
4) It is fully tracable, the average number of digis is less than 2!
5) ONLY Mobiles use RELAY,WIDE2-2 because they typically have fewer
dupes because their lower fluttering signals hit fewer digis on the
first hop
>APRS "Official Observers" remind those that choose to not play nice
>about their obligation to be good network neighbors. After a couple of
>nicely worded communications I'd bet that a majority of folks will
>comply willingly. The "big club" would be that those left over could
>eventually be SUPLISTed at the digipeater side. This will keep traffic
>managable for the forseeable future.
This would create animosity. My approach fixes flooding by nework design
while still remaining UNIVERSAL. The only condemned path in the future
would be W,W,W,W,W,W,W where the number of GENERIC WIDES is 3 or more...
de WB4APR, Bob
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
