OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   08.02.03 09:36l 314 Lines 11971 Bytes #999 (0) @ WW
BID : 842-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 01, 1/5
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<VE1ATT<HA3PG<7M3TJZ<ON0BEL<VK7AX<
      ZL2BAU<ZL3VML
Sent: 030204/0919Z @:ZL3VML.#80.NZL.OC #:58788 [Chch-NZ] FBB7.00i $:842-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Saturday, February 01, 2003.

1. Mac OSX / Xastir
2. Re: Unproto path ?
3. Re: Mac OSX / Xastir
4. javAPRSFilter Features Now on CORE-2
5. RE: javAPRSFilter Features Now on CORE-2
6. SV: RE: javAPRSFilter Features Now on CORE-2
7. RE: javAPRSFilter Features Now on CORE-2
8. Re: Unproto path ?
9. Re: Unproto path ?
10. Re: Unproto path ?
11. Re: SV: RE: javAPRSFilter Features Now on CORE-2
12. Re: SV: RE: javAPRSFilter Features Now on CORE-2
13. Intro to AX.25, APRS Authors, APRS and BEACONet.25 unproto [was: Unproto 
path ?]
14. Re: Unproto path ?
<LYR30523-118307-2003.01.31-21.51.53--kb2scs#optonline.net@lists.tapr.org>
15. RE: Hurricane Symbols...
16. Columbia Lost Over Texas
17. Shuttle Emergency!!
18. Shuttle Lost update
19. Re: Thanks-Re: Unproto path ?
20. Re:  Shuttle Lost update
21. RE: Input needed
22. RE: New spec - working notes
23. Re: New spec - working notes
24. Opto isolators
25. Re: Unproto path ?
26. Re: Routing question
27. Re:  Shuttle Lost update
<LYR27854-118386-2003.02.01-11.06.50--darnellb10#comcast.net@lists.tapr.org>
28. Shuttle Radar images...
29. Re:  Shuttle Lost update
30. Re: Unproto path ?
31. RE: APRS Symbols (versus Windows ICONS)..
32. FW: Shuttle search net request
33. Re: Unproto path ?
34. Re: Unproto path ?
35. tragic day
36. Shuttlle debris photo
37. Grim Reality shuttle
38. TEXAS debris reports first hand
39. Re: New spec - working notes
40. Re: New spec - working notes
41. Re: New spec - working notes

----------------------------------------------------------------------

Subject: Mac OSX / Xastir
From: "Brian  Riley (maillist)" <n1bq_list@wulfden.org>
Date: Sat, 01 Feb 2003 01:02:39 -0500
X-Message-Number: 1

A while back I asked about Mac OSX and Xastir and someone sent me a URL of
a site specifically oriented to that.  I seem to have misplaced it could
someone send me that again. Thanks.

I just got done downloading and installing X11 and am itching to get Xastir
up and running.

----------------------------------------------------------------------

Subject: Re: Unproto path ?
From: Bill Herrmann <bherrman@spro.net>
Date: Fri, 31 Jan 2003 23:07:25 -0700
X-Message-Number: 2

At 09:04 PM 1/31/03 -0600, Pat Karp wrote:
>Now the maximum of 7 entries does that mean I can use wide7-7 seven times 
>and AX.25 would attempt to carry me packet through 49 hops? or is that a 
>total of 7 hops?

Obviously, don't try this at home (or anywhere else for that matter) but 
yes 49 hops is theoretically possible. As Bob mentioned the chances of 
success are in the lottery range.

Part of the purpose of widen-n was to allow a shorter (text wise) path 
specification. At least in Kantronics documentation (and I think in 
Kenwood's too) it explicitly mentions that the -n part is acting as the 
SSID but that the digipeater has special rules for processing it.

It should be noted that once you hit a couple of wideN digipeaters with ID 
turned on the game is over anyway if you're using 7 wideN strings. (The 
digi will put it's own id in the front of the string leaving you with 8 
total...)

Bill

----------------------------------------------------------------------

Subject: Re: Mac OSX / Xastir
From: "Curt Mills, WE7U" <archer@eskimo.com>
Date: Sat, 1 Feb 2003 00:07:51 -0800 (PST)
X-Message-Number: 3

On Sat, 1 Feb 2003, Brian  Riley (maillist) wrote:

>A while back I asked about Mac OSX and Xastir and someone sent me a URL of a
>site specifically oriented to that.  I seem to have misplaced it could
>someone send me that again. Thanks.
> 
>I just got done downloading and installing X11 and am itching to get Xastir
>up and running.

http://members.chello.nl/~m.vanopzeeland/xastir.html

Use the latest Xastir development release or the CVS version.

Curt, WE7U.				archer@eskimo.com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

----------------------------------------------------------------------

Subject: javAPRSFilter Features Now on CORE-2
From: Greg Noneman <greg@clubnet.net>
Date: Fri, 31 Jan 2003 23:58:40 -0800
X-Message-Number: 4

Roger Bille (SM5NRK) announced his javAPRSFilter adjunct to AE5PL's  
javAPRSSrvr server software several weeks ago.  This filter add-on 
allows clients to obtain a feed which has been customized to their 
specific needs.  A filtered feed results in receiving only the data of 
interest, which can drastically reduce the burden on your internet 
connection (as compared to the full worldwide feed).  Eight types of 
filtering options are available.

The second.aprs.net (CORE-2) server has joined other javAPRSSrvr sites 
and now supports the javAPRSFilter adjunct.  Clients can log-on to port 
14580, and specify their filtering parameters.  A summary of the 
javAPRSFilter operation is available at 
http://www.aprs-is.net/javAPRSSrvr/javaprsfilter.htm.  The client port 
table of the second.aprs.net status page (port 14501) also has a link 
to this info site.

With the increasing popularity of APRS has come increasing bandwidth 
requirements for both servers and clients of the APRS-IS.  Selectively 
filtering, when appropriate, can dramatically improve the demands on 
both ends.  If you frequently connect to second.aprs.net and do not 
need the full worldwide feed, investigate the javAPRSFilter 
capabilities on port 14580.

73,
Greg
WB6ZSU
second.aprs.net

----------------------------------------------------------------------

Subject: RE: javAPRSFilter Features Now on CORE-2
From: "Stephen M. Parker, WR9A" <wr9a@commsec.com>
Date: Sat, 1 Feb 2003 03:28:11 -0500
X-Message-Number: 5

I've looked at all of the documentation and web pages about the
javAPRSFilter features, but I still can't figure out how to get it to
actually work! I log onto the appropriate server and the correct port
(14580), but how does one go about "sending an APRS message to the station"?
How do I know the station's call that I am connected to, and how can I send
it an APRS message through the TCP/IP window?

All I get in the terminal window is "# javAPRSSrvr 2.4b05" repeated over and
over. I can't get any kind of response.

Stephen M. Parker
WR9A

----------------------------------------------------------------------

Subject: SV: RE: javAPRSFilter Features Now on CORE-2
From: "Roger Bille" <roger.bille@telia.com>
Date: Sat, 1 Feb 2003 11:09:19 +0100
X-Message-Number: 6

Stephen,

>How do I know the station's call that I am connected to,

	Server                   Call

 	second-aprs.net          CORE-2
	ahubswe.net              AHUBSWE
	aprsca.net               APRSCA
	aprseast.net             APRSEAST
        aprswest.net             APRSWEST

>and how can I send it an APRS message through the TCP/IP window?

I don't understand what you mean with the TCP/IP window. What application
are you using ?  Just send a normal message as you would do to an other APRS
station but send it to the corresponing call of the server you are connected
to. UI-View, APRS-SA and Xastir have also special support for entering the
filter definition at logon to the server.

73 de sm5nrk/Roger

----------------------------------------------------------------------

Subject: RE: javAPRSFilter Features Now on CORE-2
From: "Stephen M. Parker, WR9A" <wr9a@commsec.com>
Date: Sat, 1 Feb 2003 05:25:09 -0500
X-Message-Number: 7

Thanks. That's what I needed. It's working beautifully now.

73
WR9A

----------------------------------------------------------------------

Subject: Re: Unproto path ?
From: Bob Bruninga <bruninga@usna.edu>
Date: Sat, 1 Feb 2003 07:04:20 -0500 (EST)
X-Message-Number: 8

Continued writings about the path WIDE7-7,TRACE6-6:

>Well from what Bob stated the answer to my question is yes!...  Now the
>maximum of 7 entries does that mean I can use wide7-7 seven times and
>AX.25 would attempt to carry me packet through 49 hops?

Lets go back and also look at the QRM generated by the original path
WIDE7-7,TRACE6-6.

Lets assume that every digi hears 3 others (at least).  So one packet
begets 3, begets 9, begets 27 or 3 to the Nth power for an N hop path.  So
in a perfect APRS network that one packet would generate 1,594,323 (over a
million) packets.  Again, not the kind of QRM we want on our local 1200
baud APRS channel.

But because of the mentality that "HIGHER IS BETTER", How many digis can
your local digi hear?  4?  5?  Lets do it again for 5 digis.  It is over a
BILLION QRM packets.  Dont do it, no one wants to have to contend with
such malicious interference.

Bob, WB4APR

----------------------------------------------------------------------

Subject: Re: Unproto path ?
From: Bob Bruninga <bruninga@usna.edu>
Date: Sat, 1 Feb 2003 07:42:05 -0500 (EST)
X-Message-Number: 9

>Lets go back and also look at the QRM generated by the original path
>WIDE7-7,TRACE6-6.
>
>Lets assume that every digi hears 3 others (at least).  So one packet
>... would generate 1,594,323 (over a million) packets....

Now FLIP that equation over.  If your digi can hear 3 other digis, then it
can hear all users on those digis using WIDE2-2.  It can then hear ALL
users on the next 9 digis using WIDE3-3.  Or 27 digis of people using 4-4,
or 81 other digis worth of folks using WIDE4-4 and so on.  But since each
local 144.39 channel can only support about 40 users reliably, you can see
the foolishness of anything beyond a few hops...

Now, given that a network SHOULD be designed to serve its local users, and
we have given everyone a tool by which to see the loading in their area,
(see ALOHA Circle: http://www.ew.usna.edu/~bruninga/aprs/fix14439.html )
thus the ability to determine for their own if their network is
overloaded, then I would support the following algorithm in any new
digipeater code:    (probably UI_DIGI or DIGI_NED already has it)...

DXQRM filter for OVERLOADED local digis:

   If WIDEX-Y packets are received by a digi and the difference between
   X and Y is greater than or equal to "N" then ignore the packet.

Let the local APRS community decide on the value of "N" for their local
community.  Probably 2 in a very busy area.

RESULT:  The local user is fully supported with ANY path he may choose.
And his local area fully sees his packet.  If he needs to send a multi-hop
packet out of the city, through the desert, to someone 500 miles away, he
can originate such a WIDE5-5 packet and it will go out.

Yet, any packet greater than WIDE2-2 originated by the hundreds and
hundreds of other people in the 5 surrounding states will never make it
into your area..  Wow, what a relief!

"But what about Gramma comming to visit from Alabama?  I want to see her
coming"...  Easy, Look at the map before the trip, determine the HIGH SITE
digis along the way, and build a unique path to get the packets where they
need to go.  (or give her a path of WIDE,WIDE2-2) and go watch on the
internet.

Remember, HIGH digis in the middle of the desert would have no need to
implement the DXQRM filter, because they do not have a QRM problem, thus
any long-haul packets in any such long-haul area are not affected...

CORROLARY.  However, I would also maintain that there is NO REASON
ANYWHERE in a crowded network area for ANY path of WIDEN-N longer than
about 2, because there is a reason that is called the UIFLOOD algorithm,
is because it FLOODS a network.  If someone in LA needs to be seen in San
Francisco, it makes no sense to FLOOD the entire So Cal area of dozens of
digipeaters when the simple path of DIGI1,DIGI2,DIGI3,DIGI4 will do the
same thing and only QRM 4 digis...

So in those areas, it might be better to just filter out EVERYTHING above
WIDEX-X and teach those people who insist on flooding the network that
that is not a good practice...

 Bob, WB4APR

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 03:34:12lGo back Go up