| |
ZL3AI > APRDIG 15.04.03 08:35l 121 Lines 4951 Bytes #999 (0) @ WW
BID : 1162-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 12, 2/2
Path: DB0FHN<DB0RGB<DB0FSG<DB0GAP<DB0GPP<DB0OFI<DB0LEL<DB0LX<DB0RBS<DB0SEL<
DB0ZDF<DB0AIS<DB0NDK<LX0PAC<LX0HST<HA3PG<JE7YGF<CT2GWY<CT4DK<ZL2TZE<
ZL3VML
Sent: 030414/1042Z @:ZL3VML.#80.NZL.OC #:63945 [Chch-NZ] FBB7.00i $:1162-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: APRS Multi Line
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Sat, 12 Apr 2003 16:32:15 -0000
X-Message-Number: 14
<Obligatory OpenTRAC plug>
The draft OpenTRAC spec provides an 'originating station' element, both for
high density reporting like you describe, and for non-AX.25 connections (for
an APRS-IS type system, for example.) It also includes sequence number and
originating network (VHF, Internet, UHF, Satellite, etc.)
</Obligatory OpenTRAC plug>
Sounds like a tough call for APRS, though. You'd be confusing the Kenwoods
again. Though I suppose you could trick terminal mode systems by sticking a
carriage return at the end of the first posit and faking a terminal mode
header to start the next.
For practical purposes, on the air at least, you're probably best off just
sending multiple AX.25 frames back-to-back. The header overhead adds a bit,
especially with a big path, but at least it's not going to confuse anything.
Scott
N1VG
----------------------------------------------------------------------
Subject: RE: APRS Multi Line
From: Jeff King <jeff@aerodata.net>
Date: Sat, 12 Apr 2003 15:51:18 -0400
X-Message-Number: 15
On Sat, 12 Apr 2003 16:32:15 -0000, Miller Scott Contr 30SCS/FTI=
wrote:
>For practical purposes, on the air at least, you're probably best off just
>sending multiple AX.25 frames back-to-back. The header overhead adds a bit,
>especially with a big path, but at least it's not going to confuse anything.
This would at least save the TXD time, which could be substantial since it
seems to be the norm on APRS to use TXD's 3-4 times longer then what is
really needed. This should be possible in constructing KISS frames although I
guess it depends on how the TNC decides to do it.
----------------------------------------------------------------------
Subject: findU2 down
From: Steve Dimse <k4hg@tapr.org>
Date: Sat, 12 Apr 2003 17:19:42 -0400
X-Message-Number: 16
Apparently the ops of findU are reseting the BIOS clock, and have brought
the system down for to do so. Unfortunately, I did not reset the
b2v.findu.com name to point to the primary server, and I cannot get logged
in as root to do so now.
Since I have no idea how long this is going to take (the only notice I got
was a notice of the system going down in a terminal I happened to have
open), those people trying to look at the Baker to Vegas run (which is just
starting) using the publicized name will not be able to, until the system
is back up. You can look at it on the primary server with this URL:
http://www.findu.com/cgi-bin/b2v.cgi
Sorry for further confusion on the day of the biggest event in APRSdom...
Steve K4HG
----------------------------------------------------------------------
Subject: Re: findU2 down
From: "Guy Story, KC5GOI" <kc5goi@tapr.org>
Date: Sat, 12 Apr 2003 20:32:37 -0500
X-Message-Number: 17
>Apparently the ops of findU are reseting the BIOS clock, and have brought the
>system down for to do so. Unfortunately, I did not reset the b2v.findu.com
>name to point to the primary server, and I cannot get logged in as root to do
>so now.
Steve, We were not aware of a large scale bike ride today. Had we known,
then nothing would have been done to the findu backup server today or for
the duration of the event. We are not in the habit of working on servers on
days we know of a large scale event (hobby or business related). I found out
when I returned from getting some errands completed that Clint had gone to
the co-lo site to 1.) perform normal upgrades and 2.) correct the bios clock
so the time stamps would be correct. This was an attempt to fix the
communication problem that you refered to in a post on April 12th.
>Since I have no idea how long this is going to take (the only notice I got
>was a notice of the system going down in a terminal I happened to have
>open), those people trying to look at the Baker to Vegas run (which is just
>starting) using the publicized name will not be able to, until the system
>is back up. You can look at it on the primary server with this URL:
Clint does not have your phone number and that was the only way he had to
notify you given the circumstances. The outage should have been breif.
Once again, we were not aware of this event and I no longer have time to
watch each and every email that goes through the APRSSIGs to watch for every
event that may be happening.
In referenance to the intrusion detection software you mentioned on the
April 12 post, it was installed to do just that. It is one of several
security measures that were installed. My boss is very security minded and
makes every attempt to keep any server we are responsable for nice and safe
>http://www.findu.com/cgi-bin/b2v.cgi
>
>Sorry for further confusion on the day of the biggest event in APRSdom...
73,
Guy Story, KC5GOI
kc5goi@kc5goi.net
---
END OF DIGEST
Read previous mail | Read next mail
| |
