April 2019 - 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

(no subject)
by Doug Collinge 06 May '19

06 May '19

I want to join HamWAN so I checked into the recommended hardware, the MikroTik RBMetal5SHPn. It is no longer available from my supplier and seems to have been discontinued by the manufacturer. My supplier recommended the MikroTik RBMetalG-52SHPacn as a replacement. The RBMetal5SHPn seems to be very well suited to the application. Should I make an effort to find remaindered stock? The RBMetalG-52SHPacn is slightly more expensive but would also be good, if it works. I have heard rumours... Should I expect this unit to work? Does anyone out there have experience with it? MikroTik also has a line of "Groove" weatherproof routers. Is any one of these suitable? Lower cost but also lower transmit power. I'm in Victoria, if that is somehow relevant. No issues with getting the "international" versions, anyway!

9 11

Equipment question
by Bob Sampson 29 Apr '19

29 Apr '19

Good evening, What equipment is typically used to go from HAMWAN digital or IP to the analog input/output audio/cor/ptt of a collocated ham repeater? Bob Sampson k6mby(a)olypen.com 360-477-0776 (cell)

2 1

Not on the map
by Scott Currie 24 Apr '19

24 Apr '19

I notice that my client station is not on the map, nor visible on the tree view off Baldi on the monitoring site. I am connected, so I am wondering if I have something configured wrong. -- *-Scott, NS7C*

2 1

Bill of Materials for Cell Site
by Jamie Hughes 24 Apr '19

24 Apr '19

Good Morning, The Kitsap Auxiliary Radio Service (KARS), DEM affiliate organization, would like to investigate the deployment possibility of a low altitude ring between sites, yet to be identified. The idea would be to build out a few cell sites just at lower altitudes that hopefully create a backup/redundant data ring if possible. If this is possible and authorized, may I please get a bill of materials and approximate cost of those materials. Thanks, Jamie Hughes WA7JH Mobile: (360) 340-8886<tel:+13603408886>

5 4

IP Phones
by Scott Currie 24 Apr '19

24 Apr '19

Hello World.... I'm working on getting the Auburn EOC up on HamWAN. I have a DynaDish in a portable configuration running, which will become more permanent in the next few weeks. Loads of fun sticking a dish out the side door of the EOC and getting 3 bars off Baldi! Next questions, how does one go about setting up an IP phone and getting a number? Also, I have a SIP application on my iPhone (Bria) and so I am wondering if I can get a number for it as well. Can someone enlighten me? -- *-Scott, NS7C* [image: image.png]

6 9

EOCs on HamWAN
by Scott Currie 23 Apr '19

23 Apr '19

All-- Is there a list anywhere of EOCs that are either connected, or have plans to connect to the network? If not, can EOC folks respond back and I will start a list? -- *-Scott, NS7C*

8 9

VOIP Phones
by Dan Dimick SR. 23 Apr '19

23 Apr '19

I've have great interest in the entire project, unfortunately I live in Pacific county and it will be a while before we will be on board. Can we bring our EOC's on board with VOIP phones and use our existing ip facilities and convert them to Hamwan when it becomes available? -- *Dan Dimick Sr* Riding the elevator for fun sure has it's ups and downs!

4 3

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

Network-y stuff.
by Mark Weisenfeld 15 Apr '19

15 Apr '19

I am K7TUM and I am a member of the Capitol Peak Repeater Gp. (NOT Capitol Park) Jeremy, on the board, and chief tech, asked me to cfg the VHF APRS digi/iGate that is to be installed on the peak. We are nearing completion of the equipment setup. It is operating from my QTH with the coord.s of the peak. *Question:* We are delighted to use the HAMWAN Internet access already, for such things a s remote management, Echolink, and IP phone for Auto patch. However, Jeremy is not a network/IP tech, so he needs some help. He has never known how to ask for a static IP address, or a DHCP reservation for any of the equipment up there. BUT I CAN. We would like to put up this APRS iGate, but we need to be able to telnet to it AND view the web interface for management. How would we go about securing a stable address for that device? Can you give me one, or do you prefer I give you the MAC address, or maybe there is NAT at play and we need to "play" with it s'more. What do you prefer? Thanks y'all. -- ****************************************** Mark Weisenfeld K7TUM CN87na <http://www.levinecentral.com/ham/grid_square.php?Grid=CN87na> (SW corner) **************************

4 4