Recent content by fiasko

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
  1. F

    Release [Fork] Asuswrt-Merlin 374 LTS release 51E3

    six days in and evertyhing seems to be in order with my AC66U. Thanks John!
  2. F

    Release [Fork] Asuswrt-Merlin 374 LTS release 49E4

    Last evening my AC66U with 50DA rebooted again after four days of uptime. Firts log error was this. Aug 19 19:49:32 watchdog02: no watchdog, restarting After which all daemons stopped and router rebooted.
  3. F

    Release [Fork] Asuswrt-Merlin 374 LTS release 50E8

    Related to the other threads AC66U reboot issue, now 3d 9h uptime and still going. This is with the 50DA version. There was some issue last night which looks a bit troubling. Approximately 70h after last firmware update/reboot Aug 18 03:16:09 watchdog: restart httpd, error detected or process...
  4. F

    Release [Fork] Asuswrt-Merlin 374 LTS release 49E4

    My AC66 unit acts as secondary AP role in my house, and I didn't realy notice the rebooting issue before. It's using 48E7 build and looks like the reboot issue was there as well. I just updated to 50DA firmware to see if it makes any difference.
  5. F

    Timezone difference warning

    I believe these Javascript examples should get you the matches you are looking for. No need to play with any string indexes: const paragraph = 'Thu May 07 2020 22:28:01 GMT+0300 (Itä-Euroopan kesäaika)'; const regex = /([+-][0-9]+)/g; const found = paragraph.match(regex); console.log(found[0])...
  6. F

    Timezone difference warning

    Don't rely timezones and especially DST to be with even hour offsets. That assumption will very likely bite you. Some regular expression rule is propably better ([+-][0-9]+) for example.
  7. F

    Timezone difference warning

    This is what I found: var uptimeStr = "Sat, 09 May 2020 21:04:01 +0300(218368 secs since boot)"; That seems correct to me.
  8. F

    Timezone difference warning

    I just tried it, and still the warning shows up.
  9. F

    Timezone difference warning

    I see. So every time DST kicks in, the complaining starts again.
  10. F

    Timezone difference warning

    Do you mean if I change the computer timezone or the router timezone? If I remember correctly, during the winter when there's no DST I haven't seen the error message. So maybe the timezone difference bug shows only during DST.
  11. F

    Timezone difference warning

    Thanks. It shows "Thu May 07 2020 22:28:01 GMT+0300 (Itä-Euroopan kesäaika)" where (Itä-Euroopan kesäaika) means east-european summer time. So the time matches and they are almost the same, but not quite I guess.
  12. F

    Timezone difference warning

    I'm currently using the latest merlin firmwares (384.13_8 and 384.17) with my AC87U and AC88U routers. Both of them are complaining about timeoze difference between router and local all around the configuration menus. (I dont' know the exact error message in English since, i'm using the router...
  13. F

    [Release] Asuswrt-Merlin 384.13 is now available

    Can the AiMesh main router be in Access Point mode? If I have two Asus routers with Merlin firmware in my LAN and both are in AP mode, is it possible to link them together with AiMesh? And if they can, is it usefull to do so?
  14. F

    [Release] Asuswrt-Merlin 384.13 is now available

    So did the latest 384.13_1 patch resolve AC87U AP issues for everyone? I haven't seen any reports from it. Although I got the router working with 384.13 version, it feels like the newer version boots faster. But does the WAN port now work after booting for everyone else? Thank you Merlin for...
  15. F

    [Release] Asuswrt-Merlin 384.13 is now available

    My AC87U logs have few of these errors. Anything that I should be afraid of? These probably don't have anything to do with the dead WAN port in AP mode issue?
Top