July 2020 - PSDR - mailman.hamwan.org

Grants
by John D. Hays 15 Dec '20

15 Dec '20

Please review https://www.ampr.org/giving/ If you have a project, development, etc. that could benefit from a grant, here is your opportunity. -- John D. Hays Kingston, WA K7VE

11 21

Lower 45 MHz of 5.9 GHz to go license-exempt
by Steve Stroh 02 Dec '20

02 Dec '20

https://www.fcc.gov/document/chairman-pais-remarks-new-59-ghz-band-proposal -- Steve Stroh (personal / general): stevestroh(a)gmail.com

5 4

Mikrotik Firewall
by Rob Martin 29 Aug '20

29 Aug '20

Greetings, I have been writing a lot of Mikrotik Firewall rules lately. I know I am getting better at it, but the more I know, the more apparent it is that there is a lot more to learn! I have questions about how best to use the Mikrotik Firewall. The lines below are to illustrate the issue, and are not comprehensive. Also, I have used extra spaces to make it easier to see what I am doing. Let’s say I want to block a list of address ranges, in this case (some of the) Bogons, those non-routable addresses that should never be the src-address of any incoming traffic from outside my network. For whatever reason, traffic from Bogons shows up anyway. First, add the addresses to the address-list. /ip firewall address-list add address=10.0.0.0/8 list=Bogon add address=172.16.0.0/12 list=Bogon add address=192.168.0.0/16 list=Bogon Technique #1 – Drop incoming Bogon traffic in the Firewall Filter. The determination as to whether the traffic is arriving through the tunnel, and whether its src-address in on the Bogon list is performed twice, once for chain=input and again for chain=forward. /ip firewall filter add chain=input action=drop in-interface=Tnl src-address-list=Bogon add chain=forward action=drop in-interface=Tnl src-address-list=Bogon Technique #2 – Mark the incoming Bogon traffic prior to routing using Firewall Mangle – chain=prerouting - then drop it in Firewall Filter with two simpler rules. A single Firewall Mangle rule will mark everything in one rule. That is all it does. The two Firewall Filter rules that follow only have match the packet-mark. /ip firewall mangle add chain=prerouting action=mark-packet new-packet-mark=Bogon_from_Tnl passthrough=no src-address-list=Bogon in-interface=Tnl /ip firewall filter add chain=input action=drop packet-mark=Bogon_from_Tnl chain=forward action=drop packet-mark=Bogon_from_Tnl I think both of the above techniques will achieve the same result, blocking Bogon traffic arriving through the tunnel. Questions: 1. Which method is better, and by better I think I mean, which has the lowest impact on the performance of the router? 2. Does the answer depend on the number of the Bogons in the address-list? 3. Does the answer depend on where in the Firewall Mangle list the Mangle rule is positioned? 4. Does the answer depend on where in the Firewall Filter list the Filter rules are positioned? 5. Is there a way to measure any of this quickly with simple tools, and on a limited budget? Who out there is a Firewall expert?!! Rob K7QJ

3 2

First Oregon node?
by Justin Roberts 01 Aug '20

01 Aug '20

After finally receiving all the components from Lithuania I got online yesterday! The client node configuration instructions couldn’t have been easier to work with accompanied with the video from K7MM. Initially I popped the antenna up there and pointed in what I calculated to be the right location and surprisingly I was nearly spot on. I did a little fine tuning this morning. Granted, my day job involves aiming microwave antennas. It looks like there is only one other node online connected to Larch, KD7RYY in Vancouver. Does that make me the first Oregon node online? I plan to leave the station online with my DMR hotspot and some low bandwidth weather station logging for a few weeks then I wanted to offer an uplink node. I am hoping this will aid in supporting coverage further into Oregon. W6UDF Portland, Oregon

2 1

VOTE: PTZ for Triangle site
by Bart Kus 17 Jul '20

17 Jul '20

Hello, With Blyn's backbone dishes (NOT sectors yet) on the air, there's a mission to Triangle this weekend to install a dedicated dish that points at Blyn. This will provide a high speed link all the way from Triangle to the rest of the network via Blyn and SnoDEM. Given the new bandwidth capacity, running a PTZ there is finally viable. The tower owners have agreed to let us add a PTZ there to help with remote diagnostics and user LoS verification. The costs of this spend request are as follows: PTZ: $460 PSU: $50 TOTAL: $510 Shipping and taxes extra. My vote is YEA. I expect we'll be doing more of these upgrades to our sites, as man-power allows for installations. --Bart

5 5

Site Application
by Jamie Hughes 17 Jul '20

17 Jul '20

Hello, I am in the process of filling out a site application. It requires the frequency both TX and RX. Would someone be willing to point me in the right direction for what is in use for HAMWan? 73 Jamie Hughes WA7JH Phone: (360) 362-4575<tel:+13603624575>

2 4

VOTE: Replace SnoDEM.Haystack (repair spending)
by Bart Kus 16 Jul '20

16 Jul '20

Hello, Both clients to SnoDEM.Haystack are super weak on ch0. This implies a fault with SnoDEM.Haystack. I'd like to go up there with a full dish+modem kit to swap out the whole thing and not do diagnostics on the mountain top. PTZ does not show any obvious physical damage to ch0 cable or dish. I would like to draw upon existing inventory to perform this repair. Here are the estimated costs: Dish: $130 Shield: $100 Modem: $150 TOTAL: $380 I can do diagnostics and salvage what is possible once the faulty gear is down on the ground. My vote is yea. Since this is a repair measure, only 1 more supporting director vote is required for it to pass under our standing repair spending rules. --Bart

4 4

HamWan Speaker
by Bob Stephens 15 Jul '20

15 Jul '20

I hope it is ok to post this request to this forum. I am the President of the Island County ARC on Whidbey and the Island County ARES/RACES EC/RO. We are looking at creating a digital network on the Island for EMCOMM using packet and Winlink both VHF/UHF and HF. We have looked at HamWan for the island before but our EOC's do not have line of site. The island has lots of trees and topography that makes line of site anything difficult. We do have some hams that live near the water that might have HamWan access, especially when Blyn comes online. Most of these hams are recently new and don't know much about HamWan. I was wondering if there was someone who could do a Zoom presentation introducing HamWan to our club on July 25th. The Zoom would start shortly after the meeting is called to order at 9:30am. Bob Stephens AF9W President, Island County Amateur Radio Club Island County Amateur Radio Emergency Coordinator Island County RACES Radio Officer Home: 360-579-4257 Cell: 520-576-3087

6 6

Re: [HamWAN PSDR] Got a problem
by Bob Sampson 13 Jul '20

13 Jul '20

Christopher, Yes, it looks ok now. I am able to trace route and ping to 8.8.8.8 without issue. Thanks for the quick response. ================ Bob Sampson k6mby(a)olypen.com 360-477-0776 (cell) Sequim, WA

1 0

Got a problem
by Bob Sampson 13 Jul '20

13 Jul '20

Good day, Have a problem that I am not sure where to go for support. I have a client node off Lookout in Sequim, WA. Until a few days a go it worked flawlessly serving DMR, packet 1200, VARA FM and VARA HF. The client HamWAN hardware is still connected to Lookout but I am unable to get service for the attached services. Going to tools and using traceroute to 8.8.8.8, as and example, I only get so far before there is a 100% failure… I am certainly a noobe when it comes to poking around the the router so any help would be appreciated. And yes, I did restart to HamWan router. ================ Bob Sampson k6mby(a)olypen.com 360-477-0776 (cell) Sequim, WA

2 2