| |
ZL3AI > APRDIG 23.01.07 00:20l 255 Lines 8970 Bytes #999 (0) @ WW
BID : 9583-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #20, 2/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0ROF<DB0ACH<DB0ACC<DB0PKE<DB0RES<F5GOV<F4BWT<
TU5EX<IW2OAZ<ZL2BAU
Sent: 070120/0306Z @:ZL2BAU.#79.NZL.OC #:28055 [Waimate] $:9583-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 4
Date: Wed, 17 Jan 2007 17:38:15 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] New Local Info Initiative
>>During my 1800 mile round trip last weekend, I discovered that
>>most digipeaters have not implemented the recommendations of the
>>New-N Paradigm to include the local Voice repeater info in the
>>beacon text of their local digipeaters.
>
>I guess I missed that part of the discussion while reprogramming my
>digis last year.
Yes, there was so much else involved in the New-N Paradigm, that this was
only a minor subset and the focus at the time was to get the digi's set for
New-N Paradigm first, and get all those long haul paths cut back to reduce
QRM from out of area. But using the LTP paths for the digipeater's own
packets to implement proportional pathing, freed up the Btext for this
voice repeater object system.
Though, I have not fully digested how one would do this in a non KPC-3+
TNC... I'd like to see someone suggest how best to do it on a UIDIGI ROM?
>I saw you traveling west bound on I-40, east of Nashville last week.
>I tried to catch you on Voice Alert, 2m Call and 70cm Call but was
>not able to reach you.
Yes, I did get a few V-A calls, and tried to keep my voice repeater channel
programmed into my mobile's comment field, but I may have missed it a few
times. But actually, in Tennesse, with those mountains, it is amazing that
I could go from Virginia, through Eastern Tennessee and Middle Tennessee
and only have to dial in 4 voice repeaters in the 300 miles to carry me
through to Alabama.
And with the mountains of Virginia along I-81, only a few voice repeaters
can cover the over 400 miles in Virginig along that corridore.
Bob, WB4APR
------------------------------
Message: 5
Date: Wed, 17 Jan 2007 20:42:32 -0500
From: Joe Della Barba <joe_at_dellabarba.com>
Subject: [aprssig] 315 is dead :(
My Magellan 315, which has worked perfectly until tonight, refuses to
acquire any satellites.
Is there some GPS jamming going on here in the Annapolis area or did the
thing just die on me?
73
Joe N3HGB
------------------------------
Message: 6
Date: Wed, 17 Jan 2007 19:47:22 -0600
From: Jim Duncan <jdbandman_at_earthlink.net>
Subject: Re: [aprssig] 315 is dead :(
The "Dems" probably turned it off to keep the Bush Administration from
spying on you again, Joe...
Jim, KU0G
------------------------------
Message: 7
Date: Thu, 18 Jan 2007 06:04:59 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: [aprssig] Periodic Disconnects from APRS-IS
Are you having an issue where you get disconnected from an APRS-IS server
periodically (sometimes as often as every minute)? Are you connecting to a
full feed (port 23, 10151, 10152 on the core)? Time to update your server
list and start connecting to a filtered port (14580 - user defined, others
may exist that are predefined, visit the web status page of the server you
are connecting to for more information on available ports
http://aprsserver:14501).
I just did a scan of the core server status pages and found over 10 clients
with 5 to 15 seconds of packets backed up scheduled to go to the client.
This is caused by the client not being able to handle the packet flow from
the server. At 15 seconds of queued transmissions, your client will be
disconnected to prevent loops. Most of the time, this inability to handle
the packet flow from the server is caused by the client software not being
able to keep up.
However, this could also be caused by a bottleneck enroute to or from your
client (remember that your client is generating an ack for every packet if
it has properly shut off the Nagel algorithm). It may seem like you have
plenty of bandwidth, but the full feed _averages_ 25-30 packets per second
which is significant for residential broadband and very significant for
dial-up. It is also very significant for most mapping clients to keep up
with processing each station report.
If you are accessing a full feed from an APRS-IS server and having problems
staying connected, re-evaluate your need to connect to a full feed. Most
people have found that connecting to a filtered feed makes their PC and
client much more responsive yet you still get full messaging capabilities
even if your client is an IGate. If you have a question about what kind of
filters are available, check out
http://www.aprs-is.net/javaprssrvr/javaprsfilter.htm
This is an informational post and in no way is meant to impugn anyone's
operation or configuration.
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Message: 8
Date: Thu, 18 Jan 2007 05:15:41 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: Re: [aprssig] Periodic Disconnects from APRS-IS
At 05:04 AM 1/18/2007, AE5PL Lists wrote:
>Are you connecting to a full feed (port 23, 10151, 10152 on the
>core)? Time to
>update your server list and start connecting to a filtered port (14580 -
>user defined, others may exist that are predefined, visit the web status
>page of the server you are connecting to for more information on
>available ports http://aprsserver:14501).
What's the current link to download the latest list?
ahubswe.net/APRServe.txt isn't doing it for me any more.
Thanks,
Earl
------------------------------
Message: 9
Date: Thu, 18 Jan 2007 06:28:28 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Periodic Disconnects from APRS-IS
Every software uses its own list format. I am assuming you mean for
UI-View. Someone in the UI-View support group will have to tell you on
that one. However, you can make your own list (highly recommended) and
there are many pages that have server lists such as
http://www.aprs-is.net/aprsservers.htm You can also use port 14580 on all
of the core servers (aprs.net servers).
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Message: 10
Date: Thu, 18 Jan 2007 22:33:49 +1000
From: "Andrew Rich" <vk4tec_at_tech-software.net>
Subject: RE: [aprssig] Periodic Disconnects from APRS-IS
What is wrong with roatate.aprs.net 14580
You get dynamic assignment of a server, and you just get what you ask for in
the stream.
That to me seems the best solution.
Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_tech-software.net <mailto:vk4tec_at_tech-software.net>
web: http://www.tech-software.net
Brisbane AUSTRALIA
------------------------------
Message: 11
Date: Thu, 18 Jan 2007 06:45:49 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Periodic Disconnects from APRS-IS
rotate.aprs.net is good if your client doesn't support automatic rotation.
If, however, your client does support automatic rotation, I recommend that
you specify each of the servers individually. Round-robin DNS is not as
dynamic as what would appear because of operating system inconsistencies
(caching algorithms) and the fact that a round-robin DNS gives out the next
IP on its list on each request.
To demonstrate this last issue, let's assume three IPs for rotate.aprs.net.
If your PC asks for an IP address for rotate.aprs.net, you get whichever
one is up next in the list. Now, if your PC asks again at a multiple of 3
total requests to the DNS server, you get the same IP address.
Pseudo-random but a 33% chance you will get the same IP address again.
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Message: 12
Date: Thu, 18 Jan 2007 14:49:36 -0000
From: "Dave Baxter" <dave_at_emv.co.uk>
Subject: RE: [aprssig] New Local Info Initiative
I think you hit the nail on the head with....
"...to tell the passing traveler exactly what one-and-only-one local
repeater is best for the visiting traveler..."
I suspect local politics will come into play, and there will never be a
decision as to "which is best" etc.
Cynicaly...
Dave G0WBX.
------------------------------
Message: 13
Date: Thu, 18 Jan 2007 08:48:30 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Periodic Disconnects from APRS-IS
Hi Earl,
You bring up a good point which I overlooked in my original post to you.
That point is that the default server lists which accompany most client
software is either out-dated or designed for simple universal installation.
Because of this, they tend to be long and don't take into account filtered
ports which are available on most servers today. That is why I say that
"it is highly recommended" to make your own list with filters defined when
configuring a client to connect to the APRS-IS.
Thanks for that light bulb :-)
73,
Pete Loveall AE5PL
pete at ae5pl.net
>-----Original Message-----
>From: Earl Needham
>Posted At: Thursday, January 18, 2007 6:20 AM
>Subject: Re: [aprssig] Periodic Disconnects from APRS-IS
>
>What's the current link to download the latest
>list? ahubswe.net/APRServe.txt isn't doing it for me any more.
------------------------------
Read previous mail | Read next mail
| |
