Recent content by stylish_me

lol :)

So it means there will be no beta 4 you wrote about?

Hi! I am back from my trip so if you need some help with testing - i will be able to help starting this Saturday. Thanx!

It could be a great feature, not a bug - if it really tracked diconnected wan cable and didn't switch every time to wan0 untill cable is really connected. But it says disconnected even when cable is plugged back. Fckn assus.

Hi! Thanx for your update. I will be on vacations for 3 weeks so will not be able to test new releases. I did some tests yesterday - and i am 1000% sure that the mechanism you are using in the script is breaking primary/secondary WAN detection. Or this mechanism is not reliable at all. Because...

Try dual wan helper from @thelonelycoder - i think it will help you a lot!

Now i am on primary - only after it switched from secondary after 9*99 timeout. That means that script is in charge of this strange behavior. I hope tomorrow morning we will find out what is the problem )))

I unplugged primary wan - it switched to secondary and didn't send email. After 9*99 sec it switched back to PRIMARY and sent correct email about primary wan. I dont understand what is going on.

Not sure if colors could help me lol. If you reboot your router running beta3 - it says you are on primary or on secondary? I cannot understand what is happening to my router..

Wow that is really strange. Switched back to beta 2 and now it says it is on secondary wan as well. So i see 2 versions: 1. Either this unpingable dns corrupts everything - it means you should have the same problem like i do. Please test it. 2. Or your script made some changes to some files and...

Power cycled the router - it is still online saying it is on secondary wan although it is on primary. I will try to switch back to beta 2 to see if it's code related bug.

Smth strange is happening. Secondary is changed to secondary and script sends email about it. But the router is still on primary. May be there is some mistake in the script? /tmp$ /jffs/scripts/dual-wan-helper kill Terminated /tmp$ /jffs/scripts/dual-wan-helper...

[0;31mSecondary-WAN link_wan 1 wan_primary [0;31m1 link_wan1 1 WAN_IP [0;31m192.168.0.111 That is 100% wrong. I don't know where it gets this information. These numbers refer to secondary wan. And the router is running primary. Why does it happen?

So it's not the problem. Or now your script says secondary wan when it's primary with you too? I think the problem is that script reads this wrong data from some file that was not cleared before. And new data is not written to that file.