Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. stylish_me

    [beta] Dual WAN helper script (discontinued)

    No smth is still wrong. I rebooted router after all those tests in verbose mode, now router shows that it is on primary wan, but script gives me this right after reboot Aug 11 21:02:14 crond[301]: time disparity of 1068121 minutes detected Aug 11 21:02:39 admin: dual-wan-helper: WAN type change...
  2. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Well i feel how dumb i sound at this moment but this is smth out of my understanding :-) I understand that you used some walkaround not to get email notification after 9*99 timeout. That's clear. But i don't understand why you are not using 99*9 as a separate failback timeout. Just tell me that...
  3. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Hmm now it made failback within 17 minutes. Really interesting lol But where did it take that final number? ping OK, Secondary-WAN, 192.168.0.111, WAN test in 71, Progressive timeout 36 Primary-WAN reported
  4. stylish_me

    [beta] Dual WAN helper script (discontinued)

    I still don't understand one thing. If wan test time is 71 and it repeats cycles - so where is the counter for that failback timeout 99*9? As far as i see it can repeat these cycles forever - but we need to repeat them untill 99*9 timeout runs out. I am sure that you programmed everything right...
  5. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Ok i'll check once more how many minutes will it take to failback from secondary to primary. It should be 99*9 = almost 15 minutes if i am not mistaken..
  6. stylish_me

    [beta] Dual WAN helper script (discontinued)

    For now it took more then 33 minutes to switch back from secondary to primary. It is ok for me. Need to test it again to be sure that it was not faulty asus that didn't switch back - but it was the timeout set in the script. Because it switched back only in verbose mode. May be because i...
  7. stylish_me

    [beta] Dual WAN helper script (discontinued)

    It happends like this and WinSCP starts saying that it cannot ping the router for more then 15 sec ping OK, Primary-WAN, 10.13.70.222, WAN test in 71, Progressive timeout 0 ping OK, Primary-WAN, 10.13.70.222, WAN test in 62, Progressive timeout 0 ping OK, Primary-WAN, 10.13.70.222, WAN test...
  8. stylish_me

    [beta] Dual WAN helper script (discontinued)

    I think problem is here: Settings used for dual-wan-helper 1.0 beta 3 WANDOG_INTERVAL = 9 (real setting 9) WANDOG_MAXFAIL = 2 (2) WANDOG_FB_COUNT = 99 (99) SLEEP_TIMEOUT = 9 PING_COUNT = 27 WAN_SUCCESSFUL = 71 SEND_MAIL = on NTP Timeout = 36 NTP Sleep = 4...
  9. stylish_me

    [beta] Dual WAN helper script (discontinued)

    19.20 + 99*9 = 19.20 + 891 sec = 19.20 + 14 min 51 sec = 19.35
  10. stylish_me

    [beta] Dual WAN helper script (discontinued)

    That's really strange. Timeout is not for secondary wan. And it is not switching back to primary. I think you mixed two wan types.. /jffs/scripts$ /jffs/scripts/dual-wan-helper kill Terminated /jffs/scripts$ /jffs/scripts/dual-wan-helper ---------------------------------------------...
  11. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Hmmm i was to fast. Failback is not working. Aug 11 19:20:54 WAN(1)_Connection: WAN was restored. dual wan settings are 9 / 2 / 99 now it is 19:43 - but failback didn't happen.
  12. stylish_me

    [beta] Dual WAN helper script (discontinued)

    seems to work ok. Didn't try in verbose mode - not much time for testing now. And it takes almost 2 minutes for the notification when i unplug wan cable. Aug 11 19:19:42 WAN(0)_Connection: WAN was exceptionally disconnected. Aug 11 19:19:46 WAN(0)_Connection: Ethernet link down. .... Aug 11...
  13. stylish_me

    [beta] Dual WAN helper script (discontinued)

    By the way! When being connected to secondary WAN - Asus 100% sees the state of primary wan cable. As soon as i unplug cable - UI says cable not connected. When i plug cable back - it says smth like standby - but still stays on secondary. I think this standby status after "cable not connected"...
  14. stylish_me

    [beta] Dual WAN helper script (discontinued)

    9/2/99 is ok for me for now because i need maximum failback timeout and minimum failover time. To have at least 12-15 minutes of proper internet before stupid asus switches back to primary which is down and breaks connection for almost 25-30 seconds. Custom failback and failover counts and...
  15. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Now it works ok with 9/2/99 So for now the only problem is that first number should be NOT 8 (and not 7 as well)? And i see a second bug that it takes almost 2 minutes to send email notification when primary wan is physically disconnected (with previous email notification script it took 5-10...
  16. stylish_me

    [beta] Dual WAN helper script (discontinued)

    or 9/6/99 WANDOG_INTERVAL = 10 (real setting 9) WANDOG_MAXFAIL = 6 (6) WANDOG_FB_COUNT = 100 (99) like you said before? is it possible to set maxfail to smth less then 8? Because it will give at least 80 seconds without internet if primary wan is down..
  17. stylish_me

    [beta] Dual WAN helper script (discontinued)

    ping OK, Primary-WAN, 10.13.70.222, WAN test in -1748, Progressive timeout 0 lol may be it is easier not to fix beta2 but to make customizable settings for failback and failover like i wrote in previous message?
  18. stylish_me

    [beta] Dual WAN helper script (discontinued)

    No problem, i like the process :) It would be perfect in future releases to be able to set for example failover: 2 times, 2 seconds = 4 seconds failback: 5 times, 360 seconds = 30 minutes. It means that router will switch to primary just for 4sec to check if it is still down. If so - than...
  19. stylish_me

    [beta] Dual WAN helper script (discontinued)

    Hmmm ping OK, Primary-WAN, 10.13.70.222, WAN test in 92, Progressive timeout 0 ... ping OK, Primary-WAN, 10.13.70.222, WAN test in -1092, Progressive timeout 0 It gives more then 1100 together and it is not going to stop. Where dows it get such a huge timeout number when ~980 is maximum?
  20. stylish_me

    [beta] Dual WAN helper script (discontinued)

    So all the numbers should be positive? Unfortunately it is real world problem for me because when 220 goes down - my router switches to UPS and main isp's line "unplugs" itself without 220V. In beta1 emails were perfectly sent at least after huge timeout. Which is a bit better then not getting...
Top