Home Network Community > Deco > DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
< Deco

DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
2025-05-05 20:19:31
Model: Deco BE63  
Hardware Version: V2
Firmware Version: 1.1.7 Build 20250324 Rel. 32980

Good afternoon.

 

After a thorough review of my connection with my ISP, I can conclude the following:

 

1. The connection is successful using my PPPOE credentials from my computer: This demonstrates that my credentials are correct and that it is possible to establish a PPPOE connection with the appropriate parameters.

 

2. For some reason, my DECO BE10000 cannot establish said connection despite having the same credentials and configuration as the PC.

 

It appears that the DECO BE63 / BE10000 is unable to send the username and password using the PAP protocol without encryption.

 

The device log shows "PAP Authentication Failed," confirming this conclusion (2).

 

While the DECO App interface allows you to manage many of its functions, there are specific protocol issues and options that are missing. On the other hand, the web interface is much more basic and does not offer this type of configuration.

 

Specifically: Could you send me a firmware build that's compatible with PAP, or what alternative do you suggest?

 

Not to mention, the device is one of the most advanced technolgy TP-Link has to offer (reflected in its cost), and it's unfortunate that I'm stuck for such a simple issue.

 

I look forward to your support to continue.

 

Thank you very much.

  0      
 
  0      
 
#1
Options
4 Reply
Re:DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
2025-05-07 02:13:21 - last edited 2025-05-07 02:15:02

Logs

 

Mon May  5 16:55:45 2025 daemon notice netifd: Interface 'internet' is setting up now
Mon May  5 16:55:45 2025 daemon notice netifd: proto_shell_handler Interface 'internet' cmd: 0
Mon May  5 16:55:45 2025 user  debug netifd: ubus  call network interface notify_proto { "action": 1, "command": [ "\/usr\/sbin\/pppd", "nodetach", "ifname", "share-internet", "ipparam", "internet", "lcp-echo-interval", "10", "lcp-echo-failure", "5", "nodefaultroute", "noaccomp", "nopcomp", "ipv6", "pppshare", "usepeerdns", "user", "<hidden>", "password", " <hidden> ", "ip-up-script", "\/lib\/netifd\/ppp-up", "ipv6-up-script", "\/lib\/netifd\/pppshare-up", "iMon May  5 16:55:45 2025 daemon notice netifd: proto_shell_script_cb Interface 'internet'
Mon May  5 16:55:45 2025 daemon notice netifd: proto_shell_task_finish Interface 'internet' state: 1
Mon May  5 16:55:45 2025 daemon info pppd[3675]: pppoe_init() success
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): pppoe_init() success
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: PPPoE DevName Hook, the name is nic-br-wan
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): PPPoE DevName Hook, the name is nic-br-wan
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: make the channel with pppoe_channel
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: PPPoE DevName Hook, the name is nic-br-wan
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): make the channel with pppoe_channel
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): PPPoE DevName Hook, the name is nic-br-wan
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:45 2025 daemon info pppd[3675]: Using interface pppdrv1
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Using interface pppdrv1
Mon May  5 16:55:45 2025 daemon info pppd[3675]: main 480 ipv4 = 0 ipv6 = 1
Mon May  5 16:55:45 2025 daemon info pppd[3675]: main 487 protp->enabled_flag = 0x0
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): main 480 ipv4 = 0 ipv6 = 1
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): main 487 protp->enabled_flag = 0x0
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: pppd 2.4.3 started by root, uid 0
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: PPPoE Connect Device
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): PPPoE Connect Device
Mon May  5 16:55:45 2025 daemon info pppd[3675]: Sent PADT
Mon May  5 16:55:45 2025 daemon info pppd[3675]: PPP session is 54297
Mon May  5 16:55:45 2025 daemon info pppd[3675]: Yangxv:new style driver
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Yangxv:new style driver
Mon May  5 16:55:45 2025 daemon info pppd[3675]: Using interface pppdrv1
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Using interface pppdrv1
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: Connect: share-internet <--> br-wan
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Connect: share-internet <--> br-wan
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:45 2025 daemon info pppd[3675]: got_sighup || got_sigterm || got_sigusr2 || got_sigchld
Mon May  5 16:55:45 2025 daemon info pppd[3675]: got_sigchld
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): got_sighup || got_sigterm || got_sigusr2 || got_sigchld
Mon May  5 16:55:45 2025 daemon notice pppd[3675]: len < 0
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): got_sigchld
Mon May  5 16:55:45 2025 daemon notice netifd: internet (3675): len < 0
Mon May  5 16:55:45 2025 daemon err conn-indicator: [send_query] Failed to send DNS query: Network unreachable
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon info pppd[3675]: got_sighup || got_sigterm || got_sigusr2 || got_sigchld
Mon May  5 16:55:48 2025 daemon info pppd[3675]: got_sigchld
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): got_sighup || got_sigterm || got_sigusr2 || got_sigchld
Mon May  5 16:55:48 2025 daemon notice pppd[3675]: len < 0
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): got_sigchld
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): len < 0
Mon May  5 16:55:48 2025 daemon info pppd[3675]: Remote message: Authentication Failure
Mon May  5 16:55:48 2025 daemon err pppd[3675]: PAP authentication failed
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Remote message: Authentication Failure
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): PAP authentication failed
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon notice pppd[3675]: Connection terminated.
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Connection terminated.
Mon May  5 16:55:48 2025 daemon info pppd[3675]: Sent PADT
Mon May  5 16:55:48 2025 daemon notice netifd: internet (3675): Command failed: Not found
Mon May  5 16:55:48 2025 daemon info pppd[3675]: Exit.

  0  
  0  
#2
Options
Re:DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
2025-05-08 03:29:29

  @AlexDLG still no response from support. 
 

research points to a faulty PAP protocol on DECO

  0  
  0  
#3
Options
Re:DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
2025-05-08 14:43:25

  @AlexDLG 

 

Base Configuration: (That works on the PC)

Internet Settings: PPPOE

PPPOE credentials (same as PC)

DNS auto

MTU 1492 (established by ISP)

 

Test cases (tested in combinations and permutations)

a) With and without IPv6 (opcional on PC)

b) With and without VLAN (not needed on PC)

c) With and without Mac address cloning (not needed on PC)

d) MTU 1480 (standard)

e) With and without service name y Access Concentrator Name (not needed on PC)

  0  
  0  
#4
Options
Re:DECO BE63 / BE10000 not connecting through PAP Authentication over PPPOE
2025-05-12 22:26:46

SOLVED

 

Apparently the IPV4 Config screen has a lot of bugs saving the information of your ISP's accounts and other such as DNS

 

The IPV4 information capture screen needs a general review: Reviewing logs and using trial and error, I noticed that the username wasn't being saved properly. Apparently, in some cases, a space is added at the end. This doesn't happen when you save it for the first time, but rather when you make a subsequent change to the Internet configuration (IPv4 or 6).

 

My workaround is to config everything that it's needed, go to IPV4, and save my username up to ".....  co", save it, then go back and save it as ".....   com" so that it's the final configuration and then it connects.

 

 

 

Also when you save the username and pwd on this screen, and then change the configuration to a dynamic IP, and then return to PPPOE... it seems as if the username and pwd are remembered, because you'll see your username and in pwd you'll see "***************". However, in the log, the router will send the ************ as a pwd; it doesn't actually save it.

 

 

Also the manual DNS config, it won't be saved. my workaround is to let it connect as described before, and theeeen try to set up manual IPs

 

 

What a mess......

 

 

I would review this entire screen in general with Q&A.

  1  
  1  
#5
Options

Information

Helpful: 0

Views: 555

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.