This article will focus on MikroTik – we will show you how you can do a network wide mass upgrade of RouterOS using Unimus, and the RouterOS Package Source feature. What’s even better, doing the entire upgrade process (including setup of Unimus and RouterOS Package Source) can be done in under an hour.
MAJOR CHANGES IN v6.45.7:
!) lora – added support for LoRaWAN low-power wide-area network technology for MIPSBE, MMIPS and ARM;
!) package – accept only packages with original filenames (CVE-2019-3976);
!) package – improved package signature verification (CVE-2019-3977);
!) security – fixed improper handling of DNS responses (CVE-2019-3978, CVE-2019-3979);
This was originally posted at:
So Mikrotik has a very cheap hAP Lite coming out. This is a 4 port, 2.4 b/g/n router/access point which retails for $21.95. Baltic networks have pre-orders for $18.95.
Why should you deploy this little gem and how? We have found over the years routers account for more than half of the support issues. In some networks, this number is closer to 80-90%. Whether it be a substandard router, one without of date firmware, or poor placement by the customer.
Deployment of the hAP lite can be approached in one of two ways. Both ways accomplish the same goal for the ISP. That goal is to have a device to test from that closely duplicates what the customer would see. Sure you can run tests from most modern wireless CPE, but it’s not the same as running tests m the customer side of the POE.
Many ISPs are offering a managed router service to their customers. Some charge a nominal monthly fee, while others include it in the service. This is a pretty straightforward thing. The customer DMARC becomes the wireless router. The ISP sets it up, does firmware updates, and generally takes care of it should there be issues. The managed router can be an additional revenue stream in addition to providing a better customer experience. Having a solid router that has been professionally set up by the ISP is a huge benefit to both the provider and the customer. We will get into this a little later.
The second option lends itself better to a product such as an hAP lite. With the relatively cheap cost you can install one as a “modem” if the customer chooses their own router option. The actual method of setup can vary depending on your network philosophy. You can simply bridge all the ports together and pass the data through like a switch. The only difference is you add a “management ip” to the bridge interface on your network. This way you can reach it. Another popular method, especially if you are running PPPoE or other radius methods, is to make the “modem” the PPPoE client. This removes some of the burdens from the wireless CPE onto something a little more powerful. There are definite design considerations and cons for this setup. We will go into those in a future article. But for now, let’s just assume the hAP is just a managed switch you can access.
So what are the benefits of adding one of these cheap devices?
-You can run pings and traceroutes from the device. This is helpful if a customer says they can’t reach a certain web-site.
-Capacity is becoming a larger and larger issue in the connected home. iPads, gaming consoles, TVs, and even appliances are all sharing bandwidth. If you are managing the customer router you can see the number of connected devices and do things like Torch to see what they are doing. If a customer calls and says its slow, being able to tell them that little Billy is downloading 4 megs a second on a device called “Billy’s Xbox” can help a customer. It could also lead to an upsell.
-Wireless issues are another huge benefit. If the customer bought their own router and stuck it in the basement and now their internet is slow you have a couple of tricks to troubleshoot without a truck roll. If the hAP is in bridge mode simply enable the wireless, set up an SSID for the customer to test with and away you go. This could uncover issues in the house, issues with their router, or it might even point to a problem on your side.
-Physical issues and ID10T errors can be quickly diagnosed. If you can’t reach your device it’s either off or a cabling issue. If you can reach the hAP and the port has errors it could be cabling or POE.
These are just a few benefits you can glean from sticking a $20 Mikrotik device on your customer side network. It becomes a troubleshooting tool, which makes it money back if it saves you a single truck roll. The implementation is not as important as having a tool closer to the customer. There are several vendors you can order the hAP lite from. Baltic Networks is close to me so they are my go-to. http://www.balticnetworks.com/mikrotik-hap-lite-tc-2-4ghz-indoor-access-point-tower-case-built-in-1-5dbi-antenna.html .
This isn’t practical for business and Enterprise customers, but you should already be deploying a router that has these features anyway right?
Are you looking to learn Mikrotik in a virtual environment? Check out Vultr.com.
For those of you who may not have seen the Mikrotik 60ghz dishes. Here are some screenshots.
I did an overall video of the New Mikrotik RouterOS v7.
From Mikrotik forum: https://forum.mikrotik.com/viewtopic.php?f=1&t=152003
We have released a very limited test variant of RouterOS v7. Currently only available for ARM systems with a slightly limited feature set.
What is currently unlocked / available:
– Only available for ARM architecture
– Based on Kernel 4.14.131, which is currently the latest and most supported LTS version
– New CLI style, but compatible with the old one for compatibility
– New routing features, but see below
– OpenVPN UDP protocol support
– NTP client and server now in one, rewritten application
– removed individual packages, only bundle and extra packages will remain
Other features not yet public.
What is not available:
– BGP / MPLS disabled
– Extra packages
– Winbox does not show all features, use CLI for most functionality
DO NOT USE IT FOR ANYTHING IMPORTANT, THIS RELEASE IS STRICTLY FOR TESTING AND DOES CONTAIN BUGS
Download link: https://mt.lv/v7
Announced at The Russian MUM
Currently only available for the arm processor. This supports my long running theory on the inability to get the dev tools for the Tilera processor is why v7 has been delayed so much.
More coming soon
Farm progress show 2019. Mikrotik 60 ghz backhauling between WiFi nodes. Wireless wire cluster for high Bandwidth customers. 5ghz for smaller bandwidth customers.