HamWAN client testing
Thanks to those of you who responded to my questions the other day about client equipment. I was chatting separately with Kyle Burgess (KD7IYT), and he offered to bring his mobile KISMET vehicle with 42+ feet mast and HamWAN setup (Mikrotik RB Metal 5SHPn modem) to my home to see which sectors I'd be able to hit. He and Matt (didn't catch Matt's call sign) showed up for a couple of hours of testing. Home location 48.026167N, 122.121500W Marysville WA (If you Google Map it with satellite view, it's the house with the solar panels.) Unfortunately, we could not establish a connection to the Snohomish County DEM (Paine) sector (about ~15 km away). There are apparently too many tall trees in the way or other obstacles. He tried various mountain top sectors, but I can't see the Cascades from my area, so none of those worked either. For grins, he tried the Seattle sectors (~40 km? away), and we got a weak connection. We weren't sure exactly which sector we were hitting (he said there are two it could have been), but we got the Internet and were able to do some tests. Upload/Download speeds were only a bit higher than 0.3 Mbps. (In comparison, Kyle lives about 3 miles from me in Marysville, and can easily hit the Paine sector and get 16 Mbps.) We didn't try Victoria because his modem wasn't set for their frequencies. I'll need to decide whether it's worth it to try to setup a permanent antenna for such a slow speed, but he said 0.3 Mbps would be plenty for VoIP phone calls which could be worth it in emergency situations. It might be fun to just use the connection to experiment with all kinds of things. Thanks to Kyle and Matt for going the extra mile to see what I can hit from my house. We actually had many neighbors come out to see his truck and ask questions while he was there. 73s, B.J. Guillot KI7ZDF
On Sat, Aug 11, 2018 at 1:27 PM B.J. Guillot <bj.guillot@gmail.com> wrote:
For grins, he tried the Seattle sectors (~40 km? away), and we got a weak connection. We weren't sure exactly which sector we were hitting (he said there are two it could have been)
It's pretty simple to see which sector you are connected to. Just issue this command: /interface wireless monitor 0 status: connected-to-ess channel: 5900/5/an wireless-protocol: nv2 tx-rate: 16.2Mbps-5MHz/1S rx-rate: 16.2Mbps-5MHz/1S ssid: HamWAN bssid: E4:8D:8C:F1:6D:22 radio-name: Gold-S2/K7WAN signal-strength: -57dBm signal-strength-ch0: -57dBm tx-signal-strength: -59dBm tx-signal-strength-ch0: -59dBm tx-signal-strength-ch1: -75dBm noise-floor: -120dBm signal-to-noise: 63dB tx-ccq: 93% rx-ccq: 93% authenticated-clients: 1 current-distance: 10 wds-link: no bridge: no routeros-version: 6.41.3 last-ip: 169.48.173.167 current-tx-powers: 6Mbps:31(25/31),9Mbps:31(25/31),12Mbps:31(25/31),18Mbps:31(25/31),24Mbps:31(25/31),36Mbps:29(23/29),48Mbps:29(23/29),54Mbps:27(21/27),HT20-0:29(23/29),HT20-1:29(23/29),HT20-2:29(23/29), HT20-3:29(23/29),HT20-4:29(23/29),HT20-5:27(21/27),HT20-6:27(21/27),HT20-7:26(20/26) notify-external-fdb: no You can see the radio name right there next to the signal strength. If you can tell me your MAC, I can look you up in the logs to see what sector you connected to. Tom KD7LXL
Thanks, Tom. I'll keep that in mind for the next go-around. Here is the MAC we were using during the test: 4C:5E:0C:31:C4:43 It was acting like we were making a connection to the Westin, based on the coordinates that were dialed in. I really wasn't expecting anything from that direction. However, it would be cool to verify if it truly was the Westin that we were passing traffic through. The best RSSI we saw was right around 75. Kyle On Sat, Aug 11, 2018 at 3:11 PM Tom Hayward <tom@tomh.us> wrote:
On Sat, Aug 11, 2018 at 1:27 PM B.J. Guillot <bj.guillot@gmail.com> wrote:
For grins, he tried the Seattle sectors (~40 km? away), and we got a weak connection. We weren't sure exactly which sector we were hitting (he said there are two it could have been)
It's pretty simple to see which sector you are connected to. Just issue this command:
/interface wireless monitor 0 status: connected-to-ess channel: 5900/5/an wireless-protocol: nv2 tx-rate: 16.2Mbps-5MHz/1S rx-rate: 16.2Mbps-5MHz/1S ssid: HamWAN bssid: E4:8D:8C:F1:6D:22 radio-name: Gold-S2/K7WAN signal-strength: -57dBm signal-strength-ch0: -57dBm tx-signal-strength: -59dBm tx-signal-strength-ch0: -59dBm tx-signal-strength-ch1: -75dBm noise-floor: -120dBm signal-to-noise: 63dB tx-ccq: 93% rx-ccq: 93% authenticated-clients: 1 current-distance: 10 wds-link: no bridge: no routeros-version: 6.41.3 last-ip: 169.48.173.167 current-tx-powers: 6Mbps:31(25/31),9Mbps:31(25/31),12Mbps:31(25/31),18Mbps:31(25/31),24Mbps:31(25/31),36Mbps:29(23/29),48Mbps:29(23/29),54Mbps:27(21/27),HT20-0:29(23/29),HT20-1:29(23/29),HT20-2:29(23/29),
HT20-3:29(23/29),HT20-4:29(23/29),HT20-5:27(21/27),HT20-6:27(21/27),HT20-7:26(20/26) notify-external-fdb: no
You can see the radio name right there next to the signal strength.
If you can tell me your MAC, I can look you up in the logs to see what sector you connected to.
Tom KD7LXL _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
My guess is Capitol Park. -Doug- On Sat, Aug 11, 2018 at 4:09 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
Thanks, Tom. I'll keep that in mind for the next go-around. Here is the MAC we were using during the test: 4C:5E:0C:31:C4:43
It was acting like we were making a connection to the Westin, based on the coordinates that were dialed in. I really wasn't expecting anything from that direction. However, it would be cool to verify if it truly was the Westin that we were passing traffic through. The best RSSI we saw was right around 75.
Kyle
On Sat, Aug 11, 2018 at 3:11 PM Tom Hayward <tom@tomh.us> wrote:
On Sat, Aug 11, 2018 at 1:27 PM B.J. Guillot <bj.guillot@gmail.com> wrote:
For grins, he tried the Seattle sectors (~40 km? away), and we got a weak connection. We weren't sure exactly which sector we were hitting (he said there are two it could have been)
It's pretty simple to see which sector you are connected to. Just issue this command:
/interface wireless monitor 0 status: connected-to-ess channel: 5900/5/an wireless-protocol: nv2 tx-rate: 16.2Mbps-5MHz/1S rx-rate: 16.2Mbps-5MHz/1S ssid: HamWAN bssid: E4:8D:8C:F1:6D:22 radio-name: Gold-S2/K7WAN signal-strength: -57dBm signal-strength-ch0: -57dBm tx-signal-strength: -59dBm tx-signal-strength-ch0: -59dBm tx-signal-strength-ch1: -75dBm noise-floor: -120dBm signal-to-noise: 63dB tx-ccq: 93% rx-ccq: 93% authenticated-clients: 1 current-distance: 10 wds-link: no bridge: no routeros-version: 6.41.3 last-ip: 169.48.173.167 current-tx-powers: 6Mbps:31(25/31),9Mbps:31(25/ 31),12Mbps:31(25/31),18Mbps:31(25/31),24Mbps:31(25/31), 36Mbps:29(23/29),48Mbps:29(23/29),54Mbps:27(21/27),HT20-0: 29(23/29),HT20-1:29(23/29),HT20-2:29(23/29), HT20-3:29(23/29),HT20-4:29(23/ 29),HT20-5:27(21/27),HT20-6:27(21/27),HT20-7:26(20/26) notify-external-fdb: no
You can see the radio name right there next to the signal strength.
If you can tell me your MAC, I can look you up in the logs to see what sector you connected to.
Tom KD7LXL _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
On Sat, Aug 11, 2018 at 4:09 PM Kyle Burgess <kd7iyt@gmail.com> wrote:
Thanks, Tom. I'll keep that in mind for the next go-around. Here is the MAC we were using during the test: 4C:5E:0C:31:C4:43
It was acting like we were making a connection to the Westin, based on the coordinates that were dialed in. I really wasn't expecting anything from that direction. However, it would be cool to verify if it truly was the Westin that we were passing traffic through. The best RSSI we saw was right around 75.
There are no HamWAN sectors installed at the Westin, so you would not have been able to accidentally connect to it. Here's what I found for that MAC in the log. Looks like you were able to connect to SnoDEM-S1. 5,1,Aug 10 19:15:39,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:15:41,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info, dhcp1 assigned 44.24.240.155 to 4C:5E:0C:31:C4:43 5,1,Aug 10 19:16:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:16:32,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:17:47,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:18:04,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -82 5,1,Aug 10 19:28:27,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:28:41,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:28:54,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:36:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 20:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info, dhcp1 deassigned 44.24.240.155 from 4C:5E:0C:31:C4:43 Tom
Good to know. I guess I will take the Westin coordinates out of the pointer then. Capitol Park was my next guess beings it would have been somewhat in-line. But, when I pointed it to that site, it definitely couldn't hear it. Based on that log, we were obviously communication with Paine. Is it possible we could have been picking up a reflection of the signal from Paine somehow (bouncing off a building, etc)? The pointer is GPS enabled, so it should have been quite accurate with its heading; especially after I re-ran the calibration. It has always been dead-on in the past, so that's why I question the reflection idea. I tested it a few days prior at another location, which connected to Paine with great accuracy. Thanks for the confirmation. Kyle On Sat, Aug 11, 2018 at 4:23 PM Tom Hayward <tom@tomh.us> wrote:
On Sat, Aug 11, 2018 at 4:09 PM Kyle Burgess <kd7iyt@gmail.com> wrote:
Thanks, Tom. I'll keep that in mind for the next go-around. Here is the MAC we were using during the test: 4C:5E:0C:31:C4:43
It was acting like we were making a connection to the Westin, based on the coordinates that were dialed in. I really wasn't expecting anything from that direction. However, it would be cool to verify if it truly was the Westin that we were passing traffic through. The best RSSI we saw was right around 75.
There are no HamWAN sectors installed at the Westin, so you would not have been able to accidentally connect to it.
Here's what I found for that MAC in the log. Looks like you were able to connect to SnoDEM-S1.
5,1,Aug 10 19:15:39,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:15:41,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info, dhcp1 assigned 44.24.240.155 to 4C:5E:0C:31:C4:43 5,1,Aug 10 19:16:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:16:32,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:17:47,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:18:04,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -82 5,1,Aug 10 19:28:27,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:28:41,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:28:54,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 19:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: connected, signal strength -84 5,1,Aug 10 19:36:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info, 4C:5E:0C:31:C4:43@wlan1: disconnected, control frame timeout 5,1,Aug 10 20:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info, dhcp1 deassigned 44.24.240.155 from 4C:5E:0C:31:C4:43
Tom _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
participants (4)
-
B.J. Guillot -
Doug Kingston -
Kyle Burgess -
Tom Hayward