About Gillic01

Gillic01 · ‎01-17-2022

We went back to Current version: MX 14.56 and have not had any issues since.

Gillic01 · ‎11-30-2021

I think you are correct. Problem with that is CradlePoints with private ip on their inside, the MX Headend would never be able to connect to that outside of the tunnel which is what is happening, even if I allowed that traffic he wouldn`t know where to go. Checking with Support now, should be able to block this traffic maybe on the headend

Gillic01 · ‎11-29-2021

Yes so we deny this Hub to talk out to those private ip addresses, if I did add an acl to allow it, how would it even know where that private ip is?

Gillic01 · ‎11-29-2021

I have noticed my mx450`s are trying to create tunnels to LTE devices on Wan2 Private ip address, but we are denying this on our ASA. But don`t think this is a good idea to permit our MXHub to talk out to private ip`s

Gillic01 · ‎10-18-2021

Our company has had issue with 15.44 where two separate mx 450 just stopped responding and had to be powercycled. Happened once then again 30 days later.

Gillic01

Community Record

Badges

Re: Avoid 15.44 if you are running a warm spare configuration

Re: Hub trying to connect to LTE private ip`s

Re: Hub trying to connect to LTE private ip`s

Hub trying to connect to LTE private ip`s

Re: Avoid 15.44 if you are running a warm spare configuration

Re: Avoid 15.44 if you are running a warm spare configuration