On Wednesday, 23 October 2013 22:24:29 UTC+2, Rajnus wrote:
> hm, mozda bi onda scripta za resetiranje routera rjesila problem...
Postavio sam skriptu koja pinga google i ako postoji timeout veci od
5 minuta router se resetira.
Oct 23 22:32:52 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 22:37:03 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 22:40:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 22:46:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 22:50:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 23:06:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 23:13:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 23:20:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Oct 23 23:25:04 MikroTik Netwatch: missed a ping to 64.15.113.50 - starting 5 minute timeout script
Logove pratim preko hosted syslog servera
https://papertrailapp.com
Super stvarchica....
Nisam znao da se toliko cesto mijenja IP...
Oct 22 19:14:53 MikroTik DDNS: Sending UPDATE!
Oct 23 10:30:28 MikroTik DDNS: Sending UPDATE!
Oct 23 11:24:19 MikroTik DDNS: Sending UPDATE!
Oct 23 19:29:51 MikroTik DDNS: Sending UPDATE!
Oct 24 00:18:19 MikroTik DDNS: Sending UPDATE!