October 2018 - PSDR - mailman.hamwan.org

HamWan 900 MHz
by Stan 23 May '19

23 May '19

if this is up and running, I'd sure like to buy a 900 Mhz modem and get the HamWan a bit farther into Mason County. Any suggestions? -- Stan KF7LTT Spams/Scams Forwarded To WA State Attorney For Prosecution.

12 21

CapitolPark <-> QueenAnne link
by Bart Kus 19 Apr '19

19 Apr '19

After hours of debugging, I got this 20MHz single-polarity link moving up to 55Mbit. A high resolution spectrum analysis on both sides did indeed show a better frequency to use for the link. Spectrum analysis captures here: https://imgur.com/a/4H7GB There was also an IP conflict between two modems @ Capitol Park. The conflicting IP has been removed from CapitolPark-S3. The QueenAnne modem used for the link is not one used anywhere else on the network. It's a very low-end modem, and as a result it was having CPU/RAM starvation issues when running our regular diagnostic tools, which lead to out-of-memory conditions and kernel crashes. A different test methodology had to be used to verify the link speed (testing through the modem, instead of to the modem). The modem that links QueenAnne with the Westin building (on the QueenAnne side) had a mis-configured OSPF router-id. This was fixed. I'm still seeing weird routing decisions being made by OSPF. These are triggered by our point-to-point route entries (44.24.242.0/24 space). More research needs to be done here, and perhaps a re-write of how we define point-to-point interface addresses. Any OSPF experts in the house? I also discovered R1.QueenAnne was still vulnerable to hacking due to a mis-configuration of its control software. It missed the updates that were sent out to the whole network. This has been fixed now. R1.QueenAnne also didn't have the diagnostic bandwidth-server setup correctly. This was fixed. With the CapitolPark-QueenAnne link performing well now: [eo@CapitolPark-QueenAnne] /system resource> /tool bandwidth-test 44.24.241.81 direction=both status: running duration: 57s tx-current: 28.0Mbps tx-10-second-average: 28.4Mbps tx-total-average: 27.5Mbps rx-current: 27.6Mbps rx-10-second-average: 28.0Mbps rx-total-average: 27.0Mbps lost-packets: 288 random-data: no direction: both tx-size: 1500 rx-size: 1500 its OSPF config has been reset to a normal preference level, so that packets no longer try to avoid that link as they are routed through the network. This link can be sped up by upgrading to a dual-polarity modem @ CapitolPark. While testing if the OSPF hop cost was being calculated correctly in the Beacon-Haystack-QueenAnne RF link (they both connect to the same dish @ Haystack), I discovered a mis-config on the Haystack.Beacon modem (bad LAN IP binding) which was preventing it from bringing up OSPF on its LAN interface. This was fixed and that modem should act like an actual router now, moving traffic. During the same Beacon testing, I was reminded that our Baldi-Beacon RF link sucks <https://monitoring.hamwan.net/cacti/graph.php?action=view&local_graph_id=91…>. It was optimized for speed to Tukwila, which is now gone, so a trip needs to be scheduled to Baldi to rotate the dish a few degrees north and get that link going strong. I normally wouldn't send this kind of verbose email to psdr@, but I hope it's illuminating as to the type and extent of work required to keep this network running well. --Bart

4 6

Oregon and Washington HamWAN
by Scott J. Burrows 30 Oct '18

30 Oct '18

Hello, I'm curious, do the PSDR folks in Seattle have a plan for integrating both Oregon and Washington into their existing HamWAN network? I have talked to folks within Washington State about their costing estimates and deployment strategies of their HamWAN initiative. The proposed effort discussed deploying HamWAN technology both for the Northern and Southern routes of the state. Earlier this month, the Clark County ARES/RACES group submitted a "2019 Grant Request Proposal" to the Clark Regional Emergency Service Agency to build out a prototype client station at the county EOC. Also, the folks in Oregon have secured a large grant (possibly $30,000 dollar) for HamWAN and will be discussing HamWAN deployments this year. They are organizing teams for fund raising, network administration, site installation, mentorship, and strategic planning. Much of the talk in the IRC group has been about technical suggestions for minor technical problems. I have not encountered any serious discussions about large implementation efforts in expanding the HamWAN network, although perhaps that is occurring via another method. The Memphis, Tampa Bay, and British Columbia seem to be small regional implementations in distant states/provinces. However, I have not seen any serious discussions about statewide strategic and tactical implementations of HamWAN (i.e. Washington and Oregon). In my experience, technology folks get fixated on the nuts-and-bolts of the network technology and forget about strategic leadership, management, and formal documentation. Much of the PSDR website has not been updated in years. I regularly hear comments at digital meetings where folks are interested in HamWAN, but are waiting for more specific information. This makes large scale deployments extremely difficult if you have to email the HamWAN Network Operations folks every day, assuming they have time to respond. I understand that the HamWAN folks in Seattle are busy with day jobs and unable to respond immediately to all questions. However, if the PSDR leadership team was to reach out to the larger audience, I am sure they will find many talented folks to help with most aspect of HamWAN. Hopefully this message will not be considered slamming the HamWAN folks in Seattle. Please don't shoot the messenger. The technical folks (Tom Hayward and Nigel Vander Houwen) have been extremely responsive and helpful. I respect the vision and work that PSDR volunteers have done to date. If you talk to your customer base, you might be surprised the help you may get. Thanks Scott, N7DOD

5 6

Puget Sound Project Status update (sites)
by Rob Salsgiver 28 Oct '18

28 Oct '18

Back on 8/21 I sent out a request for info regarding the following sites that were discussed earlier this year: 1. Lookout Mtn 2. Gold Mtn 3. Buck Mtn 4. Rattlesnake Ridge 5. Blyn Mtn 6. Added since initial email: a. Mt Constitution b. Gig Harbor c. SnoCo SERS Granite Falls (possible – next year candidate) To date I’ve only received responses for the following locations: 1. Buck Mtn – in process w/Kenny. (info in other threads) 2. Gig Harbor – time TBD, not weather critical (Kenny) 3. Rattlesnake – Any day now. Priority project for DMR support before the weather changes. Being coordinated between Rob Ghatham AF7PR and Tom for tech support. Equipment funded by Rob AF7PR. Climber needed. 4. Lookout – Weather limiting by end of October? Rob Chatham AF7PR is the site contact. Rob S willing to coordinate. Equipment BOM in review between Bart and Scott Honaker. SnoDEM potential assistance with hardware (hoops exist to jump through). This site has significant regional improvements it could offer into Skagit/Whatcom/Island counties. Ready immediately per Rob AF7PR but we have to schedule the timing and resources. I’m working to schedule a site visit to survey. Need to know from others what PTP links we are looking to do here and develop BOM. I have received no information regarding Blynn or Gold, and have very little on Constitution. Given the short remaining season and available help, I recommend we hold Blynn until next year. What remains for Gold? CLIMBERS NEEDED. We are extremely limited for climbers at this time. Our existing climbers have been tapped for time, particularly as they have also been “on the hook” for building/configuring the equipment as well. I am willing to build and configure equipment (others are welcome as well). We MAY be able to get short windows from our current climbers if the rest is done, but we really need MORE climbers. Let me know if anyone is willing to do the climbing work, whether you are certified and/or have your own gear. If you have any additional info on the above projects, please let me know. At a minimum I would like to see us get Rattlesnake, Lookout, and Buck done in the next 30 days before the snow flies. There are other low-elevation projects to keep us busy this winter. Thanks, Rob Salsgiver – NR3O

4 7

Client node
by B.J. Guillot 28 Oct '18

28 Oct '18

In between the rain this weekend, I did some more testing with HamWAN from my home in Marysville. My "test stand": * MikroTik RB912UAG5HPnDOT * Altelix AD5G30M2 antenna kit * 10 foot mast on a small 3 foot tripod, from deck of backyard I was able to get a connection (do some pings, visit some http sites), but it was a bit intermittent with the wind swaying the dish on the mast. If I decide to mount permanently, I'll need to find a way to attach the top part of the mast near the house to minimize the movement. Best results were: [admin@N7CS] > /interface wireless scan 0 Flags: A - active, P - privacy, R - routeros-network, N - nstreme, T - tdma, W - wds, B - bridge ADDRESS SSID CHANNEL SIG NF SNR RADIO-NAME ROUTEROS-VERSION A RT B 64:D1:54:95:C4:7F HamWAN 5920/5/an -71 -124 53 K7WAN/SnoDEM-S1 A RT B 64:D1:54:6A:65:A8 HamWAN 5900/5/an -83 -123 40 K7WAN/SnoDEM-S2 -- [Q quit|D dump|C-z pause] As the wind would blow, the SIG numbers would jump into the -90's for a moment and then come back. Ping times to google.com were between 90-500+ ms. I'll keep doing some experiments with different placements to see if I can get an improved signal when I can find a sunny weekend. In the meantime, just wanted to say thanks to the all the people that have been answering my questions over the past few months. Regards, Burt J. Guillot, N7CS

3 3

Technical info about hamwan
by Ron van Herk 23 Oct '18

23 Oct '18

Hi, My name is Ron and I work with Cybermedia Television BV of The Netherlands. I am intrigued by the system you have set up and wonder if I could talk to anyone about, as I have some questions about the setup… Would it be best to chat on the irc channel? Best regards, Ron Cybermedia Television BV Elandstraat 108 2901 BK Capelle aan den Ijssel The Netherlands Phone: +31-(0)10 30 700 21 Mobile: +31-(0)6 143 272 35 Skype : ronaht The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. This email is for discussion purposes only and doesn’t not represent binding arrangement unless expressly stated therein. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. CyberMedia Television BV cannot accept liability for any errors or omissions in the contents of this message, which may arise as a result of e-mail transmission. Please note that CyberMedia Television BV may monitor, analyse and archive email traffic, data and the content of email for the purposes of security, legal compliance and staff training. CyberMedia Television BV is a limited company registered in the Netherlands with Company Registration No. 63937093.Registered Office: Elandstraat 108 , 2901 BK Capelle aan den Ijssel , The Netherlands

3 4

Haystack SDR unreachable for 3 days
by David Haworth 03 Oct '18

03 Oct '18

Hi, Haystack SDR was working fine last weekend. http://www.stargazing.net/david/sdr/HamWAN.html#P1d <http://www.stargazing.net/david/sdr/HamWAN.html#P1d> For the past three days Haystack SDR This site can’t be reached http://44.24.241.55:8073/ is unreachable. Has Haystack SDR URL changed? 73 David WA9ONY

4 3