[aprssig] Firenet F5RVX
AE5PL Lists HamLists at ametx.comWed Nov 3 17:27:27 UTC 2004
- Previous message: [aprssig] New Tier 2 servers
- Next message: [aprssig] D7A(G2.0) Callsign List
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: Curt, WE7U > Posted At: Wednesday, November 03, 2004 10:45 AM > Subject: RE: [aprssig] Firenet F5RVX > > Please refrain from pummelling him with a large number of e-mails. > He may not know English all that well and he's already been > contacted. The dual-connect problem has been temporarily > solved as well, so the objects should expire off your screens > soon unless you're connected to firenet directly. > > We'll work through the issues and find a more permanent > solution for it. I agree and I apologize for encouraging such a response. Phillipe does understand English but is a newbie so this is his first foray into APRS and Xastir. I encouraged him to contact you directly, Curt, to figure out what is going on. The q constructs I saw were qAR,F5RVX and qAo,F5RVX so it was coming from his Xastir station (unless he has another station with the same SSID which is possible since he is a newbie). I also agree with Phil that multiple simultaneous bidirectional connections to one or more servers from a client (or server) should not be used (or possible) due to problems such as this. Address rotation (either using rotate.aprs.net or rotate.aprs2.net, or by using specific rotations defined in the client software) is definitely the way to go to continue to clean up the APRS-IS data stream. 73, Pete Loveall AE5PL mailto:pete at ae5pl.net
- Previous message: [aprssig] New Tier 2 servers
- Next message: [aprssig] D7A(G2.0) Callsign List
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
