Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)

Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)

Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)
Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)
3 weeks ago
Model: Archer BE700  
Hardware Version: V1
Firmware Version: Firmware 1.3.1 Build 20260519

Issue

Since updating to firmware 1.3.1 Build 20260519 rel.14520, my Archer BE700 no longer reliably restores the PPPoE connection automatically after a WAN/Internet interruption.

Previously the router would recover on its own. Now, if the WAN connection drops, the router can remain offline indefinitely until I either:

  • Manually press Connect on the WAN page
  • Reboot the router
  • Reload the WAN configuration

What I Observed

The logs show the router repeatedly attempting PPPoE discovery but failing to establish a session automatically.

Example:

1 pppoe send PADI

2 pppoe send PADT due to(resending PADI)

3 pppoe send PADI

4 pppoe send PADT due to(resending PADI)

5 pppoe send PADI

6 pppoe send PADT due to(resending PADI)

This cycle can continue for an extended period

 

However, once I manually reconnect the WAN interface, the PPPoE session immediately establishes successfully:

1 PADI

2 PADO

3 PADR

4 PADS

5 CHAP Success

6 IPCP ACK

7 IPV6CP ACK

and Internet access returns normally.

Why I Believe This Is a Firmware Issue

The logs demonstrate that:

  1. PPPoE credentials are correct.
  2. ISP authentication succeeds.
  3. The connection resumes normally when a manual reconnect is triggered.
  4. The failure appears to occur in the router's automatic PPPoE recovery process after a WAN interruption.

This suggests a possible firmware regression affecting PPPoE reconnection logic rather than an ISP authentication problem. 

Additional Question About Firmware

My router shows: 

1.3.1 Build 20260519 rel.14520

However, I cannot find this exact firmware on the TP-Link Australia download page.

Can TP-Link please confirm:

  1. Is 1.3.1 Build 20260519 rel.14520 an official Archer BE700 (AU) V1 release?
  2. Was it distributed via cloud/staged rollout?
  3. Is there a known issue affecting PPPoE automatic reconnection?
  4. Is there a newer firmware, beta firmware, or hotfix available?
  5. Can this issue be escalated to the firmware engineering team?

Existing Case Numbers

  • TKID260923700
  • TKID260923702

Any feedback from TP-Link staff or other BE700 users running PPPoE would be greatly appreciated.

Thanks, Ian

File:
syslog-2026-09-11.pdfDownload
  0      
0
#1
Options
2 Reply
Re:Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)
3 weeks ago

Hello  @Ian_W ,

 

Thank you for the detailed information and the case IDs regarding previous follow-ups.


Based on these details, we have confirmed the current status of your case: it is scheduled to be escalated to an engineer. We recommend keeping an eye out for email replies and maintaining contact with the engineer.

 

Regarding your observation that the latest firmware (version 1.3.1) is missing from the official website, this is usually because the local site has not yet uploaded it. Rest assured that as long as the firmware was delivered via the automatic "Firmware Update" function, it is safe to use.

 

Thank you for your feedback. You are welcome to reach out here if you receive a solution from the engineer. heart

  0  
0
#2
Options
Re:Archer BE700 (AU) V1 - PPPoE Doesn't Automatically Reconnect After WAN Drop (Firmware 1.3.1)
3 weeks ago

  @Joseph-TP 

Hi Joseph,

Thank you for the update and for confirming that my case is being escalated to an engineer.

I have now provided TP-Link Support with the latest system log and will continue to work with the engineering team.

I will update this thread if I receive a solution or further information.

Thank you again for your help.

  1  
1
#3
Options

Information

Helpful: 0

Views: 7096

Replies: 2