February 2023 - PSDR - mailman.hamwan.org

Re: [HamWAN PSDR] HamWAN Board Director Elections - Cory Johnson, Rob Salsgiver, Doug Kingston, and Dylan Ambauen
by Alan Dieringer [WX7L] 26 Feb '23

26 Feb '23

Cory: Yea Doug: Yea Dylan: Yea Rob: Yea Thank you all for building HamWAN and PSDR, Rob, Nigel, Tom, Bart, Doug, Cory and many others. Alan WX7L

1 0

mANT30 dish antenna
by Michelle Michaels 26 Feb '23

26 Feb '23

Apologies if this is not the right place but I have a used mANT30 dish that I need out of my storage locker. Looking to sell it for 50$ or donate it to an emcom or other organization that's in need. All the mounting bits are there but no radio or coax. Thanks Morgan N7BCN

2 1

HamWAN Board Director Elections - Announcement
by Rob Salsgiver 24 Feb '23

24 Feb '23

Greetings All, It is once again time for annual elections for the HamWAN Board of Directors. Here's a quick recap of the main points for those that need a refresher. * 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. If you feel you would be valuable, you're not taking a seat away from someone else. * There is a minimum of 3 board members required by the constitution. * Each board member is a separate election. You don't have to choose only one person to vote for, you choose Yea or Nay for each individual. * Please respond to the list here with your votes. This serves as our public record. * We do not have a concept of nominations. The individual themselves must express intent to run for a board position. The term Supporting Member is a specific criteria defined in the constitution as individuals who have contributed at the Basic Level ($20/mo or more) for at least the last 6 months. Both the time and financial criteria must be met to count. There have been a couple instances of employer matching or other donations that aren't always attributed to the proper source, so if you feel that you've been missed in this list, I apologize. Please reach out and we'll get it corrected. The current list of Supporting Members is: . Tim Osburn . Terence Chan . Alan Dieringer . Bob Edmiston . Burt Guillot . Carl Leon . Casey R Hickerson . Chuck Dorsett . Cory Johnson . Dana Hanford . David Giuliani . Doug Kingston . Dylan Ambauen . Ian Gallagher . John C Miller . Kenneth Koster . Kenneth Richards . Nigel Vander Houwen . Paul Sundquist . Randy Neals . Robert Salsgiver . Robert Sampson . Ronald Zuber . Warren Churchward The last couple of years have given us some challenges. A lot of effort was put into recovering from the loss of DNR leases that kept us from moving forward as much as we could have, and the extended "malaise" from Covid continued to put a drag on things. Supply chain issues has limited the availability of some Mikrotik (and other) equipment, although some of that is improving. There are a few interesting bright spots on the horizon which we'll discuss more in future emails. I would like to thank everyone who has contributed over the last year (plus). Ones who immediately come to mind are Doug Kingston, Cory Johnson, Nigel Vander Houwen, Bart Kus, Kenny Richards, and Tom Hayward. If I have missed someone, please accept my apologies and let me know. I see HamWAN at somewhat of a turning point. We are fortunate to still have the support and expertise of many of our earliest minds, although time and family commitments limit their availability. In order to develop a common, sustainable project we need to involve more resources and create a plan on what that means and how to make it happen. We need to build the organization to survive not just year to year, but for the years to come, even as each of us comes and goes within the organization. The first step is to elect a new Board. Cory Johnson and myself intend to continue forward (if voted) into the next year. Doug Kingston and Dylan Ambauen have also indicated their willingness to run and assist at the Board level. For anyone else who wishes to run for the board, please send an email here to the mailing list announcing your intention to run. The voting period on your election will end 7 days after your announcement. Duties largely consist of being available for occasional votes to approve expenses or discuss larger organizational decisions a minimum of quarterly. It is encouraged to write a small blurb about yourself and what you would like HamWAN to do, and what you bring to the table, so that folks who aren't immediately familiar with your name can have an idea on who they're voting for. There will be much to do in the coming year(s). If your life currently allows you to help out at the Board, NetOps, or even on a periodic project or administrative level, I ask you to consider lending a hand. I welcome your thoughts and input. Election and voting email(s) will follow this announcement. Cheers, Rob Salsgiver - NR3O

4 3

HamWAN Board Director Elections - Cory Johnson, Rob Salsgiver, Doug Kingston, and Dylan Ambauen
by Rob Salsgiver 24 Feb '23

24 Feb '23

Greetings all, In order to cut down on the number of emails, I have combined those I know who have agreed to stand for election into this initial email. If you are a Supporting Member who wishes to also run for a Board position, PLEASE DO by announcing your intention via the list in similar fashion to below. Cory Johnson has acted as our Treasurer/Secretary for a number of years, and whose efforts have truly been invaluable. Cory handles the finances, makes sure the taxes get filed, and the bills get paid. His help in this area "behind the scenes" allows others to devote their time to the technical and operational sides of the organization. Doug Kingston has previously served and after some time off has indicated he is willing to serve once again. Doug has been involved in many projects throughout the years in the Seattle region and elsewhere, assisting in troubleshooting, documentation, and site installations only to name a few. Dylan Ambauen has been with the organization several years as a contributing member of the NetOps group assisting with troubleshooting and regular maintenance, as well as participating in numerous site commissioning and de-commissioning operations. Rob Salsgiver (myself) - Past/current Board member, part of the NetOps group, assisted with site installations, maintenance, funding, and other items as needed. I tend to like organizing and documenting things such that almost anyone can do them. I've been in IT since the early 80s (which may be a good or bad thing - you decide). Beyond that I really don't care to "toot my own horn", so if you have questions - shoot. The voting period for the 4 individuals above will conclude 7 days from now. Supporting members, please reply in this thread with your Yea, Nay, or Abstain votes. Remember that each individual is a separate election, you do not have to choose one individual. Thank you all for your consideration, and I hope to have the opportunity to work with you further over the next year. Cheers, Rob Salsgiver - NR3O

7 6

We need to design secure control access
by Bart Kus 08 Feb '23

08 Feb '23

All of the network's control points are on public non-firewalled IPs. This is the worst security. It was done this way for the sake of simplicity. Our netops volunteers had to get up to speed with unfamiliar concepts like routing, funky netmasks, dynamic routing protocols, policy routing, VRRP, firewalls, MTUs, MSS control, IPsec, etc. We reaped the rewards of KISS from broader volunteer engagement, but lately we've been paying too heavy of a price for the awful security this simplicity creates. In the most recent breach we've lost important source code that will now need to be re-created. We escaped total disaster by the thinnest of margins, as one critical hypervisor just happened to be patched to 1 version higher than exploitable. This simplicity is not a good tradeoff anymore, so the time has come to introduce more complexity to the network to protect all control points. This is not a simple problem, since there are many fragility vs security tradeoffs, as well as complexity cost concerns. If you have experience or thoughts around this area, and can commit to a few weeks of design and implementation work on this project, please indicate your interest. We'll assemble a small working group in the next few days and start discussions. I expect the working format will involve some virtual meetings, since email is not high bandwidth enough to hash out everything quickly. Here's hoping we don't make it worse, --Bart

5 7

Re: [HamWAN PSDR] We need to design secure control access
by Nick Kartsioukas 08 Feb '23

08 Feb '23

I'm interested in assisting and have some ideas. Experience: I've been doing networking and Linux sysadmin stuff since the late 90s and have been in an infosec role for the past ~7 years. > On Feb 8, 2023, at 03:34, Bart Kus <me(a)bartk.us> wrote: > All of the network's control points are on public non-firewalled IPs. This is the worst security. It was done this way for the sake of simplicity. Our netops volunteers had to get up to speed with unfamiliar concepts like routing, funky netmasks, dynamic routing protocols, policy routing, VRRP, firewalls, MTUs, MSS control, IPsec, etc. We reaped the rewards of KISS from broader volunteer engagement, but lately we've been paying too heavy of a price for the awful security this simplicity creates. In the most recent breach we've lost important source code that will now need to be re-created. We escaped total disaster by the thinnest of margins, as one critical hypervisor just happened to be patched to 1 version higher than exploitable. This simplicity is not a good tradeoff anymore, so the time has come to introduce more complexity to the network to protect all control points. > > This is not a simple problem, since there are many fragility vs security tradeoffs, as well as complexity cost concerns. If you have experience or thoughts around this area, and can commit to a few weeks of design and implementation work on this project, please indicate your interest. We'll assemble a small working group in the next few days and start discussions. I expect the working format will involve some virtual meetings, since email is not high bandwidth enough to hash out everything quickly. > > Here's hoping we don't make it worse, > > --Bart > > _______________________________________________ > PSDR mailing list > PSDR(a)hamwan.org > http://mail.hamwan.net/mailman/listinfo/psdr

2 1