- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subnet 192.0.2.0/24
Whatever Meraki is doing with this, it really should be documented.
(Configuring an IP from "TEST-NET-2" was ok for the MX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well you aren't supposed to use test net addressing in your customer networks, so perhaps they saw it fit to use those in their internals so they would never conflict with RFC1918 addresses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, it is not a customer network. It is 100% its intended use: preparing a new chapter in a training course.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Strictly speaking, it is reserved for documentation (see the RFC).
One could argue whether Meraki is simply following the standards/RFCs or whether you should be able to use it (and violate the RFC). To be honest,I don't think the forums will help you with this issue.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, I think the "Documentation Feedback" forum is the right place to ask that something gets documented when a device does something specific.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wonder if it actually is as it says - and is used internally.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The most likely usage is some kind of internal traffic redirection. I really would like to know.
