My Customer has a test environment with an AP MR33 and an Aruba RADIUS server to perform 802.1x authentication to wireless clients. RADIUS server is in the same local LAN with MR33 and can be reachable from MR33's LAN IP.  And there is no splash page enable. When testing this RADIUS, I got a message that the AP is failed to connect. I can confirm that the share secret is correctly configured and the AP's LAN IP has been added in client list in Aruba. Also I've tried packets capturing in AP's wired interface and I can see AP has sent out access-request to RADIUS and received access-reject from it. In the captured access-request packet I find an AVP nas-ip-address with a value 6.148.146.85, which is neither the meraki cloud IP nor the AP's LAN IP.  Did anybody meet this before? I'd like to verify some questions below:   1. Where does this public IP address come from? or why it appears in nas-ip-address? 2. Is it the cause that makes RADIUS reject AP's access? ... View more