IP scope reserved for internal use

rhbirkelund
Kind of a big deal

IP scope reserved for internal use

Today, while modifying a completely different VLAN this error showed up for a dummy vlan of mine:

 

rbnielsen_0-1597314297154.png

I was not able to continue, untill I changed the IP scope of this dummy vlan.

 

Since when has this been a thing?

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
6 REPLIES 6
CptnCrnch
Kind of a big deal
Kind of a big deal

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:

https://tools.ietf.org/html/rfc5737

 

These blocks are not for local use, and the filters may be used in
   both local and public contexts.

 

The block is reserved for testing, I should still be able to configure it on an interface, that is not being used for traffic.
LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.

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.

So one could argue, that it should be allowed. 😉
LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.

>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. 🙂

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels