IP failing on RB2011 after restart

RouterOS General
1

I have an RB2011 on 6.42.12

I use it to access a Telstra wifi AIR network and then provide a wifi internally to access that for my home pc’s.

the network dropped off today and after a router restart, I cannot ping any local IP addresses in or out of the router.
the problem is the same on local wifi and also plugged directly by eth cable into the RB2011 and effects all local subnet though everything is picking up its DHCP ip address when joining the router.
(mobile phones, pcs)

there have been no changes to the config and I even double checked against a back-up config to see if there had been corruption but all is OK
the clock was slightly out by 2 mins after a few reboots trying to fix the issue, but I reconfigured it is now correct but has not solved the issue.

nothing appears to be wrong on the router (accessed using MAC address via winbox as cannot access using ip address)
the RB2011 can reach the Telstra network and is joining it, but not authenticating as I usually do that from a local PC

the local PC is accepting the DHCP ip address of 192.168.88.182 from the router,
but pinging to the router 192.168.88.1 has no response though ipconfig looks fine with gateway as the router ip address 192.168.88.1
though I can see it ping on the router interface when TORCH is used and it goes through the firewall when LOG is used.
the PC says it is failing the ping with a time out.

all ip addresses look to be working on the router, and listed available on the router, all leases are provisioned and look to be functioning.
and even show dns, icmp and other traffic listing as moving across the interfaces when I use TORCH

but no access and ping fails with timeout from all local machines (wifi or wired to interface)


then the real weird bit…
when I ping from the terminal on the RB2011 in winbox I can ping all local ip addresses assigned to the router interfaces (e.g. 192.168.88.1)
but if I try to ping local addresses leased out by the router (e.g. 192.168.88.182) or anything beyond the router on local networks
it comes up as

HOST ADDRESS 10.128.128.128 and the ip address as “admin prohibited”

all this from a reboot of the router? though it may have happened just before reboot and dropped the network.

any ideas on what is going on or how to proceed. I am stumped. is the router maybe finally broken it is 5 years old and been in a lot of dust?

EDIT: one thing I just noticed is the ip route print shows the gateway for 192.168.88.0 as 192.168.88.3 which is the Eth 3 interface (currently PC 192.168.88.182 is plugged into this)
but gateway should be 192.168.88.1 which is the WLAN2 interface and what the local machines have from DHCP. WLAN2 lists as up and working fine, so why is this change occuring in the routing?

2

problem fixed and for anyone who runs into this, maybe what I did will help

the virtual Wlan2 interface (192.168.88.1) had decided to drop the auto-route to 192.186.88.1 as the gateway for all 192.168.88.0 traffic, and for some reason it had changed the route table to 192.168.88.3 (Eth3 int) instead for all that traffic. so all IP traffic was failing for 192.168.88.0 in and outbound.

I tried removing the auto-route info 192.168.88.0 ,and adding it in manually as 192.168.88.1, but it just refused to accept it.

I was scratching my head at this point and the only other change I had made was to the SNTP settings, since the time had drifted 4 minutes out for some reason. (still not sure how or when)
after the next restart it worked and reset the route for 192.168.88.0 back to the proper gateway (192.168.88.1) automatically.

I can only assume the SNTP lost access to the original time server, and once the time on the router drifted, this impacted the IP info until finally it lost the plot and the network started to fail,
to compensate, maybe on the first reboot, it changed the gateway to another ip address 192.168.88.3, but then did not bother setting it back until I fiddled with it.

maybe someone can shed some light on this issue, because it had me very confused for a few hours and the route change occured automatically at some point before I touched it.

3

If you post full config (/export hide-sensitive and redact public IP address(es) - replace it with distinct text - and SSIDs + preshared keys) , we can have a look.