meanwhile with mikrotik we have a nice GUI to do everything with. I have both mikrotik and edgerouter, and i find the edgerouter very lacking in GUI to configure. It tries to appear nice but it is very very lacking. What isn't lacking is that you can install MIPS debian packages but the limited onboard storage is another matter, though you can actually set up nginx proxy cache if you have limited bandwidth.
The one thing that i use this for is to provide CPU based LACP bonding because i do not want to spend another 40 watts using my 36 core CCR for it

Support at ubiquiti forums are non existant from experience, whereas with mikrotik, litespeed, blesta i can badger their dev teams all i want

This post has been edited by System Error Message: Mar 28 2022, 01:24 AM

i have both since people thought i was a mikrotik fanboy. I'm just not happy with the way that ubiquiti does things and their focus, not to mention at one point they made unfair comparisons using my posts. I remember at one point they made an unfair comparison between what i said was equivalent in hardware, a dual core 800Mhz PPC mikrotik and an ERP3 which at that time was a dual core 800Mhz MIPS too, showing just how much faster the ERP3 was. The unfair comparison was that the ERP3 was not using QoS and was relying on hardware NAT while mikrotik at that time did not have acceleration for NAt, and the speed was someone elses bench on their non standard/non home consumer config.

I would'nt really call the edgerouter a low powered debian server though as 20W is still more than what the raspberry pi uses. The main thing lacking which isn't as easy to find is the block diagram for ubiquiti devices which tells you the internal architecture so that you can best set up the device.

As for the CCR i did actually load it up for fun with traffic generator. Theres a lot that mikrotik provides that actually makes it quite interesting, and its actually useful in hacking, but i did make a tutorial before on the net on silencing and replacing the fans and comparing the noise to the ERPRO including the PSU issues for mikrotik which they did fix in the 2nd generation of CCRs.

Still though a lot of what you can do with edgerouters are best done using SSH like a linux server, so the best tutorial for edgerouter would be how to add debian package repository and to use it like a debian server. You will need to understand the limits though like with the ERPRO the CPU can do 80Mb/s of squid per core as a proxy, so it may do 3x that if using nginx instead. The hardware limits for edgerouters are more that they do well for simpler logic instructions than calculations like ARM, so things like filters should run fast while things like non standard VPN servers or anything heavier including RTMP on nginx may run poorly.

Still, could be worse (cisco)

This post has been edited by System Error Message: Mar 28 2022, 05:30 PM

nah i have a place to vent about ubiquiti. There are some good and bad things and they are not useful everywhere. The issue i have with ubiquiti are
- lacking in network configuration
- lack of community support
- lack of information and proper supplier support
- wrong customer target (they try to target the professional/enterprise user promoting themselves as a cisco alternative but from what i find they fail here too.
- vendor lock in for some of their products

That said they aren't a total loss. Their wifi is good if you want basic functionality and good signal. I do question the use of an edgerouter, i mean i do like having different interesting architectures to work with. The TILERA TILE isn't far from MIPS though it is more capable at running software, comparing from the MIPS that ubiquiti uses, but to me edgerouters have always been a jack of all trades, master of none. They are more useful as a combined router/debian server. For instance why not make a tutorial on setting up nginx proxy cache for web browsing on one that is also a router? Could be very useful for those that use mobile internet. Make sure to have usb storage for this as well.

The only problem is, the use cases i get asked, its extremely rare such use case would be better off with a ubiquiti device. For instance if you wanted a good firewall fortigate has some, but if poor the answer is a linux server, if you wanted the best internet load balancer peplink is the answer, with mikrotik second for the poorer users (not as perfect as peplink). I see mikrotik used a lot by ISPs and coreISPs in their datacenters (i did even work for a coreISP as well and it was fun having the same router as my ISP before (not in malaysia) as their edge router). To me ubiquiti naming is off because mikrotik CCRs make better edgerouters than ubiquiti edgerouters while for core routing CCRs are not used if bgp is needed but i believe for OSPF it is used. Feature level is the reason why cisco is still used for bgp rather than ubiquiti or mikrotik.

I'm just letting you know the details on what to cover for ubiquiti for your tutorials as to what their strengths are rather than their weaknesses.