MikroTik Train-The-Trainer: routers used by experts?

[@rchrstphr-smp1043]

My first mikrotik device was hap lite TC. Now I have hap ax lite, RB750gr3 , MAP (recently bought - it's was not shipping yet) and later I would like try CRS310(version 2.5g ports plus 2SFPS)

[@leonardogyn]

Great memories when that guy mentioned the RB450, which were also my first Mikrotik devices, later being replaced by RB450Gs and several others. Awesome video! And cheers from Brazil for all of you, great seeing a Brazilian guy on the video as well :) Parabéns Diego!

[@tiagoabelha6471]

Grande Diego, Parabéns!!!!!!

[@jonathancolby9179]

What a cool event! I run an entire business in San Diego on Mikrotik. Thank you Mikrotik !!! You are like the Santa Clause Jesus of Technology. Don’t ever stop being the way you are… your like How America is supposed to be For the People, By the People… in technology, you are the people’s champion !!

[@cceste]

great to see you there Thomas !

[@iamyulianto2]

Greetings also from Indonesia! at 4:23 proud of you mr. At-thoriq our trainer from IDN 🤓👍

[@DiegoBarrios]

Good to see you guys!!! Great time among friend there.

[@PekPiu]

Well, with Mikrotik (ROS 7.15) you still can't have fast-track IPv6 connections (eg with existing connection, forwarding a packet thru a router, what Mikrotik incorrectly calls routing). With a HEX-S, speedtest to IPv4 target gives the full 1000/1000 Mbps (the fast-track, hardware based IPv4-forwarding works fine nicely). If speedtest is done to an IPv6 enabled server, one gets about 260/260 Mbps, and the HEX-S CPU is at 100%. This is due to RouterOS not supporting fast track on IPv6, eg hardware based forwarding with the device switch chip. With IPv6, all traffic, every packet, will go via the device CPU, and that is how it has very poor performance. This has forced me to take out over a hundred installations of HEX-S, and other Mikrotik hardware, throw those into the "obsolete crappy devices" bin, and bought non-Mikrotik hardware to replace those. That is not fun, but customers do require that also very normal native IPv6 traffic must pass a router faster than the measly 26% of the link capacity. Using the HEX-S for those customer setups, was a big mistake. Mikrotik has been promising fast-track support for IPv6 for years, but it is again very evident that Mikrotik does not use IPv6 (outside of their labs), and Mikrotik still does not care about IPv6. Mikrotik also does not allow static IPV6 neighbor configuration, kinda-like a static ARP entry for IPV4. It seems Mikrotik does not know or care too much about IPv6, and it still seems Mikrotik is not using IPv6 themselves, outside of their labs. If they did, they would have noticed these issues from the start. My native IPv6 connections have been up and running for 25+ years, and the RouterOS IPv6 forwarding performance has been crappy, from the first RouterOS 3 release. This crappy-IPv6 is clearly a planned strategy by Mikrotik, and only way to avoid it now, is to use routers from other vendors. I will loose a lot of features/flexibility, but for those simple CPE-setups will run very nicely, and wirespeed, with other non-Mikrotik hardware.

[@Grmreeper100]

Lol Could see that Owen was South African even befor he started speaking

[@owenwessels8772]

How did you know? Lol!

[@peter-johnjansen9472]

@@owenwessels8772 Us Saffas have a certain look :P

[@vids5384]

​@@owenwessels8772i'm also south African, started with same device as starter, loving the flexibility of the devices... which training centre was this recorded?

[@gerusadasilva2917]

👏👏👏👏👏👏