topic Re: PPPOE authentication with Plusnet FTTP not working in My Router

PPPOE authentication with Plusnet FTTP not working

witherford — Mon, 20 Feb 2023 17:43:36 GMT

Hi I wonder if someone from plusnet can help as the telephone support have been useless, the "back office" staff have said I need to take the issue to my firewall vendor however the issue isn't with the firewall 😐

Below is the issue:

it's a weird one I have a Palo alto firewall connected directly to the ONT provided by BT and I am trying to get FTTP broadband working using PPPOE, the interface on the PA-220 that is connected to the ONT (ethernet 1/1) is configured to use PPPOE however the interface does not obtain a public IP address. The username and password are correct, I can test that they are correct by logging into my plusnet account online or using the plusnet provided router and ensuring it is configured to use the username and password which is identical to the one entered on the Palo alto firewall, when using the plusnet router which I am now it works just fine.

However the logs show an authentication failure, I have also changed the password, and still no luck.

Initiate connection:

PPPoE session was initiated for user:xxxxxxxx@plusdsl.net on interface:ethernet1/1

Error:

PPPoE session failed to connect for user:xxxxxxx@plusdsl.net on interface:ethernet1/1. Reason: Failed to authenticate ourselves to peer, LCP down

I have attached a couple of packet capture screenshots, the CHAP authentication is failing for some reason, the hashed response my end is sending back to the access concentrator on the Plusnet or BT network is not matching what the access concentrator is expecting.

The access concentrator in question is: acc-aln2.nao

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Mon, 20 Feb 2023 17:41:57 GMT

Other file attached

Re: PPPOE authentication with Plusnet FTTP not working

Dan_the_Van — Mon, 20 Feb 2023 17:47:16 GMT

Have you by chance enabled VLAN 101 on your router as the is not required for the ONT.

HTH

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Mon, 20 Feb 2023 17:48:26 GMT

No, the Palo alto's do not allow you to define a VLAN for PPPOE interfaces the traffic is sent untagged.

Re: PPPOE authentication with Plusnet FTTP not working

RichardB — Mon, 20 Feb 2023 18:23:47 GMT

Hi witherford

Are any of the characters which can't be used shown in:

https://www.plus.net/help/archive/other/username-and-password-security/

used in the password?

Regards

Richard

Re: PPPOE authentication with Plusnet FTTP not working

Dan_the_Van — Mon, 20 Feb 2023 18:28:26 GMT

My thinking was also around the password makeup, although the current one works with a plusnet router.

I was going to suggest using a simple password as a test, Alpha and Numeric characters only

Dan

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Mon, 20 Feb 2023 18:40:41 GMT

It looks like the pppoe client on the pa220 may not support mschapv2 https://www.reddit.com/r/paloaltonetworks/comments/b9ar1m/help_pa220_and_pppoe_mschapv2/

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Mon, 20 Feb 2023 20:43:51 GMT

Thanks for the info however one thing I forgot to add, the same PA-220 worked fine on plusnet fibre VDSL (copper to the premises) using the same username and password, it's only as I have switched over to FTTP that it is not working.

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Tue, 21 Feb 2023 07:48:23 GMT

Ah! Im assuming you had a modem in front of the pa220 then. Was the 220 configured for pppoe in that setup ?

In which case it should have worked with no change to the configuration.

I can assure you there is no problem with pppoe on fttp,

i use a tplink er605 on my fttp connection.

Are you absolutely sure there no vlan id being set on the 220 ?

Thats the main differerence between fttc and fttp , fttc used vlan id 101 whereas fttp does not use vlan id.

Having said that , the vlan id is usually handled by the modem so even on fttc the router doesnt need it

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 09:30:58 GMT

I did have a modem yes to handle the RJ11 connectivity to the master socket as the PA-220 does not have that built in.

I agree it should work with no change to the configuration.

Yes, PPPOE worked just fine with the setup on VDSL through the modem.

Yes, the traffic is being sent without a VLAN tag, I have referred to the ethernet section of the packet payload within the packet captures and there are no 802.1Q headers anywhere.

The physical setup I am trying at the moment is:

Palo alto ethernet port 1/1 which is configured for PPPOE --> ONT RJ45 port, this to me should work just fine, both devices attempt PPPOE when connected this way as the ONT is just acting as a Layer 2 bridge to the access concentrator.

The workaround I have is:

L3 P2P link between Palo alto and Plusnet router so ethernet 1/1 configured with an IP on the 192.168.1.x range connected into LAN port 1 on the Plusnet router, the Palo Alto then performs NAT of all outbound traffic behind the one IP address which is then routed to the plusnet router which then NAT's behind it's public IP (so twice NAT)

This works fine so their is something different about the Plusnet router authenticating with the remote end vs the Palo alto and it's not the username and password, so what is it? I have a suspicion that it might be an extra security measure such as MAC address authentication.

Can I ask on your device did you have to configure a MAC address anywhere or perform any kind of MAC address spoofing?

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Tue, 21 Feb 2023 09:46:20 GMT

I have a suspicion that it might be an extra security measure such as MAC address authentication.

I can assure you there isn't. I have used a few different (third party) routers on my PN connection over the years.

Can I ask on your device did you have to configure a MAC address anywhere or perform any kind of MAC address spoofing?

No.

Attached my WAN configuration if it helps

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 09:49:39 GMT

Cheers, if that is the case then I am going to dig out and try configuring one of my cisco routers and see if that works. If the Cisco router works then it looks like it might be the firewall that is causing the problem.

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 09:50:54 GMT

Are you connected to FTTP?

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Tue, 21 Feb 2023 10:06:25 GMT

Yes, a 900/115Mb connection.

Looking back at your log screenshots for the PPP setup. It looks like its definitely failing CHAP authentication ( you can ignore my previous comment re MS_CHAP V2 )

The username it appears to be sending is 'name@plusdsl...' ?? it should be 'name@plusdsl.net' . Does it really not have the .net or is that just being dropped by the log ?

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 10:21:32 GMT

Dropped by the log, it does indeed have the full username

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 10:23:08 GMT

Debug logs from the Palo alto attached, shows authentication failure same as previous logs

2023-02-21 07:29:39.431 +0000 debug: pan_pppoe_ok_to_send(pan_pppoe_fsm.c:352): [0xffd0038c60/16][0] Ok to send, ha_state:0 (fsm state is:1) for ethernet1/1
2023-02-21 07:29:39.432 +0000 debug: pan_pppoe_send_padi(pan_pppoe_fsm.c:402): [0xffd0038c60/16][0] Sending PADI on ethernet1/1
2023-02-21 07:29:39.432 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 44 (36 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.434 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.434 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:68 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.434 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.434 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8863, Code:0x7(PADO), Sess ID:0, Len:48
2023-02-21 07:29:39.434 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1311): [0xffd0038c60/16][0] ******** Run PPPoE FSM *******
2023-02-21 07:29:39.434 +0000 debug: pan_pppoe_recv_pado(pan_pppoe_fsm.c:724): [0xffd0038c60/16][0] Received PADO on ethernet1/1
2023-02-21 07:29:39.434 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x101(PAN_PPPOE_SVC_NAME_TAG) of length:0 and value:Null
2023-02-21 07:29:39.434 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:44
2023-02-21 07:29:39.434 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x102(PAN_PPPOE_AC_NAME_TAG) of length:12 and value:acc-aln2.nao
2023-02-21 07:29:39.435 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:28
2023-02-21 07:29:39.435 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x103(PAN_PPPOE_HOST_UNIQ_NAME_TAG) of length:4 and value:g<9B><AE>i
2023-02-21 07:29:39.435 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:20
2023-02-21 07:29:39.435 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x104(PAN_PPPOE_AC_COOKIE_TAG) of length:16 and value:4<ED><AC><CD><CC>Y<A8><A2><E2>^RESC0{<F1>}q
2023-02-21 07:29:39.435 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:0
2023-02-21 07:29:39.435 +0000 debug: pan_pppoe_send_padr(pan_pppoe_fsm.c:579): [0xffd0038c60/16][0] Sending PADR on ethernet1/1
2023-02-21 07:29:39.435 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 64 (56 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.437 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.437 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.437 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:60 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.437 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.437 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8863, Code:0x65(PADS), Sess ID:4085, Len:12
2023-02-21 07:29:39.437 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1311): [0xffd0038c60/16][0] ******** Run PPPoE FSM *******
2023-02-21 07:29:39.437 +0000 debug: pan_pppoe_recv_pads(pan_pppoe_fsm.c:846): [0xffd0038c60/16][0] Received PADS on ethernet1/1
2023-02-21 07:29:39.437 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x101(PAN_PPPOE_SVC_NAME_TAG) of length:0 and value:Null
2023-02-21 07:29:39.437 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:8
2023-02-21 07:29:39.437 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:260): Retrieved tag:0x103(PAN_PPPOE_HOST_UNIQ_NAME_TAG) of length:4 and value:Z<AF>^R+
2023-02-21 07:29:39.438 +0000 debug: parse_pppoe_tags(pan_pppoe_fsm.c:261): remaining:0
2023-02-21 07:29:39.438 +0000 debug: pan_pppoe_recv_pads(pan_pppoe_fsm.c:905): [0xffd0038c60/16][0] >>>>> PPPoE CONNECTED ON: ethernet1/1, STARTING LCP <<<<<<
2023-02-21 07:29:39.438 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP SENT: [LCP ConfReq id=0x1 <magic 0xb4d8b7f4>]
2023-02-21 07:29:39.438 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 40 (32 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.481 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.481 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.481 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:60 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.481 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.481 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8864, Code:0x0(PPP SESS), Sess ID:4085, Len:21
2023-02-21 07:29:39.481 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1330): [0xffd0038c60/16][0] ... Run PPP FSM ...
2023-02-21 07:29:39.482 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP RCVD: [LCP ConfReq id=0x5e <mru 1492> <auth chap MD5> <magic 0x56884b49>]
2023-02-21 07:29:39.482 +0000 debug: log_write(ppp/utils.c:679): lcp_reqci: returning CONFACK.
2023-02-21 07:29:39.482 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP SENT: [LCP ConfAck id=0x5e <mru 1492> <auth chap MD5> <magic 0x56884b49>]
2023-02-21 07:29:39.482 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 49 (41 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.482 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.482 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.482 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:60 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.482 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.482 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8864, Code:0x0(PPP SESS), Sess ID:4085, Len:12
2023-02-21 07:29:39.482 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1330): [0xffd0038c60/16][0] ... Run PPP FSM ...
2023-02-21 07:29:39.482 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP RCVD: [LCP ConfAck id=0x1 <magic 0xb4d8b7f4>]
2023-02-21 07:29:39.483 +0000 debug: log_write(ppp/utils.c:679): ho->mru:1492, wo->mru:1492, go->mru:1492

2023-02-21 07:29:39.483 +0000 debug: log_write(ppp/utils.c:679): MTU: final:1492, mru:1492, mtu:1492, allow mru:16384

2023-02-21 07:29:39.483 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP SENT: [LCP EchoReq id=0x0 magic=0xb4d8b7f4]
2023-02-21 07:29:39.483 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 38 (30 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.483 +0000 debug: ppp_get_user_name(pan_ppp_fsm.c:396): [0xffd0038c60/16][0] >>>>> LCP DONE ON: ethernet1/1, STARTING AUTH <<<<<<
2023-02-21 07:29:39.483 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.483 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.483 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:95 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.483 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.483 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8864, Code:0x0(PPP SESS), Sess ID:4085, Len:75
2023-02-21 07:29:39.483 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1330): [0xffd0038c60/16][0] ... Run PPP FSM ...
2023-02-21 07:29:39.484 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP RCVD: [CHAP Challenge id=0x1 <b320700d7eb72daa2cbf9b5968956b53275ff3a6630956568246bd93a1842f55a41fe123560f4d824f695bb7fec70b26277ecc0b88a3e08a>, name = "acc-aln2.nao"]
2023-02-21 07:29:39.484 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP SENT: [CHAP Response id=0x1 <a62e7af087ed4446d2d9b5ae8258fe61>, name = "username@plusdsl.net"]
2023-02-21 07:29:39.484 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 75 (67 on wire) bytes of PPPoE pkt to DP on socket 6
2023-02-21 07:29:39.491 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.491 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.491 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:60 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.491 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.491 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8864, Code:0x0(PPP SESS), Sess ID:4085, Len:10
2023-02-21 07:29:39.491 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1330): [0xffd0038c60/16][0] ... Run PPP FSM ...
2023-02-21 07:29:39.492 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP RCVD: [LCP EchoRep id=0x0 magic=0x56884b49]
2023-02-21 07:29:39.500 +0000 debug: pan_ppp_get_pppoe_fsm(pan_ppp_fsm.c:108): Found ppp_fsm_info[0] unit for ifindex: 16, pppoe_fsm 0xffd0038c60
2023-02-21 07:29:39.500 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:185):
2023-02-21 07:29:39.500 +0000 debug: pan_pppoed_select_callback(pan_pppoe_thread.c:189): [0xffd0038c60]/16] len:60 ---------[Received a PPPoE/PPP ctrl packet]--------------
2023-02-21 07:29:39.500 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1298): [0xffd0038c60/16][0] Received PPPoE pkt from AC mac: f8:13:08:41:31:03 on: ethernet1/1
2023-02-21 07:29:39.500 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1303): [0xffd0038c60/16][0] etype:0x8864, Code:0x0(PPP SESS), Sess ID:4085, Len:33
2023-02-21 07:29:39.500 +0000 debug: pan_pppoe_recv_pkt(pan_pppoe_fsm.c:1330): [0xffd0038c60/16][0] ... Run PPP FSM ...
2023-02-21 07:29:39.501 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP RCVD: [CHAP Failure id=0x1 "CHAP authentication failure"]
2023-02-21 07:29:39.501 +0000 debug: log_write(ppp/utils.c:679): CHAP authentication failed: CHAP authentication failure
2023-02-21 07:29:39.501 +0000 debug: log_write(ppp/utils.c:679): CHAP authentication failed
2023-02-21 07:29:39.502 +0000 debug: log_write(ppp/utils.c:679): [0xffd0038c60/16][0] PPP SENT: [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
2023-02-21 07:29:39.502 +0000 debug: pan_pppoe_output(pan_pppoe_thread.c:1048): [0xffd0038c60/16][0] Sent 74 (66 on wire) bytes of PPPoE pkt to DP on socket 6

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Tue, 21 Feb 2023 10:36:29 GMT

Oh well, worth a try!.

It definitely looks like an authentication problem. It's going to be difficult to establish whether the PA is sending the correct username / password , even with packet captures , since its going to be MD5 hashed with a random number seed from the CHAP challenge

I'd try the Cisco if possible...

Re: PPPOE authentication with Plusnet FTTP not working

bobpullen — Tue, 21 Feb 2023 10:50:39 GMT

If it helps, I've checked our RADIUS logs for a period of time during which I suspect you were tinkering (~5.15pm on 16/02).

I can see no activity at all in the logs for roughly an hour following the initial disconnection, failed or otherwise.

If my assumption around timings is correct, then that suggests that whatever is happening, the attempts aren't even reaching the place where account validation takes place.

Re: PPPOE authentication with Plusnet FTTP not working

witherford — Tue, 21 Feb 2023 10:56:19 GMT

Hi Bob that is helpful to know thanks and yes on the 16th I was tinkering, can you check the logs for this morning please as I was troubleshooting again from around 06:00AM and onwards

Re: PPPOE authentication with Plusnet FTTP not working

MisterW — Tue, 21 Feb 2023 11:00:20 GMT

@bobpullen thanks for the input, what about any RADIUS logs from today , corresponding to the time of the debug log above ?

Also the log above is showing a CHAP challenge from "acc-aln2.nao" , is that not a PN/BT concentrator ?