- Public - talk.mikrotik.com.au

Re: RDS2216 - switch hardware
by Mike Everest 18 Mar '25

18 Mar '25

😂 How did I miss *that*! Our MT contact was kind enough not to chastise me for not noticing – instead politely gave over the details ; ) I’ll claim ‘elderly’ for the oversight 😏 Cheers! ------------------------------------------------------------------------------------ Why Choose DuxTel for all your MikroTik needs? 10 good reasons: <http://duxtel.com/why_duxtel> http://duxtel.com/why_duxtel ------------------------------------------------------------------------------------ Follow our tweets for news and updates: <http://twitter.com/duxtel> http://twitter.com/duxtel From: Alexander Neilson <alexander(a)neilson.net.nz> Sent: Wednesday, 26 February 2025 10:06 AM To: MikroTik Australia Public List <public(a)talk.mikrotik.com.au> Cc: Mike Everest <mike(a)duxtel.com> Subject: Re: [MT-AU Public] RDS2216 - switch hardware https://mt.lv/rds_pdf I hate when things are missing from the specifications ;) People have to guess then Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz <mailto:alexander@neilson.net.nz> 021 329 681 022 456 2326 On Wed, 26 Feb 2025 at 12:01, Mike Everest via Public <public(a)talk.mikrotik.com.au <mailto:public@talk.mikrotik.com.au> > wrote: Hi folks, I found out today that despite no mention of it in any of the documentation so far, that the new RDS2216 also features the 98DX4310 switch hardware - the same switch chip used in CRS510-8XS-2XQ and CRS504-4XQ models. It means that full VLAN filtering and L3 offloading is supported in this model - it's a full blown router and L3 switch with masses of storage! You can find the hardware specs for the L3HW routing for this chip below: https://help.mikrotik.com/docs/spaces/ROS/pages/62390319/L3+Hardware+Offload ing One of the units arriving next month is already earmarked for our rack downstairs ; ) Cheers! : ) ---------------------------------------------------------------------------- -------- Why Choose DuxTel for all your MikroTik needs? 10 good reasons: <http://duxtel.com/why_duxtel> http://duxtel.com/why_duxtel ---------------------------------------------------------------------------- -------- Follow our tweets for news and updates: <http://twitter.com/duxtel> http://twitter.com/duxtel _______________________________________________ Public mailing list -- public(a)talk.mikrotik.com.au <mailto:public@talk.mikrotik.com.au> To unsubscribe send an email to public-leave(a)talk.mikrotik.com.au <mailto:public-leave@talk.mikrotik.com.au>

5 8

RDS2216 - switch hardware
by Mike Everest 25 Feb '25

25 Feb '25

Hi folks, I found out today that despite no mention of it in any of the documentation so far, that the new RDS2216 also features the 98DX4310 switch hardware - the same switch chip used in CRS510-8XS-2XQ and CRS504-4XQ models. It means that full VLAN filtering and L3 offloading is supported in this model - it's a full blown router and L3 switch with masses of storage! You can find the hardware specs for the L3HW routing for this chip below: https://help.mikrotik.com/docs/spaces/ROS/pages/62390319/L3+Hardware+Offload ing One of the units arriving next month is already earmarked for our rack downstairs ; ) Cheers! : ) ---------------------------------------------------------------------------- -------- Why Choose DuxTel for all your MikroTik needs? 10 good reasons: <http://duxtel.com/why_duxtel> http://duxtel.com/why_duxtel ---------------------------------------------------------------------------- -------- Follow our tweets for news and updates: <http://twitter.com/duxtel> http://twitter.com/duxtel

3 4

WE'RE BACK!!! 🤓
by Mike Everest 19 Dec '24

19 Dec '24

Hello Everyone! Thanks to everyone who reported to us that the MikrotTik-AU mailing list had vanished! We actually knew about it, but had no way of notifying everyone until now! 😃 So, what happened? Short story is that the folks who were running the list wound up their hosting services and shut everything off after migrating their active customers, BUT since there were some staff changes and company restructures along the way, they had ‘forgotten’ about US! 😔 Fortunately, they were able to resume the VM running the list and allowed us to extract the database to resurrect the list on our own VM platform. Thanks to Darren Clissold (DuxTel) for all the hard work patching everything back together again! There are still a few tasks to tidy up (ssl on the web interface etc) but the base mailing list and http://talk.mikrotik.com.au applications are back and running again. Three lists are still available, (public(a)talk.mikrotik.com.au <mailto:public@talk.mikrotik.com.au> , members(a)talk.mikrotik.com.au <mailto:members@talk.mikrotik.com.au> , jobs(a)talk.mikrotik.com.au <mailto:jobs@talk.mikrotik.com.au> ) including all post archives, and WE THINK your settings will be preserved (preferences, names, email, etc) – passwords may or may not be preserved. If not, then password recovery should work. If you encounter any problems, Darren will be pleased to received your reports to listmaster(a)mikrotik.com.au <mailto:listmaster@mikrotik.com.au> Thanks for your patience! Now is the time to re-send all those posts that you tried to send over past few weeks! :-D Cheers, Mike.

1 0

WE'RE BACK!!! 🤓
by mike＠duxtel.com.au 19 Dec '24

19 Dec '24

Hello Everyone! Thanks to everyone who reported to us that the MikrotTik-AU mailing list had vanished! We actually knew about it, but had no way of notifying everyone until now! 😃 So, what happened? Short story is that the folks who were running the list wound up their hosting services and shut everything off after migrating their active customers, BUT since there were some staff changes and company restructures along the way, they had ‘forgotten’ about US! 😔 Fortunately, they were able to resume the VM running the list and allowed us to extract the database to resurrect the list on our own VM platform. Thanks to Darren Clissold (DuxTel) for all the hard work patching everything back together again! There are still a few tasks to tidy up (ssl on the web interface etc) but the base mailing list and http://talk.mikrotik.com.au applications are back and running again. Three lists are still available, (public(a)talk.mikrotik.com.au <mailto:public@talk.mikrotik.com.au> , members(a)talk.mikrotik.com.au <mailto:members@talk.mikrotik.com.au> , jobs(a)talk.mikrotik.com.au <mailto:jobs@talk.mikrotik.com.au> ) including all post archives, and WE THINK your settings will be preserved (preferences, names, email, etc) – passwords may or may not be preserved. If not, then password recovery should work. If you encounter any problems, Darren will be pleased to received your reports to listmaster(a)mikrotik.com.au <mailto:listmaster@mikrotik.com.au> Thanks for your patience! Now is the time to re-send all those posts that you tried to send over past few weeks! :-D Cheers, Mike.

1 0

VDSL Support
by Christopher Hawker 24 Oct '24

24 Oct '24

Hello all, What are people using these days in order to support FTTB/N/C services on Mikrotik routers? I need to throw an NBN service into a site that uses FTTB and as we know the Proscend transceivers aren't around anymore. Unless someone has one laying around they'd be happy to part ways with... Regards, Christopher Hawker

7 8

client separation?
by Karl Auer 22 Oct '24

22 Oct '24

We're seeing something that looks a bit like client separation - a PC can't talk to a printer on the same network (both on wifi, both using the same SSID, both on the same VLAN and same IP network, not necessarily both on the same AP though). How can I check for this on 17.15.1? I'm not really convinced it is this, because *sometimes* we can print. But maybe it's because they are on sometimes on different APs? Any other suggestions about how the network could be the problem would be welcome. Thanks, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer(a)nullarbor.com.au, he/him) work +61 2 64957435 http://www.nullarbor.com.au mobile +61 428 957160 Please feel free to deal with this email during your own working hours.

5 8

A dubious honour
by Mike Everest 07 Oct '24

07 Oct '24

Hi folks! What better reminder to keep those RouterOS patches up to date than a report naming MikroTik devices among the top 'contributors' to the world's largest yet DDoS attack peaking at 3.8 Tbs :-I https://www.bleepingcomputer.com/news/security/cloudflare-blocks-largest-re… Yoiks.

1 0

New KNOT, hAP ac^3, Chateau LTE12 for sale
by Jason Hecker 05 Oct '24

05 Oct '24

Hi, I have listed some new unused Mikrotik devices on eBay. Good prices! KNOT: https://www.ebay.com.au/itm/116347557135 hAPac^3: https://www.ebay.com.au/itm/116347573637 Cheateau: https://www.ebay.com.au/itm/116347594596 Regards, Jason Hecker <https://www.upandrunningtech.com.au>

1 0

rOS v7 suitability for production use
by Luke Thompson 26 Sep '24

26 Sep '24

G'day, I need to get a partial internal network rebuild done, and it seems like a good time to bump the routers up from v6 to v7. Are there any considerations any longer with doing this for production routers? Is BGP now allowed to use multiple cores? The safe option seems to be v6 latest, however it's a good opportunity to make the move up to v7 now that it's matured. :-) Looking forward to hearing your musings, thoughts, experiences and beyond. Cheers, Luke Thompson, CTO The Network Crew P/L E: luke.t(a)tnc.works https://tnc.works

5 9

Soooo, how does one get BFD to come up on ROS 7? :)
by Damien Gardner Jnr 22 Aug '24

22 Aug '24

So, I was off work sick today, have been holding off on upgrading all my 'production' gear to ROS 7 until BFD support was a thing. Supposedly it's now supported, so I upgraded one of my routers (RB1100AHx4). And yeah, BFD does not appear to work :( Asked a few colleagues, and it's working for them. We compared configs, and identical configs basically, just different hardware on the other side. Is there a trick to it? Is it only supported on specific Mikrotik hardware? Or only TO/FROM specific remote hardware? I tried enabling logging (/system logging add prefix=debug topics=bfd), which didn't really add anything.. Remote end is Cisco Nexus Config is basically: /routing bfd configuration add disabled=no interfaces=vlan300_WyongBGP /routing bgp connection add as=65001 connect=yes disabled=no hold-time=6s input.filter=BGP_SAU_TOR_IN_V4 keepalive-time=2s listen=yes local.address=103.235.x.x .role=ebgp name=SAU-TOR-WYONG-V4 output.filter-chain=BGP_SAU_TOR_OUT_V4 \ .network=bgp-networks .no-client-to-client-reflection=yes .redistribute=connected,static,vpn,dhcp remote.address=103.235.x.x/32 .as=64101 .port=179 router-id=103.235.x.x routing-table=main templates=SAU \ use-bfd=yes If I watch the BFD sessions, I'll see it show as 'dead',. and then disappear, then show as dead, then disappear.. Any thoughts? I've set this one to a 6 second hold timer, and halted the other upgrades for now. I've also reset the config and configured from scratch incase it was a v6>v7 upgrade issue, but still the same problem.. Thankyou! -- Damien Gardner Jnr VK2TDG. Dip EE. GradIEAust rendrag(a)rendrag.net - http://www.rendrag.net/ -- We rode on the winds of the rising storm, We ran to the sounds of thunder. We danced among the lightning bolts, and tore the world asunder

4 12