Update:  lab tested and found that the BGP learned routes were not redistributed. Called support; there is an NFO that can be applied to enable IBGP > OSPF redistribuiton. Confirmed working in lab MX68 OSPF to 3750. In this case, our branch MX is configured as a NAT Mode Hub (not spoke); it has full mesh tunnels to all the DC One-Armed concentrators, which are BGP peered to DC core router. ... View more

Hi All, Does anyone know whether a branch NAT-Mode MX will advertise routes (to its OSPF neighbour) which originated in the data centre from a concentrator's BGP neighbour? The documentation around this lacks detail ... View more

Not 100% aligned to your issue, though I also have had issues when enabling 'Mandatory DHCP'. In my case it was on an SSID which uses L3 Roaming (noting that yours is 'Bridge to LAN'). In my case all WAPs are MR52 running 26.8.1.  WPA2-Enterprise SSID, ClearPass RADIUS, using AP Tags for client VLAN assignment. Disabling Mandatory DHCP fixed the issue. (Note, I'm not using VLAN Override via Group Policy in this case, though am for other use cases on the same SSID). Client roams between WAPs with the same VLAN present (eg, WAPs on a given floor) were fine, however once the client roamed to another floor (WAP with a different VLAN), a L3 Roam occurs and the client loses all connectivity. This is because the 'roamed to' WAP didn't see the DHCP Request, therefore drops all client traffic. I spent time troubleshooting this with support, and in the end was told this is expected behaviour. Unfortunately this is not mentioned anywhere (that I have found), so hopefully Meraki will either update the doco, or prevent the feature being enabled for an SSID with L3 Roaming enabled (which aligns with how other feature incompatibilities are handled in dash)...  IMO they should fix this as it is a good security feature, particularly liked by enterprise security folks... ... View more