|
Max, There are range filters that work well, but only for position reports. ?I usually have them set fro 350 km so positions of 0N 0W get rejected, but weather is not a position. ?You could block weather, but that blocks all weather stations. ?An option I use for "undesired stations" is to filter out that station using -b/callsign filter. ?It only works after you discover the bad station and put in the filter, but it won't happen again. Arnold kq6di From: "Max Harper kg4pid@... [direwolf_packet]" To: "direwolf packet" <direwolf_packet@...> Sent: Tuesday, February 21, 2017 11:48:44 PM Subject: Re: [direwolf_packet] IGFILTER in Rx only iGate While I agree with you, we are not given any control over that. While my station is not receive only, the other day there was a short band opening and I received a single packet from a distant station 400 miles away?via RF,?and for the next three hours I received their once per minute weather station packets. I counted all 180 of them. Seems like a lot of wasted bandwidth. Not to mention it fills?up my logs with useless data. See if you can spot both problems! Max KG4PID From: "kq6di@... [direwolf_packet]" To: direwolf packet Sent: Wednesday, February 22, 2017 12:05 AM Subject: [direwolf_packet] IGFILTER in Rx only iGate
?
I have a Receive Only iGate. ?The T2 servers keep sending my iGate packets they think are going to go to RF. ?Obviously they don't, but what is the way to stop getting iGate messages for transmit? IGFILTER no send ???? IGFILTER -everything ??? There must be a way that I haven't found because I get about 20 messages an hour that it wants to send. Arnold KQ6DI |
