i am completely new to Mikrotik and need an advice on which router to take for SoHo use.
What the router should include is:
-) WAN port
-) At least 7 ports (some gigabit ports should be available)
-) WLAN (2,4 and preferrably 5GHz)
-) VPN server
-) "The Dude" server should run on it
As far as i have seen, the following two devices come closest to the specs:
RB2011UiAS-2HnD-IN
CRS109-8G-1S-2HnD-IN
However, che CRS109 is in the switch cathegory? Can it be used as classic router?
Can anybody please give me a hint on what device best suits my needs?
Thank you
I would have wanted “the dude” for 24h monitoring and logging of my PtP link.
However, i don’t wanna spend extra money for that feature.
Is there another solution to monitor Mikrotik Devices? (SNMP…)
I would like to run that tool on the mikrotik router that is always on anyway.
That heavily depends on what “poor” means for you.
CRS109 features a router on board with processing power roughly identical to the RB951G and RB2011 series, which is not that bad at all.
I think i’ll go with the CRS109-8G-1S-2HnD-IN.
Although i’ll use VPN from time to time, i prefere having the 8 gigabit ports over the split solution of the RB2011 with the CPU as bottleneck in between.
Hope that IKEv2 will be available soon
Well, that “poor” is of course relative. That is what the trainer explained in my MTCWE course, that if you want to use the router function heavily, you should use the CCR, instead of CRS.
I guess he meant 400 (four hundred) Mbps. I have 100Mbps WAN connection at home and RB951G (which is roughly as powerful as RB2011 series boards are) copes with it just fine even without fastpath/fasttrack.
yes without fast-track because firewall filtering, mangle marking and queue tree are in heavy use:
41 filtering rules (a few using an adress-list of 1000 items)
8 nat rules
159 mangle rules (marking traffic for use in queue tree)
26 queues on queue tree
It’s usually a matter of configuration optimization; 40 Mbps sounds like way too little for RB2011 even with complex configuration (and I’m, of course, NOT talking about things like IPsec here, since crypto will definitely be slow).
Putting rules in the right order, with the one accepting established,related on top, should speed things up significantly. The number of NAT rules is less important, since they are evaluated once per connection lifetime anyways.
That number of mangle rules may be a serious bottleneck, indeed. Marking connection first, then marking packets based on the connection mark (thus reducing the number of rules being process per packet) may be a solution. Also Simple Queues are officially recommended over the Queue Trees since RouterOS v6 due to performance reason, especially if the number of queues is high. Thousands of Simple Queues must in general be much much cheaper (in terms of performance) than hundreds of Queue Trees.