I’m not sure what you mean here. I used a skin to remove Quickset from webfig and it disappears in winbox too so it is not possible to use quickset in winbox. You are experiencing different behaviour?Only fully removing QuickSet works in webfig, but it does not work in winbox.
This isn't correct. IPv6 is working with wireguard for me with rc6 even without a link local. What doesn't work over wireguard is OSPFv3.With latest releases the Wireguard interfaces do not have link local addresses. This IPv6 is completely broken with Wireguard at the moment.
I had someone else confirm it works on CHR but is broken on all of the hardware routers. It still should not be green on the v7 Routing Protocol Status page if it only works on CHR and nothing else.VPLS is working very stable for me in 7.1rc6 on CHR. Running with PCIe pass-thru of Intel NIC's
/routing table add disabled=no fib name=to_ether1
I believe you can do this now in v7 with webfig skins, as they work in winbox. I'm not sure if this works with the MikroTik app yet though.PLEASE ADD THE OPPORTUNITY TO DISABLE QUICKSET,
Yes, it works fine after a reboot. OSPFv3 still comes up as before.Does that last across a reboot? Its the initial detection of the interfaces BEFORE they are added to the OSPFv3 instance as interfaces that seems to be the issue.
You have to also manually define "vpn" as a routing table in v7 otherwise it will not work, it is a new feature:ros 7 beta 6 , still have problem
/routing table add disabled=no fib name=vpn
How many bridges do you have? I see your bridge is called BR1, do you have a BR2?There are 2 switch groups, SW1 (ether1-5), SW2 (ether6-10)
We have netinstalled over 600 hap ac3 units on port 1.I need 100% certainty. I tried all ports and nothing happens !!!
Who used netinstall on port 1?
Can’t you just netinstall the device to recover it? Others were reporting that that was working.Unless you can instruct distributors to accept free returns/swaps of bricked hardware for swap for the duration?
I agree - changing something like the RSTP setting should not result in getting a new prefix from the pool.
/interface/bridge/set [find where name=bridge] protocol-mode=none
I doubt it is the feature you (and me as well) are wanting. The RADIUS not recording prefix delegation is not a bug, it is the lack of a feature.What exactly is Fixed... Is it the issue with Radius not Recording PD.????
He does not need that route since he has the IP address on the wireguard interface. If he removes the IP from the wireguard interface as you say then he would need that route.YES you absolutely need this route.
If the peer is an android phone that will move around in a Roadwarrior fashion, you should not be setting the endpoint-port for it./interface wireguard peers
add allowed-address=10.20.50.2/32 endpoint-port=13231 interface=wgmt \
It has been replaced by the XS+31LC10D.Are you releasing a new OEM optic for 10G SMF or? What is the suggested optic to use now?
As a workaround, you can use queue trees with the parent set to the LAN and WAN interfaces, rather than simple queues. I've been running this since earlier betas with fq_codel with both IPv4 and IPv6 traffic and had no issues.This problem isn't new, also had it in 7.1rc3
Protected routerboot seems to be gone from Winbox but still present in the CLI.looks like the protected routerboot option is gone from hAP ac3 LTE6 and RB4011
That is a typo/omission - it should say v7.1rc2, not 7RC2. There is no such thing as v7.0rc2.What is this then:
Yes, this workaround should still work fine in v7.Do you know if it works in v7? If so i wan't to look if we can upgrade 2 of the 3 CCR2004 who are acting as a PPPoE server with OSPF.
6.x does not support /31 addresses either. If they release it, it will be a brand new feature in 7.x.I wan't to but on the routing status page it stills says /31 adress not supported, that we really need unfortunately.
I had a similar issue on my RB4011 upgrading to 7.1rc1, what I wound up doing to upgrade was to reset to no-default-configuration so that it was completely blank and use mac winbox to upload 7.1rc1. You could give that a try on your 2011.It seems I'm stuck with 7.1beta6 now on that device!
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.