ASUS setup for BT Full Fibre

Hi folks, I've got a ASUS TUF Gaming AX5400 Router which I'm trying to setup with BT Full Fibre.

Had a new Openreach Nokia modem installed today, which is working just fine with the BT-supplied Smart Hub 2.

I just can't get it working with this ASUS router though

Used the login details:
- Username: [email protected]
- Password: bt

I tried 2 different ethernet cables just in case. Then suspected a hardware fault, so connected the WAN of the ASUS to the SH2 and that connected fine (via DHCP). So it seems to be something with the ASUS config for PPoE.

Screenshots of config: https://drive.google.com/drive/folders/1kLpxJiyH39iG...

There are tons of settings, I've tried several different combinations but this is how it's configured after a factory reset. Any suggestions or tips appreciated!

Connect the router WAN port to the ONT. Power cycle the router and allow it time to settle and to connect/ or attempt to connect via PPPoE (about 3 minutes or so give or take)

Post the output from the System Log from the router, so we can see what (error) messages are being logged.

Thanks for the suggestion, here's the log output:

May 5 06:07:53 hour monitor: daemon is starting
May 5 06:07:53 hour monitor: daemon terminates
May 5 06:07:54 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
May 5 06:07:54 miniupnpd[2218]: Cannot get IP address for ext interface . Network is down
May 5 06:07:54 miniupnpd[2218]: HTTP listening on port 55991
May 5 06:07:54 FTP Server: daemon is stopped
May 5 06:07:54 miniupnpd[2218]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 06:07:54 Samba Server: smb daemon is stoped
May 5 05:07:54 rc_service: httpd 1305:notify_rc restart_firewall
May 5 05:07:55 rc_service: ledg 1228:notify_rc restart_ledg
May 5 05:07:55 rc_service: waitting "restart_firewall" via httpd ...
May 5 06:07:55 miniupnpd[2218]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:07:55 lldpd[2272]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 5 05:07:55 rc_service: httpd 1305:notify_rc restart_wan_if 0;chpass;restart_time;restart_wireless;restart_cfgsync
May 5 05:07:57 pppd[1996]: Unable to complete PPPoE Discovery
May 5 06:07:58 pppd[2300]: pppd 2.4.7 started by admin, uid 0
May 5 06:07:59 kernel: klogd started: BusyBox v1.24.1 (2022-01-05 20:25:40 CST)
May 5 06:07:59 miniupnpd[2218]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:07:59 hour monitor: daemon is starting
May 5 06:07:59 hour monitor: daemon terminates
May 5 06:07:59 kernel: CSIMON: CSIMON[1.1.0] Initialization
May 5 06:07:59 kernel: CSIMON: M2M usr already registered ...
May 5 06:07:59 kernel: CSIMON: CSIMON[1.1.0] Initialization
May 5 06:07:59 kernel: CSIMON: M2M usr already registered ...
May 5 06:08:00 kernel: CSIMON: CSIMON[1.1.0] Initialization
May 5 06:08:00 kernel: CSIMON: M2M usr already registered ...
May 5 06:08:00 wlceventd: main(961): wlceventd Start...
May 5 06:08:00 acsd: eth5: Selecting 2g band ACS policy
May 5 06:08:04 acsd: eth5: selected channel spec: 0x1008 (8)
May 5 06:08:04 acsd: eth5: Adjusted channel spec: 0x1008 (8)
May 5 06:08:04 acsd: eth5: selected channel spec: 0x1008 (8)
May 5 06:08:04 acsd: acs_set_chspec: 0x1008 (8) for reason APCS_INIT
May 5 06:08:04 acsd: eth6: Selecting 5g band ACS policy
May 5 06:08:05 rc_service: ledg 2439:notify_rc restart_ledg
May 5 06:08:09 cfg_server: event: wl_chanspec_changed_action
May 5 06:08:09 cfg_server: skip event due no re
May 5 06:08:10 acsd: eth6: selected channel spec: 0xe06a (100/80)
May 5 06:08:10 acsd: eth6: Adjusted channel spec: 0xe06a (100/80)
May 5 06:08:10 acsd: eth6: selected channel spec: 0xe06a (100/80)
May 5 06:08:10 acsd: acs_set_chspec: 0xe06a (100/80) for reason APCS_INIT
May 5 06:08:11 roamast: ROAMING Start...
May 5 06:08:18 miniupnpd[2218]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:08:18 zcip client: configured 169.254.72.117
May 5 06:08:33 pppd[2300]: Timeout waiting for PADO packets
May 5 06:08:54 wlceventd: wlceventd_proc_event(527): eth6: Auth **:**:**:**:**:**, status: Successful (0), rssi:0
May 5 06:08:54 wlceventd: wlceventd_proc_event(556): eth6: Assoc **:**:**:**:**:**, status: Successful (0), rssi:-67
May 5 06:09:49 pppd[2300]: Timeout waiting for PADO packets
May 5 06:11:04 pppd[2300]: Timeout waiting for PADO packets
May 5 06:12:19 pppd[2300]: Timeout waiting for PADO packets
May 5 06:13:34 pppd[2300]: Timeout waiting for PADO packets
May 5 06:14:49 pppd[2300]: Timeout waiting for PADO packets
May 5 06:16:04 pppd[2300]: Timeout waiting for PADO packets

"Timeout waiting for PADO packets" looks like it might be the issue, will investigate further tomorrow. I'm going to leave the router and ONT powered off overnight on the off chance it helps.

My login is: [email protected]

everything else is the same on my AX88

Edit: I believe either should work though.

Edited by BuckleZ (Wed 12-Jan-22 04:41:30)

Thanks BuckleZ, helpful to know I didn't miss something in the config.

Still no luck after leaving it powered off though, getting that same error: "Timeout waiting for PADO packets". Tried with both variations of the PPoE username just in case.

I've had to switch back to the SH2 so I can work today, will dig into this again this evening. Suggestions welcome though!

From a TP-Link forum around the same problem.
"I have a PPPoE connection with my ISP (static IP address), and often after restarting the router, or whenever the PPPoE connection is restarted, the PPPoE connection fails during the negotiation phase. The router sends the "PADI" request, but never receives the "PADO" response. System Logs show "Timeout waiting for PADO packet". I've determined with the ISP technical support that the PPPoE access concentrator in that case rejects my PADI request based in the MAC address provided. If I then go into my router settings and change the WAN MAC address by 1 digit, the connection succeeds. But if I then restart my router, the same thing
happens. If I change the WAN MAC back to the original MAC address, the connection succeeds again."

Maybe if you clone the supplied router's MAC address to the ASUS it might work?

Edited by Adduxi (Wed 12-Jan-22 10:29:50)

The only setting i would consider a suspect is near the end of the second screen ...

"Enable VPN + DHCP connection"

You are using a PPPoE connection and the VPN ID is handled by the ONT it does not get to the router.

Agreed. Missed that on the setup pages from OP.

It just wants DHCP on the WAN connection.

Thank you all. Here's what I've tried, but still no joy with connecting:

- Enable VPN + DHCP connection: I had previously set to 'No'. It must have re-enabled with the factory reset. I set back to 'No', but it hasn't fixed it.

- VLAN tagging: I've tried with and without tag for VLAN 101 - I know shouldn't be necessary anyway since the ONT handles it.

- MAC address: I cloned the SH2 one and also tried changing it by 1 digit. Sadly also didn't work.

I can try leaving the ASUS connected overnight tonight, in case that somehow negotiates a connection after a certain time. Seems unlikely, but running out of ideas tbh.

Timeout. Just do a sense check and see if you can connect laptop/PC directly to the ONT. You will need to setup a PPPoE client session. Not too hard really.

I know you already have proved connectivity using the SH2 - but this proves without doubt the issue is with the new router (and not say a credential issue), which for all you know may have a firmware issue or hardware fault.