- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
T-Mobile CradlePoint Failover Connection
Installed a T-Mobile CradlePoint for Failover Connection on WAN2... Testing it, I was not able to browse / resolve names, but able to ping IPs just fine... I don't think it's an issue on the MX configurations, however, if anyone has encountered this issue when first setting up a cradle point, what were the steps for resolving?
I have the MX WAN2 connected to the CradlePoint's Port 1 - its using DHCP to assign an IP... It's giving WAN2 a public IP and using T-Mobile's DNS IPs.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @GFrazier, appreciate you bringing this to the community. The issue seems to be related to DNS from your description, since the MX is online on WAN 1 you can run a packet capture on WAN 2 to see if there is any response to the DNS query the MX is sending.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @GFrazier, appreciate you bringing this to the community. The issue seems to be related to DNS from your description, since the MX is online on WAN 1 you can run a packet capture on WAN 2 to see if there is any response to the DNS query the MX is sending.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi SaheedA,
I just saw this today... I don't know how I overlooked something so simple, however, I figured it out a couple of weeks ago. Thank you for responding.
