I'm afraid I don't understand your question. Can you clarify?Is this really true? If so, then what stops someone from making a script that changes the identity of some station and cramming the AP with a long list of dummy interfaces?
The SFP+ module could be autonegotiating correctly to 1Gbps in the switch but not the router.But it also doesn't explain the issue where with the switch, it works perfectly fine? The link to the modem is the same in that case but somehow it isn't affected by the issue?
The RB4011 was listed as incompatible with the old MikroTik DACs that have been discontinued. It is however listed as compatible with the new XS+DA0001.RB4011 will not work with a DAC, according to specs...use an AOC instead.
It already does, in RouterOS v7.Hi, will RouterOS support WPA3 in September? That's probably when Apple will release iOS 15 with WPA3 support. So I'm gonna need it by then I assume.
On CAP devices there is generally no need for bridge vlan filtering. Disable bridge vlan filtering and delete the VLANs from bridge->VLANs tab, then all of the VLANs you have created will just work without needing configuration.Is this guide wrong or did something change since it was written?
Did you add the routing table named "via-gw" first? It doesn't let you mark-routing for a routing mark unless that mark matches the name of a routing table defined on the router in v7./ip/firewall/mangle/export doesn't work correctly for mark-routing action.
I'm not sure if this is the cause of your problem, but 10.0.0.0/24 is not a valid address given that subnet mask. You should use something that doesn't end in .255 or .0 for a /24./ip address
add address=10.0.0.0/24 interface=localnet network=10.0.0.0
You can probably write a script to handle the changes for the tunnel automatically in event of an IP change.I tried to leave local IP field empty and set IPsec password at the same time, but this way tunnel doesn't get ready.
I think here you meant to say change installation=indoor to installation=any, not distance=any. distance=indoors is ok for that setting and is the default.Issue appears to be your wireless configuration...
That seems an odd limitation.. I would hope that this is just a temporary state of affairs and that MLAG will support MSTP later.I just tried using MSTP on the Bridge the MLAG ports are on, it definitely does not support that version of STP.
Try setting up a new server with beta 6. There was an issue with beta 4 and earlier, if I recall it was something to do with the partition table format being incorrect. It may be the cause of the issues you are having.Sorry, typed the wrong version number: 7.1 beta 4.
Please see this MUM presentation: https://mum.mikrotik.com/presentations/ ... 667160.pdfA different network operator was able to open up ports from the public for their CGNATted customers using MikroTik, we are not sure how they did it.
Your wireguard interface for roadwarriors should also be in the LAN interface list - make sure you have done that.Unfortunately I cannot replicate it. May you have any hint based on my configuration?
I may be mistaken, but my understanding is that it is only limited to IPv4 for now, and L3 offloading for IPv6 is coming.It's a pity that L3 offloading is limited to IPv4 only, but it's impressive nevertheless.
If it is a bug in 7.1beta5, please note that there is 7.1beta6 available now.Reverting to RouterOS 6.48.2 fixed the issue.
/system default-configuration print
Make sure admin mac address is set for your bridge, and that "Disable IPv6" is not checked under IPv6->Settings.may/23 00:35:32 radvd,debug RADVD:: skip Router Advertisement sending on bridge: no link local address
Which is not something I would consider a major feature. At the moment they mostly have to finish filling in the blanks - all of the minor features, or fixing bugs with the major features.More features are missing like IGMP-proxy
I'm not sure - I haven't actually tried redistributing the default route myself with OSPF on RouterOS 7. Could be a bug, or the feature has not yet been implemented.Is this a bug?
ONT and ONU are two different acronyms for the same thing, so you can't get them backwards. OLT is the term for the head end device (ex. TA5004).Edit - woops - I am getting my ONTs and ONUs backwards - I think.
Can you clarify? I'm not exactly sure what you are asking.Sorry for off-topic, but how do you make these two work together on any ROS release, without wifiwave2?
My Audience is running pretty decently with v7 beta. I would like to try wifiwave2 on it, but need 4 address mode support for that, plus CAPsMAN support.I think the Audience makes a handsome paperweight!
It works fine for me, but I am using the factory default MikroTik IPv6 firewall config and not the one from help.mikrotik.com that you pasted.It appears IPV6 connection tracking does not work on 7.5Beta5?
So what is your reselect-interval set to under channels, as mfrey said? Normally this is solved by setting reselect-interval - I'm not sure if you missed that in mfrey's message or if you tried that but it isn't working.I did start with all channels, but the signal was bad in the kitchen.
OK. Just to clarify in case you were not aware - the RouterBOOT upgrade is separate from the RouterOS upgrade. Upgrading RouterOS itself will not also upgrade the RouterBOOT firmware unless auto upgrade is enabled for RouterBOOT.I did update it yesterday.
Nice catch, missed that. Yes he has the queue priorities backwards.Another thing to realize as I think he has them backwards. Queue priorities are highest..1, to lowest..8. Vs COS/packet highest..7, to lowest..0. He has net control as queue priority 7.
You no longer have any set-priority actions to set the priority to anything other than 0 - that's why you don't see anything.That is strange because I can't see the EXP field changing its value. I made a mirror port on a port going to MPLS cloud and dumped frames with Wireshark:
What cap device are you using and what frequency has it selected on 5GHz?The problem is that the router (the CAPs Manager) is now working with this new CAPsMAN config we came to, but the CAP itself isn't (again, only the 5Ghz network).
On mine this is forbid=no, I think forbid=yes is incorrect. But I'm not sure that is related to your issue here.Code: Select all
/caps-man manager interface set [ find default=yes ] forbid=yes
You shouldn't have this +5570/80/DP(15dBm)Main: 5740/20-Ceee/ac(15dBm)+5570/80/DP(15dBm)
Yes, OSPFv2 and OSPFv3. Obviously I had to change the IP MTU on the far side too. In my case it is a /30 so there was only one other device to change the MTU on to get this working.Do you use OSPF on this interface?
Have you tried using RouterOS instead of SwOS? The switch supports either. RouterOS has more features and may handle this better than SwOS.SWoS v1.11 (Not using v1.12 because it has a bug with 2.5gbps devices)
Use the method shown here instead of simple queues: https://wiki.mikrotik.com/wiki/Manual:C ... h_LimitingPlease help me to control the bandwidth of the clients by IP or by the Interface