About allanmack

allanmack · ‎10-19-2021

So does it just mean it's an older MX250, since they've been out for a while now?

allanmack · ‎10-19-2021

The only one I have is this one from when I claimed the device. The rest of the dashboard just shows MX250.

allanmack · ‎10-19-2021

Today, I activated a new MX250 (which I've done many times). However, when I claimed the serial number on this one, it showed up with the model 'MX250B-HW.' I've never seen this, so I attempted to Google it and came to no answers. Has anyone else seen this and know what the difference is versus "MX250-HW"?

allanmack · ‎10-04-2021

EAPoL timeout indicates an 802.1X issue. Have you checked the logs for this user on your RADIUS server?

allanmack · ‎09-28-2021

Thank you, this is exactly what we were experiencing. The MX record is associated with the 1:Many NAT and the O365 server on the outside is expecting to only receive from that IP, so it denies anything from the WAN IP of the Merak. I confirmed this from the headers in the email that was being sent as the source was the WAN IP of the Meraki. Thank you for the information.

allanmack · ‎09-28-2021

Yeah, I'm not talking about 1:1 NAT. Just specifically 1:Many NAT.

allanmack · ‎09-27-2021

Right, and that's how it works on any NAT device. However, two Meraki Support engineers told me otherwise and services did not function as expected. Unfortunately, I was unable to do a packet capture before having to revert to validate this.

allanmack · ‎09-27-2021

I was just on the phone with Meraki Support for a little while, attempting to activate a new customer on an MX100. However, Meraki Support told me 1:Many NAT doesn't actually NAT the outbound traffic and rewrites the packet to the WAN IP of the Meraki. Is the only usage for 1:Many NAT for inbound port forwarding?

allanmack

Community Record

Badges

Re: MX250B-HW

Re: MX250B-HW

MX250B-HW

Re: MR46 fail connection - authentication stage - new to Meraki

Re: MX 1:Many NAT

Re: MX 1:Many NAT

Re: MX 1:Many NAT

MX 1:Many NAT