The process of upgrading RouterOS is very simple and, yet, is still somewhat confusing for some folks.Â I will attempt to detail some of the methods as well as some of the finer nuances here.
In my training classes, I go to great lengths to teach when and why proxy arp is necessary on an interface.Â I have seen (and answered) numerous questions on my mailing lists regarding proxy arp and it seems it is time to create an article that I can just point people to.Â I will focus this article on Mikrotik RouterOS (as many of my articles are), but it should be noted that proxy arp is not unique to Mikrotik.
I would LOVE to hear from those of you who read this blog. Please leave comments for this article expressing your desires for what you’d like to see me include as a tutorial. I can make you no promises that I will be able to write up every idea, but I will try to incorporate some of them.
Also, I’d like to hear from you if you’ve found these tutorials useful. It is often difficult to determine from the traffic logs how useful these tutorials are. If you’ve found my writings useful, let me know. If you think I should spend my time elsewhere, I’d like to hear that opinion as well. (Well, I really DON’T want to hear it, but you are welcome to tell me if that is your opinion. 🙂 ).
At least it is a question I’m often asked about how the Mikrotik Router treats vlan traffic.Â In this article, I will address some of the more common types of configurations and help you to understand exactly where you will, or will not, see a packet that is tagged.
Routed or bridged, there are few back haul radios available that can match the Mikrotik RouterOS software for features, tools, flexibility and cost.Â With features and flexibility comes complexity and confusion.Â I wanted to help dispel some of that confusion with this article.Â You may have lots of choices to make, but most of these choices are relatively simple decisions.Â And so, brave reader, proceed…
Mikrotik has recently added MPLS to their already amazing RouterOS product.Â MPLS offers some really nice options for bridging networks that exist within a single administrative domain.Â But, what can you do if you need to bridge 2 networks that do NOT exist within the same administrative domain?Â This article discusses how to create a bridge using another fairly recent upgrade in RouterOS.Â Read on…
About 2 months ago, I began experimenting with an approach to QOS that mimics much of the functionality of the NetEqualizer (http://www.netequalizer.com) product line.Â As I was experimenting with some various techniques for limiting bandwidth utilization, I realized that the scope of the project I had undertaken was WAY more than I had initially bargained for.Â I dedicated more and more time to this project, however, because I was seeing some real results from my tests.Â While most of my articles here have been tutorial in nature, this one is a little different.Â I have a lot of time invested in my approach to handling QOS on a network and have made this a commercial offering.Â I will attempt to describe some of the functionality in this short article.
There are numerous full duplex options available on the market today when you go looking for wireless devices.Â Most of these devices will cost in the multiple thousands of dollars.Â With NStreme Dual, Mikrotik’s proprietary FDX protocol, you can build a true full duplex link for under $1000.Â This article is a tutorial walkthrough on configuring an NStreme Dual link, along with some helpful hints on how to tweak it.
One major issue facing ISPs today is the difficulty in obtaining sufficient IP space for every customer.Â For many, it’s a matter of cost and for some it is simply a choice to NAT their customers behind their router/firewall.Â For the most part, NAT behaves much better today than in days gone by, but there is one issue that is very problematic for those that choose to NAT their customers.Â There is a significant proliferation of a new generation of trojans that turnsÂ a user’s computer into a menace to the Internet community.Â This new generation of trojans (collectively known as “botnets”) can cause problems for not only the owner, but for other customers of the ISP that chooses to NAT.Â Since a significant number of these botnets are used to send spam all over the internet, we, as service providers, have to find a way to protect our networks from being blacklisted, while still allowing our customers to utilize the internet in a way that does not set too many boundries.Â In this article, I will discuss two approaches to setting these limits which have shown to be both effective AND relatively mantenance free.