[HamWAN PSDR] Ok, my numbers

Scott Currie scott.d.currie at gmail.com
Sun Nov 3 08:57:22 PST 2019


I am still seeing slow TX speeds when I run the test from the client end.
Am I doing something wrong? Wrong IP?

/tool bandwidth-test 44.24.240.197 duration=30s direction=transmit
                status: running
              duration: 29s
            tx-current: 11.9kbps
  tx-10-second-average: 11.9kbps
      tx-total-average: 41.1kbps
           random-data: no
             direction: transmit
               tx-size: 1500
      connection-count: 20
        local-cpu-load: 4%

[ns7c at WA7AUB-Baldi] > /tool bandwidth-test 44.24.240.197 duration=30s
direction=receive
                status: running
              duration: 29s
            rx-current: 13.1Mbps
  rx-10-second-average: 14.4Mbps
      rx-total-average: 13.4Mbps
          lost-packets: 1439
           random-data: no
             direction: receive
               rx-size: 1500
      connection-count: 20
        local-cpu-load: 12%

On Sat, Nov 2, 2019 at 9:41 AM Tom Hayward <tom at tomh.us> wrote:

> His speeds look fine today.
>
> [tom at Baldi-S3] > /ip dhcp-server lease print
>
> Flags: *X* - disabled, *R* - radius, *D* - dynamic, *B* - blocked
>
> * #   ADDRESS
> MAC-ADDRESS       HOST-NAME                           SERVER
>             RATE-LIMIT                           STATUS *
>
>  0 *D* 44.24.240.252                                                      64:D1:54:AD:8C:13
> W7CLO-Baldi                         dhcp1
>                                 bound
>
>  1 *D* 44.24.240.251                                                      CC:2D:E0:1E:DE:C7
> WA7AUB-Baldi                        dhcp1
>                                 bound
>
> [tom at Baldi-S3] > /in wi registration-table print
>
> * # INTERFACE
>                                               RADIO-NAME       MAC-ADDRESS
>       AP  SIGNAL-STRENGTH TX-RATE UPTIME              *
>
>  0 wlan1-gateway
>                                               W7CLO/Enumcla...
> 64:D1:54:AD:8C:13 no  -70dBm          29.2... 13h34m40s
>
>  1 wlan1-gateway
>                                               WA7AUB/Auburn...
> CC:2D:E0:1E:DE:C7 no  -73dBm          29.2... 13h34m40s
>
> [tom at Baldi-S3] > /tool bandwidth-test  44.24.240.251 duration=10
>
>                 status: done testing
>
>               duration: 10s
>
>             rx-current: 14.8Mbps
>
>   rx-10-second-average: 14.0Mbps
>
>       rx-total-average: 14.0Mbps
>
>           lost-packets: 0
>
>            random-data: no
>
>              direction: receive
>
>                rx-size: 1500
>
>
> [tom at Baldi-S3] > /tool bandwidth-test  44.24.240.251 duration=10 direction
> =transmit
>
>                 status: done testing
>
>               duration: 11s
>
>             tx-current: 14.2Mbps
>
>   tx-10-second-average: 12.8Mbps
>
>       tx-total-average: 12.8Mbps
>
>            random-data: no
>
>              direction: transmit
>
>                tx-size: 1500
>
>
>
> On Sat, Nov 2, 2019 at 8:31 AM Bart Kus <me at bartk.us> wrote:
>
>> If it's a pre-wired unit like the DynaDish 5, you can't change
>> polarities.  Will just need to live with the confusion.
>>
>> That is pretty bad upload performance.  It could use some spectral
>> analysis on the HamWAN side, and perhaps testing with another client on the
>> same sector to find the cause.  I hope it wasn't caused by the 10MHz
>> bandwidth change!
>>
>> I don't have time to address this right now, so hopefully someone else
>> can step in.
>>
>> The download numbers look fine though.
>>
>> --Bart
>>
>>
>> On 11/1/2019 8:22 PM, Scott Currie wrote:
>>
>> So, it's not clear to me how to change the polarity on the channels. I'll
>> do some reading. It's a DynaDish 5.
>>
>> These numbers look low, I may not be doing this right:
>>
>> /tool bandwidth-test 44.24.240.197 duration=30s direction=transmit
>>                 status: running
>>               duration: 29s
>>             tx-current: 11.9kbps
>>   tx-10-second-average: 11.9kbps
>>       tx-total-average: 25.7kbps
>>            random-data: no
>>              direction: transmit
>>                tx-size: 1500
>>       connection-count: 20
>>         local-cpu-load: 4%
>>
>>  /tool bandwidth-test 44.24.240.197 duration=30s direction=receive
>>                 status: running
>>               duration: 29s
>>             rx-current: 12.8Mbps
>>   rx-10-second-average: 12.2Mbps
>>       rx-total-average: 12.0Mbps
>>           lost-packets: 1192
>>            random-data: no
>>              direction: receive
>>                rx-size: 1500
>>       connection-count: 20
>>         local-cpu-load: 16%
>>
>> -Scott
>>
>> On Fri, Nov 1, 2019 at 8:06 PM Bart Kus <me at bartk.us> wrote:
>>
>>> It appears you're connected to the Baldi site.  That's probably the only
>>> site remaining that still doesn't have MIMO (2-chainz) modems.  It only
>>> provides service with horizontally polarized signals.
>>>
>>> It looks like your modem's setup to receive HPol on ch1.  HamWAN
>>> typically suggests HPol be wired to ch0, and all our network gear follows
>>> that standard:
>>>
>>>
>>> http://hamwan.org/Standards/Component%20Engineering/Client%20Hardware.html
>>>
>>> It makes troubleshooting easier when there's a clear polarity-to-chain
>>> mapping.
>>>
>>> I'm also not sure why we're still running that sector at 5MHz bandwidth,
>>> it should be 10MHz.  I've gone ahead and updated the sector's config to be
>>> 10MHz.  This should provide you with a bit more speed, at the cost of 3dB
>>> of signal power, which you can afford given your -66dBm link.
>>>
>>> Feel free to run some bandwidth-tests to Baldi-S3.hamwan.net
>>> (44.24.240.197) to confirm performance.
>>>
>>> PS: The "tx-signal-strength-ch0" is reported back to you from Baldi-S3
>>> (how well it hears you), since Baldi-S3 only has a ch0, even though that's
>>> not your tx-ch0, but rather your tx-ch1 that it's measuring.  You see how
>>> confusing things get when polarities are flipped?  :)
>>>
>>> --Bart
>>>
>>>
>>> On 11/1/2019 7:46 PM, Scott Currie wrote:
>>>
>>> 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
>>> --
>>> Sent from my mobile device...
>>>
>>> _______________________________________________
>>> PSDR mailing listPSDR at hamwan.orghttp://mail.hamwan.net/mailman/listinfo/psdr
>>>
>>>
>>>
>>
>> --
>> *-Scott*
>>
>>
>> _______________________________________________
>> 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/20191103/171fec46/attachment.html>


More information about the PSDR mailing list