@OGM do all of the APs have full IP reachability with one another, or are the perhaps firewalls or ACLs separating the subnets of the AP's management IP addresses?  I also have the same question as @PhilipDAth if you only have a few APs is there any reason they're not running in Bridge Mode?  Using distributed layer 3 roaming may not really apply here, and is sometimes selected because it sounds like the right thing to do (the naming convention makes DL3R sound more robust or elegant or secure than "Bridge" mode). Perhaps you can simply select Bridge mode.   Anyway, I asked about IP reachability because with DL3R the APs will communicate with one another to establish anchor APs and maintain the L3 connections as the users roam across different L3 boundaries.  There's a good support doc on the best practices here: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices and https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Seamless_Roaming_with_MR_Access_Points   Here's a good doc below on the different addressing modes.  For example if you had multiple buildings on a campus and you have a VLAN-per-building type approach, then bridge mode might be perfect if users can simply be bridged back to the VLAN for whatever building they're in,  So you walk out of one building, your wireless connection obviously drops as you walk across campus, and then reconnects in another building, same SSID, different bridge-mode VLAN, and all is fine.  Now, if you had completely seamless coverage including outside from building to building and there's a requirement to maintain the client's original IP on an anchor AP, then DL3R might be the choice.  I'm leaving out details and oversimplifying a little but you get the idea. https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/SSID_Modes_for_Client_IP_Assignment   ... View more