MikroTik User Meeting (MUM) United States 2017 will be held on May 25-26 Denver

Learned early this week the MikroTik User Meeting (MUM) United States 2017 will be held on May 25-26, Embassy Suites by Hilton Denver Downtown Convention Center, Denver CO.

Registration is already open, register for FREE:

There will be two full days of workshops, product demonstrations, presentations and Exhibition.

Where: Denver CO (USA)
When: Thu-Fri, May 25-26, 2017
Meet and greet: Wednesday, May 24 at 6PM (registration, free beer and soft drinks)

There will be Train-the-Trainer course before MUM on May 22-24. Sign up to become Certified MikroTik Trainer!
More information:

Meet old friends and get new ones – see you in Denver, CO!

MikroTik Team

The post MikroTik User Meeting (MUM) United States 2017 will be held on May 25-26 Denver appeared first on Steve Discher.

Source: Blog

Mikrotik Adds Background Scan for Wireless

I just notice today that beginning with Mikrotik version 6.35, the availability of Background Scan on the wireless interface.  Fro mthe wiki: “The scan command allows you to see available AP’s in the frequency range defined in the scan-list. Using the scan command the interface operation is disabled (wireless link is disconnected during the scan operation). Since RouterOS v6.35 (wireless-rep) background scan is supported which can be used during the wireless interface operation without disconnecting the wireless links. Background scan is supported only using the 802.11 wireless protocol.”

This is a great way to scan for other wireless networks without disrupting the registered clients.  Notice in the screenshot, clients are connected but I am still scanning.  This is a long needed feature.  Thanks Mikrotik!

The post Mikrotik Adds Background Scan for Wireless appeared first on Steve Discher.

Source: Blog

MikroTik dual boot lets you choose between SwOS and RouterOS

Beginning with MikroTik CRS3xx series due this summer, you will have the opportunity to choose which operating system you prefer to use, RouterOS or SwOS. If you prefer to have a simplified switch only OS with more switch specific features, use SwOS. If you are used to Winbox and would like the ability to use routing and other Layer 3 features on some ports in your CRS, you can boot RouterOS. You will be able to select the desired operating system from RouterOS, from SwOS or from the RouterBOOT loader settings.

The post MikroTik dual boot lets you choose between SwOS and RouterOS appeared first on Steve Discher.

Source: Blog

Mimosa Training at ISP Supplies

You’re invited to a Lunch & Learn with Mimosa!

Mimosa and ISP Supplies are on a mission to bring incredible speeds to the wireless ISP market. Please join us for lunch, as we share Mimosa’s vision, updates on Mimosa’s fiber-fast capabilities including backhaul solutions in the 5 and 11 GHz spaces, and an overview of Mimosa’s MicroPop solution.

This event is free!

What Attendees Can Expect

11:30AM – 12:00PM: Check-In (Lunch provided)
12:00PM – 12:15PM: Introductions
12:15PM – 1:30PM: Mimosa Presentation & Demo
1:30PM – 1:45PM: Closing Statements

Important details to add to your calendar:

Learn More

The post Mimosa Training at ISP Supplies appeared first on Steve Discher.

Source: Blog

Using Baicells UE’s with Telrad Base Stations

Will Baicells UE’s work with Telrad eNodeB’s? We have been asked will this work several times and the answer is yes.  We tested this today using a Telrad eNodeB on the EPC2020 and yes it works, with one caveat.  You have to set the MTU down to 1436 to make it work.

This setting is found on the UE “Network->APN Management” page.


  • Telrad eNodeB running 0606.04013
  • EPC 2020 running 0606.00729

Here are some screen shots:

Here is the UE Status:

And finally a speed test:

The post Using Baicells UE’s with Telrad Base Stations appeared first on Steve Discher.
Source: Blog

Cloning MikroTik Routers, Quick and Easy


If you are wanting to configure multiple MikroTik routers with the same configuration, or to copy a config from one router to another, the best way is to use an export.  The export command dumps all of the configuration commands you added to a router to a text file and none of the stuff that gets you in trouble like MAC Addresses .  Then by using the import command, you can apply that set of commands to an unconfigured router.  Issues with this method are often experienced if the target router has any configuration on it to begin with, even the default config, thereby causing the import to fail.

Therefore, I always like to start with a fresh, blank router.  Unfortunately, unconfigured routers can be problematic to connect to via the MAC address for some PC’s.   I have found a better way to accomplish this task.  The following example is from my latest book RouterOS by Example, 2nd Edition:

Step 1 – Creating a Text Export on Router 1

The text export is created from the command line only:

  1. Open a terminal window by clicking the New Terminal button.
  2. At the root prompt, type export file=[your file name here]. Of course, the square brackets are not actually typed, you should be naming your file in that field. Example: export file=myconfig. It is not necessary to specify the file extension. The extension will be added automatically. Producing the export will take 100% CPU for a few seconds but will then produce a file in the Files List.
  3. From there you can drag and drop it to your desktop for renaming and further editing. You can also omit the “files=” portion of the command and it will export the configuration to the terminal window. From there you can copy and paste parts of the file for use elsewhere. Also note that the export is produced relative to the portion of the command tree you are in. For example, from the root of the command tree, you will export the entire configuration. By typing IP address and enter, you will then be inside the IP address menu branch and an export from there will only produce that portion of your configuration.

Step 2 – Upgrade and Import


  • I have reset the router  to the defaults using the reset switch or started with a router out of the box.
  • In my lab, I have a DHCP server and network access that I will connect to the router on ether1.  Since that port has a default config with DHCP client, it will pull an IP and have internet access.
  • I will be using the default configuration which includes a complete base config and I am attaching my laptop with DHCP to ether2.
  • Once everything boots, the laptop should have internet access through the defaulted router.
  1.  Once the router is booted and the laptop has internet access, click System-Packages and the Check for Upgrades button and install any upgrades, router will reboot.
  2. After reboot, drag the script your created on Router1 into the Files list on Router2.  You can even drag from one Winbox Files list to another Winbox window’s files list, or drop it on your laptop desktop in between, your choice.
  3. Next, click System-Reset Configuration, check No Default Configuration and select the script you previously exported:


Click Reset Configuration.

The router will then reboot, erase itself and then import your custom configuration.  This works very well when you have a stack of routers to upgrade and configure.

Have fun and Keep on ‘Tiking!

The post Cloning MikroTik Routers, Quick and Easy appeared first on Steve Discher.
Source: Blog

How FCC Part 15 Rules Will Affect MikroTik Wireless

For operators using MikroTik wireless, careful attention should be payed to the the new series of products being released.  In particular, I am talking about anything with -US in the model number.  I think some background is in order.

The Federal regulations dealing with wireless equipment are found in 47 C.F.R. Ss 15.5(b), referred to as “Part 15”.  802.11 equipment is certified under Part 15.  In April of 2014, the FCC enacted major changes to Part 15 certification as follows:

  • Remove indoor restriction for 5.15-5.25 GHz
  • Modifications to requirements for devices operating in (U-NII-1) 5.25-5.35 GHz and (U-NII-2) 5.47-5.725 GHz with regard to Dynamic Frequency Selection (DFS)
  • The Commission also grandfathered U-NII devices certified under old standards, that are already installed for “the life of the equipment”.
  • Rules were supposed to already be in effect but some parts are still being delayed by manufacturers.
  • More information on Part 15 changes at https://apps.fcc.gov/edocs_public/attachmatch/DA-15-575A1_Rcd.pdf.

The 5GHz band is divided into 4 sections as follows:


Prior to the Part 15 changes, MikroTik devices were ONLY certified in the U-NII-3 band.  They were never certified to operate in the U-NII-1 and U-NII-2 bands, ever.  nothing changes after the Part 15 change, even though they opened up the U-NII-1, MikroTik legacy devices (old Part 15 certified) are not certified there.  Any devices without the -US in the model number are considered “grandfathered” devices and can continue to operate for the life of the device in U-NII-3 only.

Any devices with -US in the model number are certified for U-NII-1 and U-NII-3.  Legacy devices will eventually get re-certified but until then, they are only usable legally in U-NII-3.  There is a “drop dead” date coming, after which, any devices not certified and not yet in service will become international versions, meaning they can not legally be used in the US.

Here are a few FAQ’s that might help:

  • What about legacy equipment certified under old Part 15 with respect to operation on U-NII-1 and U-NII-2 with/without DFS, was it ever certified for those frequencies?

Answer: It was only certified for U-NII-3 band, always has been.  U-NII-1, U-NII-2 were never certified even though U-NII1 & 2 frequencies exist in the Regulatory Domain setting (these are taken from the Atheros chip)!

  • Will new MT devices certified under new Part 15 rules eventually be certified for U-NII-2 with DFS?

Answer: To be determined by MT.

I know this is all a lot to digest so if you have questions about a particular device, please feel free to reach out to me.  Until then, stay legal!

The post How FCC Part 15 Rules Will Affect MikroTik Wireless appeared first on Steve Discher.

Source: Blog

Why LTE? An Explanation Even Your Investors Will Understand

This is a repost of an email from Patrick Leary, President of Bai Cells, North America. Well said Patrick!

Baicells Technologies is offering LTE at a value that blows away the entrenched myths that LTE is too expensive for WISPs and other small operators, such as small towns and cities or verticals like oil & gas that might be interested in LTE for private networks. That’s well and good, and we are proud of accomplishing this once thought impossible feat, but a fair question remains: Why LTE at all? So we’d like to explain the impact of 2 simple issues you may not fully yet appreciate: NLOS challenges and the benefits of a standard. We think once you do, the case for using LTE as your primary wireless access method will be too compelling to ignore.

We hope you do not mind if we explain these things in as layman a way as possible, so you can potentially use these explanations to your investors and customers who might want to understand why you want to upgrade your network to Baicells LTE solutions.

1. NLOS (Non-Line-of-Sight) Challenges
In the license-exempt and lightly-licensed fixed wireless broadband space, operators must live with the modest power limits set by regulators. Whether in the USA, Canada, are anywhere else, regulatory regions require wireless technology in these frequency bands we are permitted to use to operate at greatly reduced power relative to those operators like mobile carriers who hold expensive licensed bands. The reasons for this go back many years, but the crux of the issue is that these bands were never expected to support commercial broadband plays, but rather were expected to be used by all the common indoor and very close range wireless devices that have become pervasive in our lives today, such as Wi-Fi, baby monitors, garage door openers, etc. The exceptions include 3.x GHz bands, but even these are granted very limited output power for fear of interfering with adjacent license band licensees like satcom companies.

Despite this, technologists have been able to make lemonade out of lemons, and now thousands of operators around the world are serving millions of customers around the world – especially in rural areas where choices are few – with community-saving high speed internet. But common technologies like Wi-Fi and its proprietary derivatives can only do so much; Wi-Fi capabilities are modest when it comes to outdoor obstructions like trees. The result is that areas with lovely forests (and even a few trees in a wireless path), while nice to live around have been impossible to service with any kind of broadband speeds today’s streaming users demand.

You see (again, this will be remedial for some of you),
wireless signals weaken over distance – a process called “attenuation.” This attenuation occurs in a step-like manner, where enough attenuation means the signal drops to progressively lower and lower levels, with each level down reducing the ability of the signal to deliver less and less speed (megabits). These levels are called “modulations.” Top modulations might be able to deliver 80 megabits or more, but by the time distance and trees continue to attenuate the signal, one might be in a modulation that can only deliver 1 or 2 Mbps, and eventually nothing at all. With trees in the way, low power signals are both scattered (reflection) and absorbed by leaves, modulating the signal down to useless levels.

In the wireless business we categorize this sort of radio path obstruction as a foliage-related non-line-of-sight problem (NLOS). Tree-based NLOS is the primary reason keeping most WISPs from being able to connect a majority of the customers in their footprint who want their service; it is a massive business problem, not just a technical one. Those who can beat NLOS — or at least deal with it much more effectively — win in the marketplace.

In the wireless world we measure these signal levels in decibels (dB). The way the science works, -3 dB attenuation (loss) means you’ve lost half your power. Conversely, +3 dB (gain) means your power is double. And it’s exponential, so a loss of 6 dB is catastrophic in terms of delivering effective high speed internet. To use an analogy, imagine you are driving down the interstate at 80 mph. If you lost half your power (3dB), you are down to running at 40 mph. Lose another 3 dB (or 6 dB total) and now you are down to 20 mph. So in the wireless world, we might say 80 mph is like 80 dB, but 77 dB is like 40 mph and 74 dB is like 20 mph. That’s not going to get you anywhere fast – and your competitor still driving 80 will crush you in the market if your job is to delivers goods down the highway. And guess what? Your job IS to deliver “goods” down the “highway” – broadband down the information superhighway.

This is where LTE comes in. Unlike Wi-Fi, LTE was designed for outdoor wireless, not indoor wireless local networks. As a more advanced technology designed specifically for outdoors, LTE signals are able to hold higher modulation levels in the face of more foliage. LTE also does a better job of collecting all the various reflections off leaves and still making sense of the signal.

LTE does such a better job in fact that it holds about a 7 dB advantage over Wi-Fi on a per modulation basis — remember that’s more than double and double again. With that massive advantage it can easily cope with foliage-based NLOS that will literally render competitive technologies useless, unable to connect. Baicells LTE lets you deliver much higher speeds to your NLOS-impacted customers where your competitors maybe can’t service them at all. This means many more potential customers for every tower you install.

2. Standards
The NLOS benefits alone are enough to drive most fixed wireless operators delivering broadband commercially to move to LTE if they deal with foliage-based NLOS, but there is another reason why such users should care a lot about LTE: standards. This is also a reason cities and towns, must care about it.

We are all carrying LTE-enabled devices in our purses and pockets. LTE, in just a few short years, has displaced all other old school mobile technologies. When you see that “4G” icon appear on your smart phone, that’s LTE. The mobile operators have invested billions to upgrade their networks to LTE because it gives them much more speed at distances the old 3G methods could deliver.

But that’s not the only reason, the global drive for all mobile carriers to use LTE for its technological advantages also means the entire globe is unifying around a single standard, and with such mass comes economies of scale that result in higher profits and lower costs. It results in more vendor choices, preventing companies from the deadly risk of vendor lock where one vendor holds an operator hostage at the mercy of one company’s limited R&D and customer service. It results in massive continuing investments by all parties to bring new services and build new devices. It’s an explosion in innovation. Just consider the amount of Wi-Fi prompted revolutionary innovations for what and how we can connect things inside just over the space of ½ a generation. We can’t imagine living with it, just ask your kids!

LTE is doing the same for outside and we are only at the beginning of the LTE revolution. Those who get on board now with LTE will be able to take advantage of untold new efficiencies, products, and services that emerge. Over $1 billion is invested annually in LTE R&D, and being standard, every new leap will be backward compatible with the last, just as Wi-Fi has been. Imagine, no more forklift upgrades, or at least you’ll now control your pace – no single vendor can put your entire CAPEX investment at risk of obsolescence on a whim or by its failings in the marketplace.

This also translates into a network with higher equity value. Investors understand the value of standards. Potential competitive buy out opportunities become more plausible with your network being more attractive because of an easier integration.

As well, new spectrum being opened by regulators in the U.S. called the Citizens Broadband Radio Service (CBRS) band (3.55 GHz- 3.7 GHz) will enable even the smallest operators to build their own private networks that can have frequency protection similar to what mobile carriers now enjoy in their licensed spectrum. This includes cities and towns. This is a huge deal because today every city and every town has ever increasing OPEX budgets as they pay the big mobile carriers monthly fees to connect an every-growing list of devices in the communities, from traffic controllers, electronic signs, cameras, plate readers, water plant control valves, and even parking meters. This is part of the “Internet of things” (IoT) phenomenon within a municipal sphere, and while it provides efficiencies and better capabilities, it costs a lot of tax money to pay to connect these things.

The new CBRS band lets cities and towns and oil field operators, etc. the ability to shed these onerous carrier contracts for the first time by allowing them to build their own private, frequency-protected networks. No more carrier contracts. No more ever-expanding monthly fees. Sure, cities could have tried this using Wi-Fi, but that scheme was already tried and failed miserably in the “muni Wi-Fi” boondoggles ten years ago. The band was too shared and too unpredictable. It was also too expensive, requiring base stations every block or so. Now Wi-Fi is back doing what it does best, connecting things in our homes and allowing us to connect best-effort with our smart phones without carrier charges as we drink coffee, shop, etc.

With the CBRS band, no longer will communities that want to connect outdoor devices be at risk of connecting things with cluttered and noisy Wi-Fi spectrum that is being shared by every home and person in town, causing constant interference problems that negatively affects services, and makes it unwise to use for critical operations.

What technology will dominate this space? LTE. LTE will be the pervasive choice in CBRS because of its technical advantages outdoors, its vendor flexibility, its growing set of devices, its backward compatibility, its low cost. Those trying proprietary will find themselves with high cost and limited choices – they would simply be trading one vendor dependency for another.

So friends, Baicells Technologies was created and is staffed by some of the inventors of LTE with a visionary goal of not only making LTE as simple as Wi-Fi, but to democratize the technology in a way that will re-define who can be a carrier. We will bring LTE’s revolutionary NLOS benefits, its economies of scale, and the flexibility of globally-adopted standards to you at price points even the smallest operator – private or public – can afford. Whether your customers are broadband subscribers, taxpayers, or internal customers, the positive results will accrue quickly and progressively, both in customer satisfaction and your bottom lines. Welcome to the Baicells Technologies LTE future; it’s going to be amazing!

The post Why LTE? An Explanation Even Yours Investors Will Understand appeared first on Steve Discher.

Source: Blog

Using rsync to Move UniFi-Video to Different Linux Server

This one caught me by surprise so I wanted to share. I was moving a unifi-video server from one machine to another.  The best way to do this is to first install the unifi-video software using the instructions Ubiquiti provides.  Then, use rsync to copy your old data to the new server.  I used rsync for this but left out one important command line switch, -F.  Ubiquiti uses symbolic links in their directory structure so without -F, it will not copy the linked directories.

The directories you have to copy are:

Default Directory: /usr/lib

any alternate directory where you might have the actual video files stored, in my case /srv/video

The rsync command I use while logged into the new server that gives good performance is

rsync -aHAXxvF --numeric-ids --progress -e "ssh -T -c arcfour -o Compression=no -x" OldServerIP:/var/lib/unifi-video

-F ensures everything makes the trip.

Step by step:

  1. Stop UniFi service on new and old server:
    service unifi-video stop
  2. Use the rsync command above to copy the /var/lib/unifi-video directory
  3. WHen finished, restart UniFi on new server:
     service unifi-video stop

Good luck!

The post Using rsync to Move UniFi-Video to Different Linux Server appeared first on Steve Discher.

Source: Blog