I’ve been experiencing daily drops of internet with no signs of loss on the modem. I’m wondering if Watchdog is a necessary feature to make sure I have good uptime.
I noticed a comment about DNS and I’m fairly certain I’m using google DNS on the router. I was wondering if that is where the problem is.
Also, noticed 1.0.14 is now available. Should I try to update first?
Thanks.
Some of the watchdog and uptime checking features were modified for the better in 1.0.14, I would update. (I like to update, then factory reset, then re-setup … but that’s just me 
)
BUT in general, the watchdog set at 10 to 30 mins would be a good idea if you are having issues with general connectivity that a connection reset fixes.
You can set it to 5 mins, but if your connection has periodic service blips more often, the watchdog at 5 mins can be a little aggressive, unnecessarily.
Thanks. I was on a VPN when I saw the update was available. Felt more comfortable doing the update on site. Factory reset, I’ll definitely want to be on site so I can make the necessary tweaks.
It should be fine to update direct, I’m just obsessive over fresh configs Safer when on site with any updates on net hardware 
I got on site and did the update. I didn’t have the time to do a full reset. However, I did enable the watchdog function.
The strange thing is it seems like the router is losing connection with the Invisagig and the only way to fix it is a reboot. It took more than one reboot to get the internet back through the network.
Any ideas what else to check?
Which router are you using with it?
Mikrotik hap_AC2. I was looking for one that could do VPN with CGNAT.
I did change the DNS settings to Google but I feel like whats happening is a connectivity issue between the Router & Invisagig.
It would be Mikrotik, lol. I have almost zero experience with Tiks.
What does the Miktotik logging say is happening on the WAN interface?
Also, have you disable the IPPT on the InvisaGig? AND are you on T-Mobile with the IG in Auto mode with LTE and both NSA 5G and SA 5G enabled?
I ask, because if the modem/network is swapping between SA and NSA mode, and the modem is in IP Passthrough, it will have to drop the ETH interface to re-assign IP addresses each time it swaps between modes. The Mikrotik may not like this. Hopefully it’s not doing something like randomized mac addresses on the WAN interface, that would further muck things, I’d think.
Not sure if @ryan is around to wade in.
Yes, I would echo Richard’s response. Mikrotik can be extremely finicky with bridge mode / IP passthrough type connections in my experience. I would either turn this off at least for testing to see if it improves stability and/or statically specify the specific MAC address of the WAN port on the Mikrotik within the IG local network configuration.
I see that the connectivity issue was occurring pre-update so there is a good chance bridge mode or carrier network mode flapping (between LTE/NSA and SA) will be the culprit as Richard has highlighted.
Thank You both for the feedback. This sounds exactly like what’s going on. I’m unfamiliar how to check mikrotik logs but every time it happens the WAN IP is lost and I can’t release/renew it. I will turn off pass through.
I didn’t configure the MAC address before but do you think that will allow me to keep it in passthrough mode? Is there any benefits to passthrough mode?
Yes, statically setting the WAN interface MAC in the IG Local IP configuration (under Connection Configuration) when enabling pass through solves this for most routers. Pass through is mostly designed for business plans that have static, public IPs. If you have a standard consumer plan it is less useful as your connection will be behind carrier grade NAT anyways. In either case, there can be a slight performance improvement when pass through is enabled as it eliminates one additional layer of NAT. Hope this makes sense