I guess that‘s a thing since RFC5737 (perhaps even since RFC1166) came out which declared 192.0.2.0/24 as reserved IP space:
These blocks are not for local use, and the filters may be used in both local and public contexts.
Strcitly speaking, it's reserved for documentation (see the RFC). 😉
One could argue if Meraki is simply following standards / RFCs or if you should be able to use it (and violate the RFC). On the other hand I don't think that the forums will help you further with this question.
>Well, it's Cisco best practice to use 192.0.2.1 as virtual ip for web authentication.
No, I don't think that is the case. They merely use it in their documentation - you know - the block reserved for documentation.
I hear ya...Cisco WLC != Cisco Meraki AP though. 😉
Guess we'll see many other interesting facts if the discussion continues, but as already written: I don't think this will bring you further with that request to be allowed to use that. 😉
I don't know, possibly Meraki is really using this space (because it's reserved) for some kind of internal stuff. At least I'd be really curious to get some deeper insight into that. 🙂