Menu
▾
▴
aprsd-users
|
From: KC7ZRU - T. <kc...@ar...> - 2001-11-14 18:47:47
|
Hi all,
Got an email from the guys in South Africa that're supporting a PCSat/UO-14/ISS/etc I-gate in Antarctica. They're connecting to a 'low traffic' server I run at the hose, which is in turn connected to my 'main' server here at the office. The house machine (CSP-2) normally runs 2.1.4.vk3sb.2, the main server (CSP) was running 2.2.0 - I've since moved it back to 2.1.4.vk3sb.2 as well. (kludge).
Here's why:
Packets are being dropped - two examples are:
ZR1CBC-3>DDF565,APRSAT,ZR1CBC,I*:'.O|l [/>/A=000755
KE6JAB-1>APRS,UOSAT5*,APRSAT,ZS7ANT,I*:!7131.33S/00847.44E_Stanford U Wx, Blue One, Antarctica, 3680ft
I'm not enough of an 'eye' to twig onto why they're being dropped. Getting their info from Antarctica, to South Africa to Wyoming is cool - but I gotta be able to pass it onto the APRS IS core as well.
Is it UI-VIEW's 'igate' insertion tag? "I*" (also used by xastir now).
Any ideas? I'd rather be using 220 for both servers - but I have to know what to fix. What's wrong with the packets?
73
--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
| CARC Repeater 146.940 DN62 |
| http://groups.yahoo.com/group/RM-APRS |
| "The Dungeon" at http://go.to/KC7ZRU |
| LINUX user: 227845 http://counter.li.org/ |
+++++++++++++++++++++++++++++++++++++++++++++++
"I fear all we have done is to awaken a sleeping giant and fill him with a terrible resolve."
- Admiral Yamamoto
|
|
From: Chuck B. <cb...@vi...> - 2001-11-14 18:59:19
|
On Wednesday 14 November 2001 01:47 pm, KC7ZRU - Tate wrote: <<snip, snip>> .: Packets are being dropped - two examples are: .: ZR1CBC-3>DDF565,APRSAT,ZR1CBC,I*:'.O|l [/>/A=000755 This one doesn't look like a valid APRS data type .: KE6JAB-1>APRS,UOSAT5*,APRSAT,ZS7ANT,I*:!7131.33S/00847.44E_Stanford U Wx, Blue One, Antarctica, 3680ft .: This one looks like it didn't make it through the packet length check. Which BTW has been removed from 2.2.1 (data < 252) Chuck |
|
From: KC7ZRU - T. <kc...@ar...> - 2001-11-14 19:16:14
|
Guess I should add in:
The ZR1CBC string is generated by a D7 gated by UI-VIEW.
The KE6JAB is generated by UI-VIEW (I believe)
I'll give 2.2.1 a shot here.
Any ideas on what's going wrong with the CBC packet? Could it be UI-VIEW not handling the MIC-E conversion/pass through?
Thanks for the input!
Chuck Byam wrote:
>
> On Wednesday 14 November 2001 01:47 pm, KC7ZRU - Tate wrote:
> <<snip, snip>>
> .: Packets are being dropped - two examples are:
> .: ZR1CBC-3>DDF565,APRSAT,ZR1CBC,I*:'.O|l [/>/A=000755
>
> This one doesn't look like a valid APRS data type
>
> .: KE6JAB-1>APRS,UOSAT5*,APRSAT,ZS7ANT,I*:!7131.33S/00847.44E_Stanford U Wx,
> Blue One, Antarctica, 3680ft .:
>
> This one looks like it didn't make it through the packet length check. Which
> BTW has been removed from 2.2.1 (data < 252)
>
> Chuck
>
--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
| CARC Repeater 146.940 DN62 |
| http://groups.yahoo.com/group/RM-APRS |
| "The Dungeon" at http://go.to/KC7ZRU |
| LINUX user: 227845 http://counter.li.org/ |
+++++++++++++++++++++++++++++++++++++++++++++++
"I fear all we have done is to awaken a sleeping giant and fill him with a terrible resolve."
- Admiral Yamamoto
|
|
From: Hamish M. <ha...@cl...> - 2001-11-15 11:42:07
|
On Wed, Nov 14, 2001 at 11:47:34AM -0700, KC7ZRU - Tate wrote: > Packets are being dropped - two examples are: > ZR1CBC-3>DDF565,APRSAT,ZR1CBC,I*:'.O|l =1C[/>/A=3D000755 Not a known packet type? > KE6JAB-1>APRS,UOSAT5*,APRSAT,ZS7ANT,I*:!7131.33S/00847.44E_Stanford U Wx,= Blue One, Antarctica, 3680ft Too long according to APRSD's current rules. Maximum allowed comment is 43 characters, but due to a bug it is actually 41 characters. Expect to see this limit relaxed in the code any time now. Hamish --=20 Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
|
From: KC7ZRU - T. <kc...@ar...> - 2001-11-15 18:24:22
|
Ok - here's where we're at. 2.2.1 is supposed to be takeing care of the 'too long' packet. The origionating station is a home-brewed remote weather station out on the ice someplace in Antarctica. It was developed and built as a class project by a University here in the States. Sorry, don't have the school name at hand, but I can post it when I get back to the house. No way to change what it's sending out, so for this station at least - allowing the longer packets through is a "show saver". The 'unknown packet type' is decoding and displaying fine in UI-VIEW that's connected to my 2.1.4.vk3sb.2 server. Seems "something" is happening to it going through the 2.2.0 server. I've since upgraded both to 2.2.1 - no reports yet on if/what's changed. Could it be that I'm again not understanding the port usage? These two remote stations are connecting to the CSP-2 server via port 1313. CSP-2 then connects to CSP also via port 1313, which in turn connects to the core APRS IS via 10152. Is the 'local' data not local enough at some step? The whole idea is to get their data to the core, but not send them a bunch (if any) of data. They have a poor I-net link and pay for access by volume. With no use for the full TCP/IP feed, we're trying to limit what gets back to them. Thanks for the input guys. I appreciate it and the guys in South Africa do as well. 73 Hamish Moffatt wrote: > > On Wed, Nov 14, 2001 at 11:47:34AM -0700, KC7ZRU - Tate wrote: > > Packets are being dropped - two examples are: > > ZR1CBC-3>DDF565,APRSAT,ZR1CBC,I*:'.O|l [/>/A=000755 > > Not a known packet type? > > > KE6JAB-1>APRS,UOSAT5*,APRSAT,ZS7ANT,I*:!7131.33S/00847.44E_Stanford U Wx, Blue One, Antarctica, 3680ft > > Too long according to APRSD's current rules. Maximum allowed comment is > 43 characters, but due to a bug it is actually 41 characters. Expect > to see this limit relaxed in the code any time now. > > Hamish |
|
From: Hamish M. <ha...@cl...> - 2001-11-16 11:07:25
|
On Thu, Nov 15, 2001 at 11:24:06AM -0700, KC7ZRU - Tate wrote: > Could it be that I'm again not understanding the port usage? These two remote stations are connecting to the CSP-2 server via port 1313. CSP-2 then connects to CSP also via port 1313, which in turn connects to the core APRS IS via 10152. Is the 'local' data not local enough at some step? Hmm I think that sounds correct. Cheers Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
Thanks for helping keep SourceForge clean.
X