[aprssig] CW stations and ui-view igate

[Eric Christensen]

I'll have to go back and look when I get a chance. 

-----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:51
To: TAPR APRS Mailing List
Subject: RE: [aprssig] CW stations and ui-view igate

u lost me on Igate.ini I can not see anything obvious that is
blocking this ?





-----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://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20050616/f9041e7c/attachment.p7s>