scMerlin scMerlin 2.5.41 - Service and script control menu for Asuswrt-Merlin

[Tarek Yag]

I also get this though on the development version when I failover, whereas I would have expected a low number for WAN1, as in counting from when it "took over"?

Logically you're talking totally right. But as I myself understood from lots of reading in this forum, the Asus Dual WAN feature is so unreliable and full of bugs, and that's why there's Ranger's script WAN Failover.
So, I guess this issue has nothing to do with scMerlin or AMTM in general.

Probably just display issues as you say?

So, no! Probably stock firmware issues as I just explained.

No doubt @ExtremeFiretop will chime in and clarify all this and tell me what an idiot I am...

LOL! Don't say that.
I'm waiting for @ExtremeFiretop's reply to assure my understandings too.

 

[ExtremeFiretop]

@Stephen Harrington

Sorry for the delay, I've been mentally tired recently after work and passed out early last night.
There was a few things cleaned up last night can I have you re-test and advise? Make sure do download the latest develop version

Thank you!

 

[ExtremeFiretop]

I also get this though on the development version when I failover, whereas I would have expected a low number for WAN1, as in counting from when it "took over"?
Probably just display issues as you say?

View attachment 67798

View attachment 67799

No doubt @ExtremeFiretop will chime in and clarify all this and tell me what an idiot I am...

@Stephen Harrington
To be specific, this is what I'd like you to re-test and advise about found above

 

[Stephen Harrington]

There was a few things cleaned up last night can I have you re-test and advise? Make sure do download the latest develop version

Ok, @ExtremeFiretop, I did a "uf" force update and re-tested ...

Starting state:

After Failover (and waiting a bit):

After Fallback (and waiting a bit):

So it looks like this version happily "re-starts the clock" on WAN0 but the same thing does not appear to be happening on WAN1 ... it just continues the cumulative time as per what was already the count for WAN0?

Is that what I'm meant to be seeing?

If on the Failover the time on WAN1 likewise started from zero that would be a useful compromise I guess?
Would let you know how long you'd been on backup WAN etc ...

Not sure what you have in mind though.

 

[ExtremeFiretop]

Ok, @ExtremeFiretop, I did a "uf" force update and re-tested ...

Starting state:

View attachment 67821

After Failover (and waiting a bit):

View attachment 67822

After Fallback (and waiting a bit):

View attachment 67823

So it looks like this version happily "re-starts the clock" on WAN0 but the same thing does not appear to be happening on WAN1 ... it just continues the cumulative time as per what was already the count for WAN0?

Is that what I'm meant to be seeing?

If on the Failover the time on WAN1 likewise started from zero that would be a useful compromise I guess?
Would let you know how long you'd been on backup WAN etc ...

Not sure what you have in mind though.

No not what I had in mind it should reset everytime for both interfaces as they become the "active" interface...

Let me dive a little deeper and I'll PM you if I need any additional information.
I just wanted to see how it was functioning now after the last tweaks.

I hope to have progress soon, don't go too far!

 

[Stephen Harrington]

I hope to have progress soon, don't go too far!

Looks like you are halfway there then ... out running errands for next couple of hours but I'll check in here after that and respond.
I'm GMT+10 Sydney Australia timezone.