[aprssig] CW stations and ui-view igate
Eric Christensen kf4otn at ericsatcom.netThu Jun 16 21:01:57 UTC 2005
- Previous message: [aprssig] CW stations and ui-view igate
- Next message: [aprssig] CW stations and ui-view igate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Well, I can tell you that there are quite a few more than 2 within 100km of my location... -----Original Message----- From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Andrew Rich Sent: Thursday, June 16, 2005 15:45 To: TAPR APRS Mailing List Subject: RE: [aprssig] CW stations and ui-view igate It is not dangerous if in the filter definition you put filter m/100 I only get stations within a 100 km radius. There are only two weather stations within 100 kms of me. That is all that comes in on the aprs server link, that is how i have it configered. Alot of people over look this. They ASSUME a world wide feed. If you only let in a few stations, you can only ever gate a few stations hi hi Cheers Andy -----Original Message----- From: Eric Christensen [mailto:kf4otn at ericsatcom.net] Sent: Friday, 17 June 2005 2:07 AM To: aprssig at lists.tapr.org Subject: RE: [aprssig] CW stations and ui-view igate UI-View is seeing as "foreign". There is a way to gate them out, though, in the igate.ini file BUT I warn of how you have them setup. CW*=ALL will put thousands of stations out on RF. Not a very good idea. Email me directly if you need specifics on the modification to the igate.ini file (or you can look for yourself). 73s, Eric KF4OTN -----Original Message----- From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Steve Dimse Sent: Thursday, June 16, 2005 06:44 To: TAPR APRS Mailing List Subject: Re: [aprssig] CW stations and ui-view igate On Jun 16, 2005, at 6:24 AM, AE5PL Lists wrote: > CW stations use an unverified login (see post in other thread > describing > these) which I would guess UI-View recognizes as non-ham and refuses > to gate them to RF. > I do not know specifically about UI-V, but some other IGates will pass unverified packets when the call is specifically included in the list. Obviously using CW* in this situation would be a disaster, but specific local CW stations would not cause excessive QRM. Speaking only of US rules, this is not illegal. Under the Automatic message forwarding system rules, unless a verification is made, the first station to transmit a message on RF assumes responsibility for the content of the message. If it is a CW station, the risk to an IGate operators license is small, but still real. This is why the default behavior of the system is to exclude unverified packets. So just to fine tune your statement in the previous message, the verification does not PREVENT those packets from being IGated to RF, but rather allows the IGate operator to decide for him/herself whether to assume responsibility for those messages. Steve K4HG _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3108 bytes Desc: not available Url : http://www.tapr.org/pipermail/aprssig/attachments/20050616/7de39e08/attachment.bin
- Previous message: [aprssig] CW stations and ui-view igate
- Next message: [aprssig] CW stations and ui-view igate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
