[aprssig] Droping WIDEn-N does work!

[Brian B. Riley]

I dropped WIDEN-N here in NW VT at N1BQ-3 last Spring ... And it has made a
major difference. I was the "bridge" between the Albany/Saratoga NY LAN and
the Montreal LAN and was regularly 'passing' WIDEN-Ns that were 4 to 7 hops
with at least 2 hops left after it hit me. The probability of NW VT APRSers
getting posted to FINDU via the iGate in Montreal more than doubled as a
result


On 12/9/04 10:27 AM, "Robert Bruninga" <bruninga at usna.edu> wrote:

> Here is a report from Arizona on droping WIDEn-N routing
> to reduce out-of-area QRM:
> 
>>>> <dick at kb7zva.com> 11/22/04 12:45:24 PM >>>
>> ... I changed my digi outside Yuma saturday. And our load
>> dropped 50% from the outside world.  We are actually
>> starting to see our own RELAY,WIDE mobiles!
> 
> And a followup report a month later:
> 
>> It worked fine... we are attempting to get more digis [to do it].
>> So far, the 2 main digis are doing RELAY,WIDE only.
>> Most locals are running WIDE and mobiles are set to RELAY,WIDE.
>> My Igate went from 180 RF stations heard to less than 40.
>> 
>> But to also support W2-2 and W3-3 locals, we added
>> those starting paths into the UIDIGI alias list so that mobiles
>> using a "decent path" of W2-2 or W3-3 will get out.
>> 
>> UIDIGI ON RELAY,WIDE,WIDE2-2,WIDE3-3
>> 
>> My digi ALOHA circle is 180 miles. However, one hop covers
>> most of it. So my unproto path for the Igate is APRS,WIDE.
>> Which converts to APU25N,WIDE in UIview.
>> 
>> This has been a major improvement and everything is covered fine
>> within the ALOHA.
>> Happy Holiday's
>> Dick 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig