July 2019 - PSDR - mailman.hamwan.org

VOTE: Board Director Elections - Tom
by Tom Hayward 30 Jul '19

30 Jul '19

I am announcing my intention to serve on the HamWAN board of directors for the year following the conclusion of this vote. The voting period defined in the HamWAN constitution is 7 days, starting now. A reminder of the voting procedures can be found in the quoted email below. I have served as a Network Operator for HamWAN's Puget Sound network since 2013. I have contributed greatly to HamWAN software development: https://github.com/HamWAN. And I have taken an active role in new site research, design, and installation. Tom KD7LXL On Mon, May 13, 2019 at 8:37 PM Nigel Vander Houwen <nigel(a)nigelvh.com> wrote: > Hello Everyone, > > It’s been a year since our current board members were elected, so it’s > time for new elections. > > As a quick recap for folks that haven’t been around, or need a reminder: > > > - Board member positions last for one year. > - Any supporting member is eligible to vote for board members. > - Any supporting member is eligible to run for a position on the board. > - There is no limit on the number of board members, so if you want to > run and participate, you’re not taking a spot away from anyone else. > - There is a minimum number of 3 board members. > - Supporting members are those who have contributed at the Basic level > ($20/mo) (or more) for the last 6 months. > - Voting is open for 7 days. > - Each board member is a separate “election”, IE you don’t have to > choose one person to vote for, you choose Yay or Nay for all individuals. > - Please respond to the list with your votes, the list serves as our > public record. > > > Here’s our current list of supporting members (the folks who are eligible > to vote on directors, or run for director themselves) (Thank you Cory for > pulling this together): > > - Bart Kus > - Bob Edmiston > - Carl Leon > - Cory Johnson > - David Giuliani > - Doug Kingston > - David Yost > - Dylan Ambauen > - Ian Gallagher > - Jim Hudspeth > - Kenny Richards > - Marc Lacy > - Mark Sheppard > - Mikel Shirley > - Nick Hall > - Nigel Vander Houwen > - Robert Salsgiver > - Ronald Zuber > - Ryan Cukierman > - Ryan Turner > - Terence Chan > - Tom Hayward > - Randy Neals > > I’d like to thank everyone for contributing to the project, and helping us > grow. We’ve seen a handful of new members added this year, in addition to > quite a few new non-member users/orgs. This speaks greatly to the massive > efforts of a number of folks in the project doing installs, giving > presentations, and talking about HamWAN. > > We’ve seen a lot of great progress over the past year, not to mention a > number of new users on the network. Here’s a small sampling of some of the > things accomplished over the past year. > > > - Quite a handful of new Network Operations folks have been brought > on, and are quickly tackling issues and making improvements. Thanks team! > - A couple visits to our Capitol Park site saw new backbone links > installed, sector upgrades, and additional batteries in case of power > outage. > - Phone adoption has been taking off considerably with ACS and other > emergency services folks on board. > - Gear installed at Buck > - Gear installed at Beacon Hill > - Gear installed at Larch > - Work at the Seattle EOC > - Upgrade work at Snohomish County DEM > - Upgrade work at Haystack > - Upgrade and repair work at Gold > - New edge router at FMT as a partial replacement for Tukwila, which > gives us internet facing redundancy > - Aiming visit to Baw Faw > - Probably a bunch more that I forgot or managed to scroll past in my > emails. > > > All of these things and more have been the results of massive efforts of a > whole lot of people this year. Thanks to every one of you for making this > happen. HamWAN is entirely volunteer driven which makes such an enormous > undertaking even more remarkable. Whether your contribution was in time > onsite tightening bolts, or with a few dollars that helps us buy new modems > and dishes, it’s all been valued. Thank you. > > So, to the final point. It’s time to vote again on the board directors. > For the past year Bart Kus, Cory Johnson, Rob Salsgiver, Doug Kingston, and > myself have acted as the board for HamWAN. I have appreciated their work > over the past year, and if they choose, I hope to continue doing so this > year. > > Cory Johnson - Cory has graciously handled HamWAN’s financial and legal > filings and reports. I’m incredibly grateful for his efforts. Thank you > Cory! > > Bart Kus - Bart continues to put enormous effort into the physical aspects > of the network, particularly in his gracious hosting of our site at > Haystack, some software projects, as well as acting as an administrator for > the Puget Sound network day to day. Thank you Bart! > > Rob Salsgiver - Rob has been a significant driver in terms of organizing > what work needs to be done in the network, and making sure it gets taken > care of. In addition to that, he has been coming up to speed as a Network > Operations member, and has been tackling a number of issues. > > Doug Kingston - Doug has been part of a number of big wins for the network > over the past year, both in terms of new sites, as well as getting projects > done and maintaining existing ones. He has additionally been working on > Network Operations and has jumped in to tackle issues that the rest of the > team hadn’t been able to get to. > > Nigel Vander Houwen - (me) I handle much of our contract work, and record > keeping around technical aspects like LoAs, I serve as a day to day network > administrator, and have helped deploy and maintain some of the on-network > services, occasionally I manage to make a site visit to help out, and I > handle things like the email you’re reading now. > > I have spoken with Bart, Rob, and Doug with regards to serving on the > board again this upcoming year. Rob and Doug have graciously offered to > continue serving. Bart has chosen to step away from the Board work and > focus on the other aspects of HamWAN and I look forward to our continued > work. > > For anyone who wishes to run for the board, please send an email to the > mailing list announcing your intention to run (You’ll see mine momentarily > as an example). The voting period on your election will end 7 days after > your announcement. Duties are not time intensive, and mostly consist of > being available for occasional calls to approve expenses, and assisting > HamWAN in whichever ways your time and/or skills/knowledge allow. > > Thank you all for reading this rather long email, and I hope to work with > you all here in this next year. > > Nigel Vander Houwen > _______________________________________________ > PSDR mailing list > PSDR(a)hamwan.org > http://mail.hamwan.net/mailman/listinfo/psdr

11 12

Encryption on HamWAN
by Thom Wescott 28 Jul '19

28 Jul '19

Nigel, Thanks for the reminder, I'm not one to argue that, but it does bring up a question. There is not much of the web left that is not HTTPS, I'm thinking particularly of emergency management sites such as WebEOC. Is this violation likely to be excused when providing communications support in a real public emergency? Thanks, Thom Wescott KI7EFG

11 15

HamWAN Thank you
by Dakers, Scott (MIL) 28 Jul '19

28 Jul '19

Thank you all for installing HamWAN into the Radio Room at Camp Murray. This was a huge project. I look forward to the steep learning curve I will have to fully utilise HamWAN. Having this happen has been a priority for us. Your willingness to install it into the RACES Radio Room is truly appreciated. Again, thank you! Best regards, Scott Scott G. Dakers Washington State Emergency Management Division Logistics Program Auxiliary/ RACES Radio Communications Station Manager Cell/ Text: (559) 804-1851

3 3

Baldi S3 back to normal
by Rob Salsgiver 28 Jul '19

28 Jul '19

Baldi S3 was returned to normal about an hour after my initial email. All should be functioning normally on S3 at this time. Let me know if you see any problems. We changed frequencies/channel sizes to aid in aiming the new PTP dish to Baldi from Camp Murray. Unfortunately we'll need to tweak the aim on the Baldi end to complete the work, but we at least now know we have the Camp Murray dish properly aimed at Baldi. Cheers, Rob

2 1

Camp Murray install update
by Rob Salsgiver 28 Jul '19

28 Jul '19

After a 2nd long day I'm happy to report that the WA State EOC at Camp Murray is online. All of the tower work is done, but there is still some configuration updates and off-tower tweaking to be completed, as well as walking Camp Murray staff through the use of HamWAN, documentation/etc. A BIG "thank you" to Mike Ping, Scott Honaker, Ed Braaten, Scott Burrows, and Bob Purdom for their help in finishing off major work today. I'll be following up in a couple weeks to wrap up the remaining little items. I would also like to thank our crew from last weekend - Bart Kus, Carl Leon, Doug Kingston, Tom Hayward, and Steve Aberle who got it all started. Both crews worked well and it was very productive both Saturdays. This has been a huge milestone for HamWAN and WA State EMCOMM, as this allows existing and future EOCs to have a high-speed data and communications path to augment traditional amateur radio in a disaster. Thanks to everyone involved in HamWAN - it's your contributions throughout the project that have made this all happen. Cheers, Rob Salsgiver - NR3O

3 2

AMPR/ARDC selling 1/4 44 IPs to Amazon?
by Chad Smith 27 Jul '19

27 Jul '19

https://mailman.nanog.org/pipermail/nanog/2019-July/102103.html KA7HAK

2 1

Baldi S3 offline for Camp Murray alignment today
by Rob Salsgiver 27 Jul '19

27 Jul '19

Greetings all, I'll be changing the frequency and channel width of Baldi S3 for a while today to help in aligning a new PTP at Camp Murray. Should be back to normal in an hour or two once we get everything wrapped up. Existing clients will be offline while this is done. Rob

1 0

Re: [HamWAN PSDR] Encryption on HamWAN
by Edmund Leavitt 19 Jul '19

19 Jul '19

My experience with microwaves is limited almost entirely to the unlicensed 2.45 GHz system in my kitchen that thaws food and reheats coffee. So please forgive the fundamentally ignorant question. Is it feasible to switch to something other than 47 CFR 97 freqs without obsoleting the existing hardware? ______________________________________________ Edmund Leavitt K7EFL / AFZ0AH USNG: 10TET36292223 ______________________________________________ ---------- Original Message ---------- From: Bart Kus <me(a)bartk.us> To: Puget Sound Data Ring <psdr(a)hamwan.org>, Nigel Vander Houwen <nigel(a)nigelvh.com> Subject: Re: [HamWAN PSDR] Encryption on HamWAN Date: Fri, 19 Jul 2019 12:54:30 -0700 I think it's important to recognize that the Internet has changed significantly since the project's inception in 2012. Two very important things came to pass, that impact the HamWAN use case arguments in 2012: 1) HTTPS became universally deployed, instead of being reserved for specific pages. 2) Browsers have removed support for null-cipher HTTPS. Even the use case of surfing Wikipedia can't be done on HamWAN these days. Heck, you can't even do a Google search for anything. Is there a point to powering a network that's so useless? As Thom points out, it can't even be used for WebEOC emcomm either. People need to regularly test + practice emcomm tools for them to be usable in a real emergency. This is not allowed right now. Part97 is incompatible with modern computing life, and we might be better off having a smaller footprint that offers actual utility. Or we can just wait a couple years for StarLink / OneWeb. --Bart On 7/19/2019 12:27 PM, Nigel Vander Houwen wrote: > Thom, > > This is something we’ve thought about as well. The FCC is explicitly permissive in the case of a real emergency, though that doesn’t really cover the use case during the rest of the time. This is one of a number of reasons why we (the network admins) have specifically avoided blocking anything but blatant abuse (mostly virus type stuff). We want to leave the possibility open in terms of the network for these sorts of cases, but that comes with users needing to take on the responsibility to maintain their own compliance. > > The team is discussing ways we can help with this, while leaving things as flexible as possible. One of the current front running ideas is adding instructions to the client node configuration page that everyone uses to set up their modems, to block HTTPS at your modem. That leaves you the option to disable it if required (unlike if we implemented the block on the network side), but helps to maintain compliance during regular activities. It’s still very much an active discussion at this point, but if folks have ideas we’ll certainly welcome them. > > Thanks, > Nigel > >> On Jul 19, 2019, at 12:17, Thom Wescott <thom.wescott(a)gmail.com> wrote: >> >> Nigel, >> >> Thanks for the reminder, I'm not one to argue that, but it does bring up a question. There is not much of the web left that is not HTTPS, I'm thinking particularly of emergency management sites such as WebEOC. Is this violation likely to be excused when providing communications support in a real public emergency? >> >> Thanks, >> >> Thom Wescott >> KI7EFG >> _______________________________________________ >> PSDR mailing list >> PSDR(a)hamwan.org >> http://mail.hamwan.net/mailman/listinfo/psdr > _______________________________________________ > PSDR mailing list > PSDR(a)hamwan.org > http://mail.hamwan.net/mailman/listinfo/psdr _______________________________________________ PSDR mailing list PSDR(a)hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr

1 0

Reminder on HamWAN use
by Nigel Vander Houwen 18 Jul '19

18 Jul '19

Hello All, Due to some recent activity we’ve seen on-network, we’d like to send a reminder to folks about being careful about HTTPS or other SSL traffic. HamWAN sectors and by extension your modems run on Part 97 frequencies where encryption is not permitted. HamWAN cannot be a replacement for your commercial internet service, and you are responsible for maintaining compliance. For now this is a general reminder. In the future we’ll be working to help remind individuals specifically when we notice a problem. Thanks again for your help and support! Nigel

1 0

Camp Murray volunteer update
by Rob Salsgiver 17 Jul '19

17 Jul '19

We are good at the moment for this coming Saturday - 7/20 unless you happen to be a card-carrying tower climber <g>. Thanks to Doug, Carl, Tom, Steve, and Kenny for stepping up to help out this weekend. Next weekend (7/27) we have NO additional ground crew other than myself. If you can help out on Saturday the 27th, please let me know. Depending on how much we accomplish this weekend we may or may not need the 27th. More as soon as we know it. Cheers, Rob

1 0