Hey all, I’m getting a really strange issue: when I add the gateway static route (so dest address 0.0.0.0/0 → gateway IP) the router starts majorly dropping out. If I run a ping test while doing this before adding the route my pings are <1ms, but as soon as I add the route it starts dropping/timing out and when it does go through the pings are ~3000ms.
This is using Hyper-V and Cloud Hosted Router. I’ve tried several different versions and they all do it. There’s even a currently functioning instance of the RouterOS (with the same resources and config in Hyper-V) that has to be replaced as we switched software providers because the old provider was having all kinds of issues. This is even from using a fresh download of the CHR and following the first time setup from the wiki to a tee, as well as trying to use the quick set via winbox. I even tried cloning the working instance, wiping it, and reconfiguring from there and it still does it.
Note: this happens regardless of whether the old instance is shutdown, so it’s not conflicting with the new. Also, this is an ISP gateway, so WAN and LAN are both public IPs.
I feel like there’s some simple setting that’s the issue, but I have very little knowledge of the RouterOS and I wasn’t able to figure out what was wrong or what was the difference between the old functioning.
Can you show your routing table when it’s in it’s working condition? Either screenshot from Winbox IP/Routes or text from Terminal “ip route print detail”
Then the same when it’s in the failed condition with your route added.
I will grab some screenshots tonight when I can try again. Although, outside of that default route the only other routes were the dynamic ones added automatically when adding IP addresses. Ie. LAN IP - > ether2 (lan), WAN IP - > ether1 (wan).
I did see what would happen I added it while it was not in-line and it didn’t cause any issues, so clearly something is going on with it handling traffic being the problem. I’m going to try adding some extra firewall rules tonight to see, but the currently working one doesn’t have any firewall rules outside of the ones for directing traffic for delinquent/active accounts.
I’m not sure what happened, but apparently my latest reply got eaten.
After a lot of testing, and at a loss for ideas, I finally decided to try re-renewing the license and it immediately started working. I’m not sure what happened, the license was showing as P Unlimited before I re-renewed it, so it would seem something must have gone wrong with registering the license? Of course, it was getting bombarded with like ~2Gbps of traffic when put inline (it’s a fiber gateway), so the 1Mbps of the free license was getting totally destroyed.
Added to this, and maybe related, after getting everything set up it started crashing every few minutes. This was all on the latest 7.1.2 Stable CHR. I ended up spinning up another Hyper-V instance, but this time using the 6.48.6 Long-term and everything went smoothly and has been in-line since the 11th without issue!