<div dir="ltr">Thank you Bart. I took all the step you suggested.<div>Here are this mornings test results. If I was RF into a repeater I'd be ecstatic about these signals, How is it in the HamWan world?</div><div> wireless-protocol: nv2<br> tx-rate: 3.2Mbps-10MHz/1S<br> rx-rate: 3.2Mbps-10MHz/1S<br> ssid: HamWAN<br> bssid: 74:4D:28:57:F6:BA<br> radio-name: Lookout-S2/WA7DEM<br> signal-strength: -64dBm<br> signal-strength-ch0: -66dBm<br> signal-strength-ch1: -68dBm<br> tx-signal-strength: -65dBm<br> tx-signal-strength-ch0: -69dBm<br> tx-signal-strength-ch1: -67dBm<br> noise-floor: -120dBm<br> signal-to-noise: 56dB<br> tx-ccq: 6%<br> rx-ccq: 6%<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 7:46 PM Bart Kus <<a href="mailto:me@bartk.us">me@bartk.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
So, fun fact: you can still use Winbox even if you disable the "/ip
service winbox" service. :)<br>
<br>
Winbox is available as both an IP-routable service (/ip service
winbox), AND as an Ethernet-MAC-level service (/tool mac-server
mac-winbox). Disabling the IP one still leaves the MAC one
accessible, as long as you're on the same Ethernet segment as your
modem. The trick with the GUI is to click the MAC address when
choosing your device, not the IP address.<br>
<br>
It's not intuitive, so maybe this email helps folks out.<br>
<br>
PS: winbox.exe is a huge security risk and we should probably stop
recommending it. It apparently downloads DLLs from the (possibly
exploited) modem and runs them on your Windows machine, with all
your user permissions at its disposal.<br>
<br>
--Bart<br>
<br>
<br>
<div>On 11/1/2019 7:34 PM, Ric Merry wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Thanks Bart! I I ran the client setup page
verbatim and this was the results with the exception of Winbox
and Port222. I wanted to stick with Winbox until I was finished
with the initial setup.
<div>I just received a new computer this afternoon so will move
the whole set up along with all Ham related programs over to
it.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 3:36 PM
Bart Kus <<a href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> 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.<br>
<br>
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:<br>
<br>
[eo@K7ITE-Lookout] > /tool bandwidth-server set
authenticate=no<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
With the bandwidth-server available on your end, I ran a
speed test from the sector to your modem:<br>
<br>
<tt>[eo@Lookout-S2] > /tool bandwidth-test 44.25.143.94
duration=30s direction=transmit</tt><tt><br>
</tt><tt> status: running</tt><tt><br>
</tt><tt> duration: 29s</tt><tt><br>
</tt><tt> tx-current: 38.4Mbps</tt><tt><br>
</tt><tt> tx-10-second-average: 35.6Mbps</tt><tt><br>
</tt><tt> tx-total-average: 37.5Mbps</tt><tt><br>
</tt><tt> random-data: no</tt><tt><br>
</tt><tt> direction: transmit</tt><tt><br>
</tt><tt> tx-size: 1500</tt><tt><br>
</tt><tt> connection-count: 20</tt><tt><br>
</tt><tt> local-cpu-load: 20%</tt><tt><br>
</tt><tt> remote-cpu-load: 28%</tt><tt><br>
</tt><tt><br>
</tt><tt>[eo@Lookout-S2] > /tool bandwidth-test
44.25.143.94 duration=30s direction=receive</tt><tt><br>
</tt><tt> status: running</tt><tt><br>
</tt><tt> duration: 29s</tt><tt><br>
</tt><tt> rx-current: 40.8Mbps</tt><tt><br>
</tt><tt> rx-10-second-average: 41.7Mbps</tt><tt><br>
</tt><tt> rx-total-average: 35.7Mbps</tt><tt><br>
</tt><tt> lost-packets: 1285</tt><tt><br>
</tt><tt> random-data: no</tt><tt><br>
</tt><tt> direction: receive</tt><tt><br>
</tt><tt> rx-size: 1500</tt><tt><br>
</tt><tt> connection-count: 20</tt><tt><br>
</tt><tt> local-cpu-load: 21%</tt><tt><br>
</tt><tt> remote-cpu-load: 27%</tt><tt><br>
</tt><br>
This is the performance you can expect from a 10MHz MIMO
link that has good signal.<br>
<br>
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.<br>
<br>
--Bart<br>
<br>
<br>
<div>On 11/1/2019 3:18 PM, Ric Merry wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">tx-rate: 6.5Mbps-5MHz/2S<br>
rx-rate: 3.2Mbps-5MHz/1S<br>
ssid: HamWAN<br>
bssid: 74:4D:28:57:F6:BA<br>
radio-name: Lookout-S2/WA7DEM<br>
signal-strength: -62dBm<br>
signal-strength-ch0: -64dBm<br>
signal-strength-ch1: -66dBm<br>
tx-signal-strength: -62dBm<br>
tx-signal-strength-ch0: -66dBm<br>
tx-signal-strength-ch1: -64dBm<br>
noise-floor: -124dBm<br>
signal-to-noise: 62dB<br>
tx-ccq: 35%<br>
rx-ccq: 19%<br>
authenticated-clients: 1<br>
current-distance: 32<br>
<div><br>
</div>
<div>Mo' betta? Is current distance miles in both send
and receive (round trip)?</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at
3:06 PM Bart Kus <<a href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> No, you're missing an entire
chain of the radio (ch1). Do this to enable both
chains:<br>
<br>
/interface wireless set 0 rx-chains=0,1
tx-chains=0,1<br>
<br>
--Bart<br>
<br>
<br>
<div>On 11/1/2019 2:55 PM, Ric Merry wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I climbed back up the ladder to do
some fine tuning (thanks for the advice here)
<div>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.</div>
<div>;)</div>
<div>These are my results, I can do more but for
now, how do they look?</div>
<div><br>
</div>
<div>signal-strength: -66dBm<br>
signal-strength-ch0: -66dBm<br>
tx-signal-strength: -67dBm<br>
tx-signal-strength-ch0: -67dBm<br>
tx-signal-strength-ch1: -89dBm<br>
noise-floor: -123dBm<br>
signal-to-noise: 57dB<br>
tx-ccq: 88%<br>
rx-ccq: 70%<br>
authenticated-clients: 1<br>
current-distance: 32<br>
</div>
<div><br>
</div>
<div>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.</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
PSDR mailing list
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a>
<a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div>