- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MX Concentrator had a public IP to get to local status page...?
We have an MX105 concentrator for our sites, we were doing nessus scans and were getting results for RFC 1918 addresses that dont exist in any of our subnets (nor were they found on client list)...
Looking at the nessus trace route for one of these bogus addresses, we would see the final hop would be a public IP address... we had no idea what it was, but after doing a port scan i found out it was a meraki device. I entered the public IP into my web browser and it went to the local status page of our concentrator. (only accessible internally and not externally)
That IP has no meaning to our organization. If anyone can provide insight as to why our concentrator is using this public IP address that would be appreciated.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was it a 6.x.x.x address?
"When in Passthrough or Routed/NAT mode in Single LAN the MX will source traffic from a 6.X.X.X address for services such as Syslog, Netflow, RADIUS access requests and potentially others."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was it a 6.x.x.x address?
"When in Passthrough or Routed/NAT mode in Single LAN the MX will source traffic from a 6.X.X.X address for services such as Syslog, Netflow, RADIUS access requests and potentially others."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In your environment it might be more appropriate to disable the local status page (you'll need to make this decision).
