Getting Public Addresses on Corporate LAN/Wifi

LandmarkSupport
Just browsing

Getting Public Addresses on Corporate LAN/Wifi

Greetings all!!

 

I have an issue I cannot seem to solve nor can my Spectrum provided Meraki support. For a while now I have one site where devices are receiving public addresses. Sometimes the public IP of the MX!! Ive checked NAT and nothing there. I've checked any forwarding rules...nothing there.

 

Support INSISTS it's someone playing a joke on me and hardcoding static addresses...but I know that's not the case. It will happen on wifi and LAN. Heck I just got onsite today and tried to get on the corporate WiFi and lo and behold I was given a public IP address. 

 

We have 2 Meraki APs and they go direct into the last two ports on our MX 68. 

 

I checked a user's laptop yesterday who was unable to hardwire and his IP was a public one but oddly enough the network name Windows gave the adapter was "WiFi 2" and it was a public network...didn't know our domain.

So I am leaning more and more on something weird is going on with our APs and it's bridging the public pool with our private pool somehow.

 

Anyone ever see anything like this???

11 Replies 11
alemabrahao
Kind of a big deal

Look, it seems to me that there is a rogue DHCP server or something like that on your network.

I have worked with Meraki for years and have never seen any cases like this.

When the device receives the IP, can you see which DHCP server is providing the address?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
LandmarkSupport
Just browsing

Weird right?? and the odd thing is the error I see in the log regarding my own computer is the multiple DHCP server detected error. which my computer is not...nor is any other computer onsite. DHCP is handled by the MX so when the other user got the error yesterday...it was showing the public IP of the MX as the DHCP server and DNS.

alemabrahao
Kind of a big deal

Okay, so are you proxying DHCP through MX or do you have a dedicated server?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
alemabrahao
Kind of a big deal

I'm referring to this configuration.

 

alemabrahao_0-1742312683573.png

 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
LandmarkSupport
Just browsing

MX handles DHCP...

LandmarkSupport
Just browsing

Oops thought I replied...lol..yes the MX handles our DHCP. We have 4 sites and each site the MX handles it. this is the only one acting weird. 

Mloraditch
Kind of a big deal

The only way this would happen barring an outrageous bug is there is another dhcp server plugged into the lan. Are you sure your spectrum modem doesn’t have a wired connection to the MX WAN AND a lan port?

 

you should also be able to see the ip address of the dhcp server on a client with a bad ip and trace the corresponding mac to a specific port. 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
LandmarkSupport
Just browsing

We have our fiber and secondary coax backup in their respective WAN ports and then going to switch from next LAN port. nothing onsite runs DHCP other than the MX. 

ww
Kind of a big deal
Kind of a big deal

You have a meraki switch?

Does it show anything related to this dhcp scope at switch>dhcp server&arp

 

Also go to mx event log, and filter on all dhcp.  Do you see the public  ip's being assigned there, and does it show mx_mac/ip

LandmarkSupport
Just browsing

I do not...I have a Dell switch that's basically a dummy switch. single VLAN

DineshSingh
Conversationalist

This could be occured due to 

1) Misconfigured DHCP Server, Layer 2 Briding Misconfiguration may also due to VLAN misconfiguration. 

If none of these, then it should be a bug in the firmware of MX. 

Get notified when there are additional replies to this discussion.