- PSDR - mailman.hamwan.org

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

Recommended Donation
by Jamie Hughes 22 Dec '22

22 Dec '22

Dear HamWan Management team, I am looking for a recommended donation amount. The Kitsap County Amateur Radio Club has used HamWan as its primary internet connection now for 18 or so months for our repeater and camera. I was hoping we could be given some guidance as to what you would recommend. We apricate the efforts of Dylan in getting us setup. 73 (Ham radio way of saying Best Regards), Jamie Hughes WA7JH President / Public Information Officer / Repeater Committee Chair, KCARC Public Information Officer, ARRL - Western Washington Section Email: president(a)kcarc.org<mailto:president@kcarc.org> Phone: (360) 340-8886<tel:+13603408886> Kitsap County Amateur Radio Club<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kcarc.…> PO Box 2268 Silverdale, WA 98383 [cid:image001.png@01D9155D.9EC2D210]<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kc7z.o…> [cid:image002.png@01D9155D.9EC2D210]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.c…>[cid:image003.png@01D9155D.9EC2D210]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [cid:image004.png@01D9155D.9EC2D210] <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [cid:image005.png@01D9155D.9EC2D210] <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> [cid:image006.png@01D9155D.9EC2D210] <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [cid:image007.png@01D9155D.9EC2D210]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsmile.ama…>

3 2

stream.westin.hamwan.net got an upgrade
by Bart Kus 21 Dec '22

21 Dec '22

Hello, Our video streaming service got completely redesigned and is now available at the same address as before (http://stream.westin.hamwan.net/) Some notable improvements: 1) Multi-browser support! The old design would only run on Chrome. This redesign should be compatible with all modern browsers, including those on mobile devices. Please let me know what doesn't work, as I'm sure there are some combinations of tech that fail. 2) Audio support! Where the cameras have capabilities, audio is being streamed along with the video. Cameras that don't have microphones stream silent audio. The mic on ptz.haystack appears to be broken as it's buzzing. 3) Better reliability! The new implementation responds to stream / connectivity errors in real-time. The old implementation would wait an hour or more before doing self-heal and bringing video back online. The javascript video player is also resilient to brief problems. It stalls for a bit and then skips forward in time after the problems are gone, all automatically. And just like the old site, all of this is happening without any transcoding that can degrade quality. What you see are the raw camera feeds. The lack of transcoding also means low CPU load, so we can add many more cameras here. Please give this new system a whirl and let me know if there are any problems or missing features that the old system had which are important still. Thanks, --Bart

7 9

FCC Rules
by Jonathan Dorminy 16 Dec '22

16 Dec '22

I am trying to experiment with making a link on the 10 GHz band, the problem is that I think I am trying to do something prohibited by Part 97. On the 2.4 and 5 GHz bands, pulse emissions are allowed, however, they are prohibited on the 10 GHz band, the band I want to use. My question is, is the OFDM modulation used in 802.11n considered pulse, or spread spectrum by the FCC? I have done extensive searching online and I have found conflicting answers. If you can answer this question, I would greatly appreciate it. 73, Jonny Dorminy/KN4LGM

2 1

Client Hardware Recommendation
by Brooke Burdick 03 Dec '22

03 Dec '22

Hello, I would like to connect to the Triangle Mountain site. Please send me your recommendation for client hardware. My home station is located west of Coupeville: 48.23724607340578, -122.75712568687796 Thank you, Brooke Burdick KJ7EMP 425.273.0271

2 1

RouterOS question - PSDR Digest, Vol 117, Issue 1
by Rob Martin 23 Nov '22

23 Nov '22

Thank you for very prompt responses, and two workable suggestions. I appreciate the help. RobK7QJ On Wednesday, November 23, 2022 at 12:00:21 PM PST, psdr-request(a)hamwan.org <psdr-request(a)hamwan.org> wrote: Send PSDR mailing list submissions to psdr(a)hamwan.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.hamwan.net/mailman/listinfo/psdr or, via email, send a message with subject or body 'help' to psdr-request(a)hamwan.org You can reach the person managing the list at psdr-owner(a)hamwan.org When replying, please edit your Subject line so it is more specific than "Re: Contents of PSDR digest..." Today's Topics: 1. RouterOS question (Rob Martin) 2. Re: RouterOS question (Tom Hayward) 3. Re: RouterOS question (Jamie Owens) 4. Re: RouterOS question (Bart Kus) 5. Re: RouterOS question (Stephen Kangas) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Nov 2022 03:00:30 +0000 (UTC) From: Rob Martin <rgmrob(a)yahoo.com> To: Puget Sound Data Ring <psdr(a)hamwan.org> Subject: [HamWAN PSDR] RouterOS question Message-ID: <735986746.3846576.1669172430587(a)mail.yahoo.com> Content-Type: text/plain; charset="utf-8" I am trying to achieve something using RouterOS scripting, and I'm hoping that here I might find the appropriate expertise. >From a script running in a Mikrotik router I wish to pull in a copy of a file from an attached Windows computer. The computer is on the same subnet as the router. By way of illustration: A file called test.xxx exists on a Windows computer in the folder c:\aaa\ I want a copy of this file to appear in the attached router /file list. This copy "event" could be either a push from the computer, or a pull from the router. When using Winbox, this function is achieved easily using "drag and drop", but I need to automate the function. Thanks. RobK7QJ

1 0

RouterOS question
by Rob Martin 23 Nov '22

23 Nov '22

I am trying to achieve something using RouterOS scripting, and I'm hoping that here I might find the appropriate expertise. >From a script running in a Mikrotik router I wish to pull in a copy of a file from an attached Windows computer. The computer is on the same subnet as the router. By way of illustration: A file called test.xxx exists on a Windows computer in the folder c:\aaa\ I want a copy of this file to appear in the attached router /file list. This copy "event" could be either a push from the computer, or a pull from the router. When using Winbox, this function is achieved easily using "drag and drop", but I need to automate the function. Thanks. RobK7QJ

5 4

HF radiated emissions immunity for Mikrotik gear
by Levente Buzás 06 Oct '22

06 Oct '22

Hi everyone, I am reaching out to ask for advice regarding HF radiated emissions immunity for Mikrotik gear. At our HAMWan site, we have three sectors (mANTBox 15s) and two dishes (mANT30PA with BaseBox5) in the vicinity (<10feet) of a multi-kW EIRP HF (10-15-20m) antenna. Since we have installed the HAMWan gear, the HF gear has been offline but I am worried that it will get damaged once we turn things back on. Mikrotik support did not have any information on this. Does anyone have any specs or practical experience to share? Any advice would be much appreciated. Thanks for your time! 73, Levente VA7QF -- Levente Buzas, MASc, EIT Laboratory Manager Propagation Laboratory Department of Electrical and Computer Engineering University of Victoria lbuzas(a)uvic.ca +1.250.818.3937

2 1