I wouldn't use LACP with links of different characteristics. It can be a nightmare.
It's better to configure them in an active/passive fashion with the 5G link acting as a backup and forwarding packets only if the 60G link fails.
I imaginedThese fixes will be included in upcoming v6.44.Using the stable releases (6.43.12 included) I can't establish a link. With 6.44 betas and rc it works, it just needs to set the interface to 1 Gbps
Anyway management interfaces, be it Winbox, APIs, ssh, web and whatnot should never be exposed without proper filtering. So the version display is harmless in my opinion.security by obscurity
Great job. Now a single Btest can saturate a w60 linkPlease read carefully through change log:
*) btest - added multithreading support for both UDP and TCP tests;
Great These links are almost as good as a fiber.Thank you very much, I did not know this method to measure the speed, but from now on I will do it that way.
I was much calmer when I saw the results of the test.
Tx = 994Mbs
Rx = 998Mbs
Multiple reflections can be a problem I guess.We found that the installation location is more important than one would assume on a building or roof (was expecting the narrow beam pattern to do the work)
How did you reduce power?
A silly or not so silly idea. What about coating the reflector with a hydrophobic material such as Teflon (PTFE)?Please keep in mind that stated 1.5km range is with including weather factors.
They do on 6.43rc. IF-MIB::ifSpeed shows the PHY rate. Before 6.43 it showed 10 Mbps.Can the phy-rate and RSSI for 60G interfaces also be exposed over SNMP please?