Community discussions

MikroTik App
 
WayneX
just joined
Topic Author
Posts: 3
Joined: Tue Mar 15, 2016 3:43 am

RouterOS 6.10 - Clients cannot access internet after schedule regular reboot intermittently

Fri Mar 25, 2016 9:12 am

As mentioned above, we configured a schedule weekly reboot, IP address was issued to clients within DHCP scope, but clients cannot access internet after the reboot intermittently, usually I need to manual reboot again then it can work, can anyone teach me how to resolve it permanently? thanks.
 
User avatar
hgonzale
Member Candidate
Member Candidate
Posts: 272
Joined: Thu Nov 06, 2014 1:12 pm
Location: Fuengirola, Spain
Contact:

Re: RouterOS 6.10 - Clients cannot access internet after schedule regular reboot intermittently

Fri Mar 25, 2016 9:43 am

After the automatically reboots, are you getting the IP from the DHCP?
This is a not normal issue, we need to know first what is happening and at 99% the, the problem is not in the mikrotik...
 
WayneX
just joined
Topic Author
Posts: 3
Joined: Tue Mar 15, 2016 3:43 am

Re: RouterOS 6.10 - Clients cannot access internet after schedule regular reboot intermittently

Tue Mar 29, 2016 5:21 am

After those automatically reboots, clients are able to getting IP from DHCP.
When the problem happens, usually a manual reboot on Mikrotik can resolve it, so I'm pretty sure this problem is in Mikrotik. But all log is emptied after reboot, so any suggestion how to do troubleshooting?
 
User avatar
hgonzale
Member Candidate
Member Candidate
Posts: 272
Joined: Thu Nov 06, 2014 1:12 pm
Location: Fuengirola, Spain
Contact:

Re: RouterOS 6.10 - Clients cannot access internet after schedule regular reboot intermittently

Tue Mar 29, 2016 9:57 am

I am asking about getting IP in the Router from the Bridge/modem, if your MK is getting the IP, not your clients
 
WayneX
just joined
Topic Author
Posts: 3
Joined: Tue Mar 15, 2016 3:43 am

Re: RouterOS 6.10 - Clients cannot access internet after schedule regular reboot intermittently

Mon Apr 11, 2016 8:27 am

MK are not configured to get IP from DHCP, we're using MK to provide service of Captive Portal.
A particular VLAN is configured in the main route and MK is a member of that VLAN to access internet.

When the problem happened, usually a manual reboot can resolve it.

Who is online

Users browsing this forum: maigonis, mbovenka, mquan1984, rplant, scsiii and 114 guests