[HamWAN PSDR] optimization first results

[Scott Currie]

So, should I be concerned about my ch0 numbers?

-Scott

[ns7c at WA7AUB-Baldi] > /interface wireless monitor 0
                  status: connected-to-ess
                 channel: 5880/5/an
       wireless-protocol: nv2
                 tx-rate: 6.5Mbps-5MHz/1S
                 rx-rate: 13Mbps-5MHz/1S
                    ssid: HamWAN
                   bssid: D4:CA:6D:7A:A3:EF
              radio-name: N7FSP/Baldi-S3
         signal-strength: -66dBm
     signal-strength-ch0: -90dBm
     signal-strength-ch1: -66dBm
      tx-signal-strength: -67dBm
  tx-signal-strength-ch0: -67dBm
             noise-floor: -101dBm
         signal-to-noise: 35dB
                  tx-ccq: 47%
                  rx-ccq: 79%
   authenticated-clients: 1
        current-distance: 31
                wds-link: no
                  bridge: no
        routeros-version: 6.41.3

On Fri, Nov 1, 2019 at 3:36 PM Bart Kus <me at bartk.us> wrote:

> Yes, much better.  I also noticed a problem on the HamWAN side, where that
> sector was configured for only 5MHz service instead of our normal 10MHz.
> I've changed the sector config, and you should be getting twice the
> bandwidth now.
>
> I tried to run a speed test, but noticed your bandwidth-server was still
> set to require authentication, so I've logged into your modem and turned
> that off:
>
> [eo at K7ITE-Lookout] > /tool bandwidth-server set authenticate=no
>
> I also noticed you still have an "admin" account.  If it's not properly
> password protected, this may be dangerous now that your modem is on the
> Internet.  I have left it untouched.
>
> I also noticed you have the "winbox" service running.  This is also
> dangerous, as it's full of exploits.  I have left it untouched, but you
> should probably disable it.  (/ip service disable winbox)  We should update
> the website instructions to disable this by default.
>
> I also noticed your ssh is on port 22.  This will get more hacking
> attempts than port 222.  You can change it with /ip service set ssh
> port=222.
>
> With the bandwidth-server available on your end, I ran a speed test from
> the sector to your modem:
>
> [eo at Lookout-S2] > /tool bandwidth-test 44.25.143.94 duration=30s
> direction=transmit
>                 status: running
>               duration: 29s
>             tx-current: 38.4Mbps
>   tx-10-second-average: 35.6Mbps
>       tx-total-average: 37.5Mbps
>            random-data: no
>              direction: transmit
>                tx-size: 1500
>       connection-count: 20
>         local-cpu-load: 20%
>        remote-cpu-load: 28%
>
> [eo at Lookout-S2] > /tool bandwidth-test 44.25.143.94 duration=30s
> direction=receive
>                 status: running
>               duration: 29s
>             rx-current: 40.8Mbps
>   rx-10-second-average: 41.7Mbps
>       rx-total-average: 35.7Mbps
>           lost-packets: 1285
>            random-data: no
>              direction: receive
>                rx-size: 1500
>       connection-count: 20
>         local-cpu-load: 21%
>        remote-cpu-load: 27%
>
> This is the performance you can expect from a 10MHz MIMO link that has
> good signal.
>
> The current-distance is reported in km, not miles.  It's not round-trip
> distance, just physical distance between the modems.  There is a separate
> metric for round-trip-time, which is measured in microseconds:
> tdma-timing-offset=202.  You can do the speed-of-light math to get a more
> precise distance than the 1km granularity reported by the
> "current-distance" field.
>
> --Bart
>
>
> On 11/1/2019 3:18 PM, Ric Merry wrote:
>
> tx-rate: 6.5Mbps-5MHz/2S
>                  rx-rate: 3.2Mbps-5MHz/1S
>                     ssid: HamWAN
>                    bssid: 74:4D:28:57:F6:BA
>               radio-name: Lookout-S2/WA7DEM
>          signal-strength: -62dBm
>      signal-strength-ch0: -64dBm
>      signal-strength-ch1: -66dBm
>       tx-signal-strength: -62dBm
>   tx-signal-strength-ch0: -66dBm
>   tx-signal-strength-ch1: -64dBm
>              noise-floor: -124dBm
>          signal-to-noise: 62dB
>                   tx-ccq: 35%
>                   rx-ccq: 19%
>    authenticated-clients: 1
>         current-distance: 32
>
> Mo' betta? Is current distance miles in both send and receive (round trip)?
>
> On Fri, Nov 1, 2019 at 3:06 PM Bart Kus <me at bartk.us> wrote:
>
>> No, you're missing an entire chain of the radio (ch1).  Do this to enable
>> both chains:
>>
>> /interface wireless set 0 rx-chains=0,1 tx-chains=0,1
>>
>> --Bart
>>
>>
>> On 11/1/2019 2:55 PM, Ric Merry wrote:
>>
>> I climbed back up the ladder to do some fine tuning (thanks for the
>> advice here)
>> Luckily I could remotely view my computer with my cell phone thus saving
>> me the cost of a divorce attorney had I asked my wife to help me when she
>> gets home from work.
>> ;)
>> These are my results, I can do more but for now, how do they look?
>>
>> signal-strength: -66dBm
>>      signal-strength-ch0: -66dBm
>>       tx-signal-strength: -67dBm
>>   tx-signal-strength-ch0: -67dBm
>>   tx-signal-strength-ch1: -89dBm
>>              noise-floor: -123dBm
>>          signal-to-noise: 57dB
>>                   tx-ccq: 88%
>>                   rx-ccq: 70%
>>    authenticated-clients: 1
>>         current-distance: 32
>>
>> Funny things is that thee are about where I started. Elevation is the
>> more difficult adjustment with the brackets provided. I may end up
>> modifying those.
>>
>> _______________________________________________
>> PSDR mailing listPSDR at hamwan.orghttp://mail.hamwan.net/mailman/listinfo/psdr
>>
>>
>>
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.net/mailman/listinfo/psdr
>


-- 
*-Scott*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20191101/5438bcdb/attachment.html>