Same with beta 9, getting SA query timeouts and roaming fails on a late model iPad Air and a laptop with an AX200 that worked and roamed with no problems on previous versions.The iPad started asking for the password again and it kept being rejected until I forgot the network, powered the iPad off and on and rejoined. Using a 5009 with 2x hAPAX^2. I suspect the “*) wifi-qcom - updated driver;” is the culprit. A bit late in the beta cycle to be dropping in newer drivers.
LOL? Seems not to be easy for MT. add drivers in a testing release: people moan. Exchange drivers in beta (!) release: people moan. Exchange drivers at all: people moan. 
You forgot to add also if they don’t change driver people moan
Mikrotik Audience, wifi, 2.4Ghz reconnects occurring on a regular basis. Strong signal, logs just show reconnecting.
I’ll stick with this for a bit longer for diagnostics.
Currently have an open ticket with support file: SUP-149531
We seem to be having issues with BGP with this version. I really don’t have a baseline to go off of, except 7.14.2 seems to be working.
In one case, I have two ospf advertise default routes from two routers pointed towards a FW. That firewall only shows one default route. Shouldn’t it show both, but then have one that is active and the other that is not??
We have had issues with our bgp filters seem to not either work. Or not show our advertised routes in rout bgp ad print commands..
Just random things when working with new bgp servers. It seems wonky, and doesn’t “act” like we think it should when doing commands. Like I’m not showing advertisements, but the peer is seeing them at times.
route will not show if that router is also originating default route and one of the other two routers selected it as best.
I’m talking about the router that is receiving from two routers sending originate default. It would be the router choosing which one to pick that doesn’t show both routers. Wouldn’t it be an eigrp situation then? Or at least show both defaults and then have picked one in its table??
ehm.. you mean ECMP, it can be but only if the two routes have the same cost (to reach both devices advertising the default).
And yes, you should see at least one of them in the routing table (as long as you do not have another better default from another source, or you are filtering it).
Yes, ECMP lol..
These other two routers are directly connected to the 3 that is getting the defaults from the other two. So, should be the same cost(s) I do see them both in the OSPF LSA table. So, the router is getting both. I just find it odd that the main table doesn’t show both, and that it’s choosing one over the other in there. ie not listing both, and then showing one as active and the other not.. No filters enabled on OSPF.
We still had some weirdness with bgp and the router not showing advertised routes. Or even showing routes in the main table.. So, while I can’t quite prove my “feelings” here. Some things seem weird, and we went back to the stable for a working config.
I’m assuming it is only showing the installed routes in the routing table, OSPF will release the inactive route when it becomes active. Less items in the routing table result in faster speeds.
Sure. But it doesn’t work that way with BGP routes.. so why with OSPF…?
I think Mikrotik can think of ECMP with BGP Also… Which will unlock more possibilities
It can, and shows routes in the main FIB for multiple devices just fine.. It even shows routes for ECMP that aren’t default originates just fine in the proper way as well.. Just not two default originate routes in the main fib properly.. It only shows the one that it picked. So, it gets confusing. You aren’t sure if you are getting both routes until you check LSA’s
I could be wrong…
But ECMP is not a RIB thing, but a FIB thing.
I don’t know what this is like in the MikroTik world, but you can have ECMP even with static routes.
But in general, talking about ECMP without talking about TE, and especially without RSVP, doesn’t make much sense.
Lots of ext4 USB stick container problems with hAP ax³ and 7.14.2 or 7.15beta9, downgrade to 7.13.5 and everything works:
http://forum.mikrotik.com/t/upgrade-to-7-14-1-on-hap-ax3-broke-my-containers/174668/1
Based on TWO reports, why do you say LOTS ?
Besides, you’re cross-posting, you know …
I’m not having any problem with USB stick on ax3 at my parents house. Its some no name 64G stick. Working without a problem on 15beta9.
I can add the third report (not ax3, though) 
And, for what it’s worth, the support has managed to reproduce the problem:
[SUP-149159] At the moment we have been able to replicate the issue you are having, it’s software bug we are working on,
If I read you initial mentioning of this ticket number correctly, the behavior is different.
In your case, the device randomly reboots.
In the case of burn3r and LOTS of others, the USB stick simply gets corrupt and unusable anymore.
Any chance we could please fix DHCP snooping please?
CRS devices (CRS112-8P-4S, CRS328-24P-4S+, CRS326-24G-2S+ and CRS354-4S±2Q+) drop DHCP requests when we enable dhcp snooping and there are VLANs configured. Yes, the ‘trusted=yes’ is correct set on the uplink port.
Herewith a summary of the switch configuration:
https://imgur.com/a/4aYzTtY
Herewith the export from 7.14.2:
/interface bridge
add admin-mac=78:9A:18:3D:26:5F auto-mac=no dhcp-snooping=yes name=bridge priority=0x7000 vlan-filtering=yes
/interface bridge port
add bpdu-guard=yes bridge=bridge interface=ether1 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether2 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether3 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether4 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether5 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether6 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether7 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether8 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether9 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether10 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether11 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether12 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether13 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether14 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether15 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether16 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether17 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether18 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether19 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether20 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether21 pvid=17 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=ether22 pvid=17 restricted-role=yes
add bridge=bridge interface=ether23 pvid=25 restricted-role=yes
add bridge=bridge interface=ether24 pvid=25 restricted-role=yes
add bridge=bridge interface=sfp-sfpplus1 trusted=yes
add bpdu-guard=yes bridge=bridge interface=sfp-sfpplus2 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=sfp-sfpplus3 restricted-role=yes
add bpdu-guard=yes bridge=bridge interface=sfp-sfpplus4 restricted-role=yes
/interface bridge vlan
add bridge=bridge tagged="bridge,ether1,ether2,ether3,ether4,ether7,ether8,ether9,ether10,ether11,ether12,ether13,ether14,ether15,ether16,ether17,eth\
er18,ether19,ether20,ether21,ether22,sfp-sfpplus1" vlan-ids=14
add bridge=bridge tagged=bridge,sfp-sfpplus1 vlan-ids=17
add bridge=bridge tagged=bridge,sfp-sfpplus1 vlan-ids=25
add bridge=bridge tagged=bridge,sfp-sfpplus1 vlan-ids=31
add bridge=bridge tagged=bridge,ether5,ether6,sfp-sfpplus1 vlan-ids=100
add bridge=bridge tagged=bridge,ether5,ether6,sfp-sfpplus1 vlan-ids=101
add bridge=bridge tagged=bridge,ether5,ether6,sfp-sfpplus1 vlan-ids=102
add bridge=bridge tagged=bridge,ether5,ether6,sfp-sfpplus1 vlan-ids=666
add bridge=bridge tagged=bridge,ether5,ether6,sfp-sfpplus1 vlan-ids=667
/ip neighbor discovery-settings
set lldp-med-net-policy-vlan=14