March 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

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

setting a Dynadish 5 as a dhcp client on wlan1 fails
by Steve - WA7PTM 31 Mar '19

31 Mar '19

Is anyone maintaining the https://www.hamwan.org/Standards/Network%20Engineering/Client%20Node%20Conf… web page? The reasons I ask are: • Step 1 will not work as listed as the command is wrong (should be "/system package update install" in RouterOS v6.43.12) and if some preliminary steps are not taken (moving the default network to one connected to the Internet with a "/ip address add address=a.b.c.d/xx interface=ether1" command and establishing a default gateway with a "/ip route add gateway a.b.c.gw" command), then the update will fail. • Step 21 on a Dynadish5 results in a "failure: incompatible band and channel-width" message unless "channel-width=5mhz" is added to the command. • Step 22 on a Dynadish5 results in a "failure: can not run on slave interface" message. This last one has me stumped, and I have been unable to determine a workaround. Has anyone else encountered and solved this problem? Thanks, Steve

4 5

EmComm 5th Saturday - Seattle ACS
by Randy Neals 30 Mar '19

30 Mar '19

Today, Saturday March 30th was a 5th Saturday EmComm exercise across Washington State. The Seattle Auxiliary Comm. Service used this to focus on HamWAN deployments at the Sector level. As background, The City of Seattle has a very nice EOC in downtown Seattle. It has two HamWAN dishes on the roof providing redundant HamWAN backbone connectivity to two different HamWAN cell sites. Seattle ACS is organized in 6 sectors. Central West, Central East, North West, North East South West, and South East. Each sector establishes its own UHF voice net, and operates within the sector like it were a small town. Radio amateurs are dispersed at their homes, or in community emergency hubs (Parks/Community Centers). Today we fielded HamWAN at 5 of the 6 sectors, some using permanently installed HamWAN clients at amateur's homes, and other using field deployable tripods and radios in parks. Each Sector net maintained voice and Winlink connectivity with Seattle EOC, and in turn Seattle EOC maintains communications with King County and the State EOC. We also deployed HamWAN VoIP Phones, and were able to call between the EOC and Sectors by dialing 4 digit extension numbers on the phone. Winlink Telnet over HamWAN is extremely fast. In previous events we have congested our UHF Winllink RMS Gateways. This problem was eliminated with Winlink over Telnet. we also tested sending photos over Winlink with the photo reduced to 100kB size. Randy, W3RWN Seattle

1 0

Re: [HamWAN PSDR] Pacific County sites / planning - input needed
by Rob Salsgiver 20 Mar '19

20 Mar '19

Steve provided some EOC sites to fill in on the map. The below locations have been added. Coverage colors for each peak have been changed to better allow seeing which client locations can be served by different potential cell sites. This should be available on the same map link provided earlier. Let me know if anyone has more to add. Cheers, Rob Locations added: Pacific County EOC Public Safety Building 300 Memorial Drive, South Bend, WA 46.6621, -123.8106 Pacific County Alternate EOC 7013 Sandridge Road, Long Beach, WA 46.3524, -124.0506 (140' tower) Clatsop County EOC (Camp Rilea) 33168 Patriot Way, Warrenton, OR 46.1228, -123.9341 South Seaside (potential cell site) Line of sight to Long Beach EOC tower 45.9527, -123.9385 Wickiup Mtn. (potential cell site) Line of sight to Clatsop EOC 46.1056, -123.5858 Map link: https://caltopo.com/m/UT9N

2 3

Pacific County sites / planning - input needed
by Rob Salsgiver 19 Mar '19

19 Mar '19

Greetings all, Been playing some catch-up as I get ready for MHDC this weekend and was working on some mapping. I laid out some potential routing based on the email chain that was going around. There are a couple of sites that I didn't see GPS coordinates for, so they are left off for the moment. These are Long Beach, North Cove, and Radar Ridge. If someone can get me coordinates for those I can add them to the map. Snapshots of the map are below. They show the primary sites I have coordinates for, and their (combined) expected coverage. Photo 1 (below) shows the basic routing being discussed. Photo 2 below shows the anticipated LOS coverage from these sites. Additional information (GPS coordinates and names) of the EOCs and/or other sites of interest to connect to the system can be placed on the map to show a first-draft of whether they are likely to be in a possibly covered area. Right now it was easier to show total coverage with the same color. Each site can be assigned a separate color to determine which (client) sites would be service by which (cell) sites. It is much easier to distinguish separate colors if the map is zoomed in and not covering such a wide area. Misc Notes: 1) BawFaw/Boistfort - I don't know the geography down there, but when I put the GPS coordinates for Boistfort in, it covered our existing BawFaw site exactly. If these are not in fact the same sites, I need better coordinates to get them split. 2) The URL for you to look at this map directly is: <https://caltopo.com/m/UT9N> https://caltopo.com/m/UT9N. The map is read-only, but you should be able to zoom in and move around. Information requested: 1) If there are additional sites to be considered to establish pathing (Long Beach, North Cove, and Radar Ridge, etc) let me know. I need site name and GPS coordinates (UTM preferred) 2) If you would like to see EOCs or other client sites shown on the map, I can do that as well. Need the same info as above. 3) If you want close-ups with coverage colors changed (example: KO peak as yellow and Megler as red), I can do that as well. Let me know what sites you want to see and I'll set it up. Zooming in with different colors would show for example which uplink site would best serve a given EOC / client site. For the moment I would like to consolidate all of the information so we can all be working off of the same map. I know there are some folks in Portland that this could be helpful to as well, and might bring secondary paths back into Pacific County from down there. Once the map is fairly static I have no problem duplicating it or dumping datasets for others to use. Give me a shout if you have any questions. You can also shoot me info off-list at rob(a)nr3o.com Cheers, Rob Salsgiver - NR3O

1 0

Help with connecting
by Subhro Kar 15 Mar '19

15 Mar '19

Hello, I have recently moved the Lake Stevens and was wondering about signal strength here. Does anyone have spare gear and willing to drive a bit to help a fellow Ham? I will buy you lunch. Thanks -- Subhro Kar System Administrator Working and Playing with FreeBSD since 2002

1 0

Any other ideas on how to experiment with hamwan?
by Chris Prosser 12 Mar '19

12 Mar '19

Hi folks, I was hoping to take some time this summer during my work sabbatical to build a station on hamwan and experiment with it, my idea was to experiment with voice over IP with concurrent downloads/uploads and fq_codel to do traffic shaping and see how a saturated link performed. But I just mapped out my home location and things don't look good. Here's where I'm at: 47°41′5″ N 122°21′48″ W 270ft Looking at Gold Mountain: Distance = 37.889 km (23.543 miles) Azimuth, Point 1 to Point 2: 247.21° True Azimuth, Point 2 to Point 1: 66.86 ° True I'm shielded to the south by Queen Anne, to the east by Phinney Ridge, and when I look out towards Gold Mountain all I see are tree tops and one or two roofs. This is from a third-floor balcony in my townhouse, while I could probably get another 10 feet of elevation on my roof, I'm scared to go on the roof and I'm 90% sure that doesn't give me any line of sight. Am I correct in assuming that I'm pretty much out of luck with my QTH? I'd really prefer to be able to run things from here if at all possible. But if there isn't a creative solution, it looks like I'm going to have to figure out a portable solution. I came across this post documenting a mobile station that someone had built: https://cdine.org/2017-11-19-portable-hamwan-station/ Would the high power version help with range? it's not clear to me which side tends to be the limiter in HamWan. https://mikrotik.com/product/sxtsq_5_high_power Then I need to find a place where I can set up within range and not sit in sun the whole day. Thanks, Chris -- Chris Prosser chris(a)nart.org

3 3

Re: [HamWAN PSDR] Replacing Metal5SHPn modem?
by Rod Johnson 04 Mar '19

04 Mar '19

Kenny, Thank you for the reply. That looks pretty daunting to me. I am not much of a computer guy, and a lot of the terminology looks foreign to me. I tried something like that a year or two ago, and got completely lost; and very frustrated. I could well have also corrupted any files that were still intact. I think I had better just skip the idea of installing the spare modem for now. Maybe when I am bored and have some 'geek' help, I should try it again. Thanks, Rod Johnson -----Original Message----- From: Kenny Richards <richark(a)gmail.com> To: Rod Johnson <we7x(a)aol.com>; Puget Sound Data Ring <psdr(a)hamwan.org> Sent: Mon, Mar 4, 2019 4:12 pm Subject: Re: [HamWAN PSDR] Replacing Metal5SHPn modem? Rod, >Can I just plug in the replacement unit, or is there some programming that will need to be done, for it to be recognized. There is probably some programming that should be done, at the very least you should upgrade the firmware in the modem to the current version if it has been offline for several years. I would recommend going through the client setup guide on the HamWAN site. It is straightforward and takes you through all the current recommended processes. Thanks Kenny http://www.hamwan.org/Standards/Network%20Engineering/Client%20Node%20Confi… On Mon, Mar 4, 2019 at 3:51 PM Rod Johnson via PSDR <psdr(a)hamwan.org> wrote: I have a spare 'Metal 5SHPn' modem, and I am considering replacing the suspect one on my tower. This spare is the original modem that was on my roof, to relay from Baldi to the tower which is part way up the west side of Tiger Mountain. The HamWan on that tower was deactivated as a result of the group moving to a site on top of the mountain. The ham who was using that dish and modem pair was also removed from using HamWan , as a result of the move and deactivation of that tower sector. I took a lightening hit several years ago, and immediately discovered I was not able to connect to Baldi ( the only possible connection route from my location). I found the wall wart POE power supply was fried, and I replaced it, but to no avail, and I have always suspected the modem was damaged in the strike. I have been off-line for several years. Although I have been told the system sees my dish, I have not been able to connect, and I think it might be an issue with the modem. Can I just plug in the replacement unit, or is there some programming that will need to be done, for it to be recognized. Thanks, Rod Johnson Mirrormont _______________________________________________ PSDR mailing list PSDR(a)hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr

1 0

Replacing Metal5SHPn modem?
by Rod Johnson 04 Mar '19

04 Mar '19

I have a spare 'Metal 5SHPn' modem, and I am considering replacing the suspect one on my tower. This spare is the original modem that was on my roof, to relay from Baldi to the tower which is part way up the west side of Tiger Mountain. The HamWan on that tower was deactivated as a result of the group moving to a site on top of the mountain. The ham who was using that dish and modem pair was also removed from using HamWan , as a result of the move and deactivation of that tower sector. I took a lightening hit several years ago, and immediately discovered I was not able to connect to Baldi ( the only possible connection route from my location). I found the wall wart POE power supply was fried, and I replaced it, but to no avail, and I have always suspected the modem was damaged in the strike. I have been off-line for several years. Although I have been told the system sees my dish, I have not been able to connect, and I think it might be an issue with the modem. Can I just plug in the replacement unit, or is there some programming that will need to be done, for it to be recognized. Thanks, Rod Johnson Mirrormont

2 1