Is it normal to have to reboot a router after enabling an interface, addressing it, and creating the route for the interface?
It is quite frustrating to troubleshoot for an hour only to reboot and have the same exact rules work great on a reboot.
I have had a few issues like that over the years, random.
For whatever reason it will set one route as the default route and won’t accept mine until I reboot. I’d say 3 out of 100 have done it, generally after I’d changed the routes several times.
I don’t think it ever happened in a production situation, but when I was building out my CPE or AP config it has happened.
This is the 2nd time. I don’t know why I didn’t just reboot right off I just figured the first time was a fluke. But here’s the kicker. I’m back to the client’s office and now the route is non-functional again. It isn’t down. I can ping it from the router. Traffic works to the two internet interfaces from all 3 subnets but 1 of the subnets won’t get traffic to it from the other.
This is incredibly frustrating. Not changing anything and the router stops working. I feel like I’m using an old Linksys.