RT-AC3100 WAN gets disconnectd after Firmware upgrade to 3.0.0.4.380_3341

[Thiago Luttig]

Hello all,

I've updated to the latest firmware(3.0.0.4.380_3341) to my RT-AC3100
via the web interface and it went just fine. However after some hours
the WAN got disconnected and the WAN/Internet LED goes purple.

Rebooting the ADSL modem does not resolve it and the only way to get it
connected to the internet is to restart the ASUS router.

The ASUS router connects to the ADSL via Static IP address.

Does anyone else have upgraded to this
firmware(3.0.0.4.380_3341) and faced similar issue ?

Since the firmware update, system log started to show these messages:

Jun 3 21:01:16 WAN Connection: WAN was restored.
Jun 3 21:01:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 21:33:08 rc_service: httpds 507:notify_rc start_webs_update
Jun 3 21:35:38 rc_service: httpd 508:notify_rc start_webs_update
Jun 3 21:51:54 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 21:51:54 stop_nat_rules: apply the redirect_rules!
Jun 3 21:53:43 WAN Connection: WAN was restored.
Jun 3 21:53:43 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 21:54:08 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 21:54:08 stop_nat_rules: apply the redirect_rules!
Jun 3 21:55:15 WAN Connection: WAN was restored.
Jun 3 21:55:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 21:57:32 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 21:57:32 stop_nat_rules: apply the redirect_rules!
Jun 3 21:58:06 WAN Connection: WAN was restored.
Jun 3 21:58:06 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 21:59:38 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 21:59:38 stop_nat_rules: apply the redirect_rules!
Jun 3 21:59:51 WAN Connection: WAN was restored.
Jun 3 21:59:51 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 21:59:59 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 21:59:59 stop_nat_rules: apply the redirect_rules!
Jun 3 22:00:16 WAN Connection: WAN was restored.
Jun 3 22:00:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 3 22:04:01 DualWAN: skip single wan wan_led_control - WANRED off
Jun 3 22:04:01 stop_nat_rules: apply the redirect_rules!


Dual WAN is not activated and Asus router is using static ip to connect to the ISP router.

Tried going back to the 3.0.0.4.380_2345 however this new update does not
allow downgrading to any other builds before it

Sent a feedback to Asus via the router but so far no reponse from them.

Do you have any ideas or suggestions ?

 

[RMerlin]

Asus did some changes to PPP in recent firmware, which they reverted back in 3479. It's possible that this was the cause of your problem. You will have to wait for a newer version, or revert back to an older version.

 

[Thiago Luttig]

Asus did some changes to PPP in recent firmware, which they reverted back in 3479. It's possible that this was the cause of your problem. You will have to wait for a newer version, or revert back to an older version.

Hi RMerlin,

Thanks for the reply. Does the PPP infrastructure play any role in my actual context, where the RT router uses a static IP address to route everything up to the ISP modem without doing any PPPoE authentication or other related stuff ? I've even tried to set my ISP's modem to bridge mode and let the RT do the PPPoE negotiation and authentication but then it permanently reports as disconnected from the internet, even though the clients can navigate. Then reverted back to static WAN ip information and the same behavior comes back(form time to time WAN is reported as disconnected and WAN led goes purple).

What about using the firmware uploader tool to 'force' an older firmware(maybe 3.0.0.4.380_2345) in recovery mode ? Do you think that this would be possible as the regular firmware downgrade via file upload does not work(as announced by Asus in the release notes of this latest one) ?

Thanks in advance.

 

[bodean]

I am experiencing same issue now. Purple light, router GUI says disconnected from internet, however I am still on it. Not sure what's up...

 

[Thiago Luttig]

Also, I've noticed some decrease in the Wifi signal(lost around 7 to 10 Db measured in Wifi Analyzer app for Android in a Xperia Z3 Dual) in both 2.4 and 5GHz. Does anyone else feels this too after the update ?

 

[RMerlin]

Does the PPP infrastructure play any role in my actual context, where the RT router uses a static IP address to route everything up to the ISP modem without doing any PPPoE authentication or other related stuff ?

I think it's only related to users with PPPoE/L2TP connections, I can't be sure however there isn't an indirect impact on other types of connections.

What about using the firmware uploader tool to 'force' an older firmware(maybe 3.0.0.4.380_2345) in recovery mode ?

For now this method still works.

 

[RMerlin]

You could also test the 380.60 alpha build of my firmware, which is based on 3479, and therefore reverts those WAN-related changes.

 

[Thiago Luttig]

I think it's only related to users with PPPoE/L2TP connections, I can't be sure however there isn't an indirect impact on other types of connections.



For now this method still works.

Thanks RMerlin,

I'll monitor the behavior of the RT router during the upcoming weeks in the hope ASUS releases a new build/version of this firmware. I've already sent them an feedback via router itself. Let's see what happens.

Thanks again.

 

[Thiago Luttig]

You could also test the 380.60 alpha build of my firmware, which is based on 3479, and therefore reverts those WAN-related changes.

That would be great. Do you mind in share where i can get it ? This RT-AC3100 is my first Asus router, so I'm still using the ASUS firmware. Are both firmwares interchangeable between them using the recovery mode and upload tool ?

Also, after flashing the first Merlin firmware, further updates can be done via file upload using the
WEBUI or should I still use the flashing tool ?

Thanks in adavnce.

 

[Thiago Luttig]

Hi Merlin,

Ok, I've found your website and the download page

As for the 380.60, the changelog mentions that the new signature method of ASUS Firmware is already in place. Considering that I'm already using the
3-0-0-4-380_3341.33038 from ASUS, can I go for the standard upload/upgrade method using your build or should I go for the recovery method using the flashing tool ?

Thanks and BR,

 

[RMerlin]

Alpha builds are discussed in this thread.

This alpha should be directly flashable on top of 380_3341.

 

[Thiago Luttig]

Alpha builds are discussed in this thread.

This alpha should be directly flashable on top of 380_3341.

Thanks a lot Merlin. I have downloaded the alpha and will give it a try later today. Tomorrow i'll post whether it went fine or not.

Best regards,

 

[RMerlin]

Actually, wait a few days. That alpha build does NOT contain the fix yet. Check again this weekend, I should have a newer alpha build there by then.

 

[bodean]

Asus did some changes to PPP in recent firmware, which they reverted back in 3479. It's possible that this was the cause of your problem. You will have to wait for a newer version, or revert back to an older version.

3479 was never released for the 3100. But if you are merging it into your FW, for this router, thats great news.

 

[Thiago Luttig]

Actually, wait a few days. That alpha build does NOT contain the fix yet. Check again this weekend, I should have a newer alpha build there by then.

Thanks Merlin, i will postpone it to next week then. Looking forward for it

Sent from my D6633 using Tapatalk

 

[RMerlin]

3479 was never released for the 3100. But if you are merging it into your FW, for this router, thats great news.

All currently supported models are based on 3479. As long I have compatible binary blobs, I'm never tied to a specific release for a specific model. I just had to patch a few things together to ensure compatibility with the various closed source components.

Current alpha builds are based on 3459.

 

[Thiago Luttig]

All currently supported models are based on 3479. As long I have compatible binary blobs, I'm never tied to a specific release for a specific model. I just had to patch a few things together to ensure compatibility with the various closed source components.

Current alpha builds are based on 3459.

Hi Merlin,

I've just saw the following test build available:

RT-AC3100_380.60_alpha3-gda2457a.zip

This is the one based on 3479 with the merged fix for the WAN/ISP issue ?

Thanks and regards,

 

[RMerlin]

This is the one based on 3479 with the merged fix for the WAN/ISP issue ?

Yes, it contains the reverted changes from Asus related to PPP and WAN.

 

[Thiago Luttig]

Thanks, I'll update the router tonight and monitor the behavior

Sent from my D6633 using Tapatalk

 

[Thiago Luttig]

Hi Merlin,

Updated to 380.60alpha3 and is running for 3 hours in this version without any issues, specially the WAN disconnect.

One additional question: was the traffic monitor per device removed in this build? I'm failing to find it.

Thx and BR

Sent from my D6633 using Tapatalk