BartoszP, thank you. but i have found out today that capsman is not the cause of the problem. we have all wlans and virtualAPs as dynamic bridge ports on capsman and all caps. i have two CRS-326 connected through ether2-3. on both i reset config and disable all interfaces except for ether1-3, then c...

..."bridge port received packet with own address as source address" You have two routes/interfaces for packets received by this bridge. I have noticed something similar configuring CAPSMAN with CAP's device WiFi interface assigned staticaly to "locally-forwarded" CAP's bridge in...

It's fixed now. I set the switch to static aggregation or whatever the hp equivalent term for cisco's etherchannel is. The bond interface works in balance-rr and there are no mac errors. Also I removed the bogus macs that I've previously set on mikrotik. To others, please be advised that bridge and...

hello, have a problem with this release. we have two CRS-326 connected together through 4 ether ports, both have same configuration: 4 connecting ether ports are bound into a bonding that bonding is part of a bridge before upgrade (6.40.5), everything worked fine. but after upgrade to 6.41, both CRS...

adblock-dns.rsc adblock-addrlist.rsc Is this lists updated Daily or how often.? this list is not updated at all, the author refers to it as a "list of immortal malware/ad sites". if you want updated list with currently active malwares/ads, use this: also created an updatable lightweight v...

also created an updatable lightweight version of it (13.5k entries ATM). it uses the http://winhelp2002.mvps.org/hosts.txt file.

Has anyone implemented this: https://github.com/aziraphale/routeros-dns-adblock yes i have. i used this repo to create a list with almost 52k entries. it does it's job well. but be aware, that the implementation as DNS static entries takes shitload of RAM (cca 200 MB), so it cannot be used on mtiks...

fasttrack is indeed a cool feature, but it's current implementation is confusing and misleading. it also breaks the "normal" rule behavior. when you place a "fasttrack connection" rule in your fw, then packets matched with this rule may or may not be fasttracked. that means, not ...

fasttrack is indeed a cool feature, but it's current implementation is confusing and misleading. it also breaks the "normal" rule behavior. when you place a "fasttrack connection" rule in your fw, then packets matched with this rule may or may not be fasttracked. that means, not ...