PPPoE fails with HANGUP after successful authentication

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi! I'm using OpenWRT for the first time, and I have troubles setting up PPPoE to get Internet.

By default, I get 'wan' and 'wan6' interfaces, with DHCP and DHCPv6 protocols.

Default config 
config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd6a:4d13:c8f2::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'

To setup PPPoE, I'm switching 'wan' to 'PPPoE' protocol and set the usename and password. My configuration switches to this:

config interface 'wan'
	option device 'wan'
	option proto 'pppoe'
	option username '...'
	option password '...'
	option ipv6 'auto'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'

But in the UI, I get Unknown error (HANGUP) error instead of an IP.

So I reboot the system, and now I seem to get IPv4 and IPv6 addresses almost immediately followed by the same Unknown error (HANGUP) error.

Looking at the system logs, it seems like I succesfully authenticate:

Wed Nov 22 07:26:10 2023 daemon.info pppd[20045]: CHAP authentication succeeded
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: CHAP authentication succeeded
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: peer from calling number 84:03:28:62:F8:68 authorized

And receive my IP addresses:

Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: local  IP address 10.255.148.179
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: remote IP address 10.1.1.1
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: primary   DNS address 193.27.209.10
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: secondary DNS address 193.27.209.5
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: local  LL address fe80::7c0a:db7a:24a3:4289
Wed Nov 22 07:26:10 2023 daemon.notice pppd[20045]: remote LL address fe80::8603:28ff:fe62:f868

But then this happens:

Wed Nov 22 07:26:11 2023 daemon.info pppd[20045]: LCP terminated by peer
Wed Nov 22 07:26:11 2023 daemon.info pppd[20045]: Connect time 0.0 minutes.
Wed Nov 22 07:26:11 2023 daemon.info pppd[20045]: Sent 200 bytes, received 8 bytes.

As well as this:

Wed Nov 22 07:26:11 2023 daemon.notice pppd[20045]: Modem hangup
Wed Nov 22 07:26:11 2023 daemon.notice pppd[20045]: Connection terminated.

Followed by:

Wed Nov 22 07:26:11 2023 daemon.info pppd[20045]: Exit.
Wed Nov 22 07:26:11 2023 daemon.notice netifd: Interface 'wan' is now down

And it seems to reboot the interface to try everything again.

I would appreciate any help to get this working, thanks in advance.

Shortened system log 
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan_6' is setting up now
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: LCP terminated by peer
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: Connect time 0.0 minutes.
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: Sent 152 bytes, received 8 bytes.
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan_6' is disabled
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Wed Nov 22 07:25:20 2023 daemon.notice pppd[16666]: Modem hangup
Wed Nov 22 07:25:20 2023 daemon.notice pppd[16666]: Connection terminated.
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: Connect time 0.0 minutes.
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: Sent 152 bytes, received 8 bytes.
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Wed Nov 22 07:25:20 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan_6' is now down
Wed Nov 22 07:25:20 2023 daemon.info pppd[16666]: Exit.
Wed Nov 22 07:25:20 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan' is now down
Wed Nov 22 07:25:20 2023 daemon.notice netifd: Interface 'wan' is setting up now
Wed Nov 22 07:25:20 2023 daemon.info pppd[16781]: Plugin pppoe.so loaded.
Wed Nov 22 07:25:20 2023 daemon.info pppd[16781]: PPPoE plugin from pppd 2.4.9
Wed Nov 22 07:25:21 2023 daemon.notice pppd[16781]: pppd 2.4.9 started by root, uid 0
Wed Nov 22 07:25:21 2023 daemon.info pppd[16781]: PPP session is 5875
Wed Nov 22 07:25:21 2023 daemon.warn pppd[16781]: Connected to 84:03:28:62:f8:68 via interface wan
Wed Nov 22 07:25:21 2023 kern.info kernel: [  214.536099] pppoe-wan: renamed from ppp0
Wed Nov 22 07:25:21 2023 daemon.info pppd[16781]: Renamed interface ppp0 to pppoe-wan
Wed Nov 22 07:25:21 2023 daemon.info pppd[16781]: Using interface pppoe-wan
Wed Nov 22 07:25:21 2023 daemon.notice pppd[16781]: Connect: pppoe-wan <--> wan
Wed Nov 22 07:25:21 2023 daemon.warn odhcpd[1580]: No default route present, overriding ra_lifetime!
Wed Nov 22 07:25:24 2023 daemon.info pppd[16781]: CHAP authentication succeeded
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: CHAP authentication succeeded
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: peer from calling number 84:03:28:62:F8:68 authorized
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: local  IP address 10.255.148.29
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: remote IP address 10.1.1.1
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: primary   DNS address 193.27.209.10
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: secondary DNS address 193.27.209.5
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: local  LL address fe80::24b1:229b:8655:39b8
Wed Nov 22 07:25:24 2023 daemon.notice pppd[16781]: remote LL address fe80::8603:28ff:fe62:f868
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Interface 'wan' is now up
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.10#53
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.5#53
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Nov 22 07:25:24 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Interface 'wan_6' is enabled
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity
Wed Nov 22 07:25:24 2023 daemon.notice netifd: Interface 'wan_6' is setting up now
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: LCP terminated by peer
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: Connect time 0.1 minutes.
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: Sent 200 bytes, received 8 bytes.
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan_6' is disabled
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Wed Nov 22 07:25:25 2023 daemon.notice pppd[16781]: Modem hangup
Wed Nov 22 07:25:25 2023 daemon.notice pppd[16781]: Connection terminated.
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: Connect time 0.1 minutes.
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: Sent 200 bytes, received 8 bytes.
Wed Nov 22 07:25:25 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Wed Nov 22 07:25:25 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov 22 07:25:25 2023 daemon.info pppd[16781]: Exit.
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan' is now down
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan' is setting up now
Wed Nov 22 07:25:25 2023 daemon.info pppd[17082]: Plugin pppoe.so loaded.
Wed Nov 22 07:25:25 2023 daemon.info pppd[17082]: PPPoE plugin from pppd 2.4.9
Wed Nov 22 07:25:25 2023 daemon.notice pppd[17082]: pppd 2.4.9 started by root, uid 0
Wed Nov 22 07:25:25 2023 daemon.info pppd[17082]: PPP session is 1796
Wed Nov 22 07:25:25 2023 daemon.warn pppd[17082]: Connected to 84:03:28:62:f8:68 via interface wan
Wed Nov 22 07:25:25 2023 kern.info kernel: [  218.866928] pppoe-wan: renamed from ppp0
Wed Nov 22 07:25:25 2023 daemon.err odhcp6c[17037]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 07:25:25 2023 daemon.warn odhcpd[1580]: No default route present, overriding ra_lifetime!
Wed Nov 22 07:25:25 2023 daemon.info pppd[17082]: Renamed interface ppp0 to pppoe-wan
Wed Nov 22 07:25:25 2023 daemon.info pppd[17082]: Using interface pppoe-wan
Wed Nov 22 07:25:25 2023 daemon.err odhcp6c[17037]: Failed to send RS (Network unreachable)
Wed Nov 22 07:25:25 2023 daemon.notice pppd[17082]: Connect: pppoe-wan <--> wan
Wed Nov 22 07:25:25 2023 daemon.notice netifd: Interface 'wan_6' is now down
Wed Nov 22 07:25:26 2023 daemon.warn odhcpd[1580]: No default route present, overriding ra_lifetime!
Wed Nov 22 07:25:28 2023 daemon.info pppd[17082]: CHAP authentication succeeded
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: CHAP authentication succeeded
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: peer from calling number 84:03:28:62:F8:68 authorized
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: local  LL address fe80::707b:f603:e2bf:3608
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: remote LL address fe80::8603:28ff:fe62:f868
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: local  IP address 10.255.149.145
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: remote IP address 10.1.1.1
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: primary   DNS address 193.27.209.10
Wed Nov 22 07:25:28 2023 daemon.notice pppd[17082]: secondary DNS address 193.27.209.5
Wed Nov 22 07:25:28 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Nov 22 07:25:28 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Wed Nov 22 07:25:28 2023 daemon.notice netifd: Interface 'wan' is now up
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.10#53
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.5#53
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Nov 22 07:25:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' is enabled
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' is setting up now
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: LCP terminated by peer
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: Connect time 0.0 minutes.
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: Sent 124 bytes, received 8 bytes.
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' is disabled
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Wed Nov 22 07:25:29 2023 daemon.notice pppd[17082]: Modem hangup
Wed Nov 22 07:25:29 2023 daemon.notice pppd[17082]: Connection terminated.
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: Connect time 0.0 minutes.
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: Sent 124 bytes, received 8 bytes.
Wed Nov 22 07:25:29 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Nov 22 07:25:29 2023 daemon.err odhcp6c[17342]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 07:25:29 2023 daemon.err odhcp6c[17342]: Failed to send RS (Network unreachable)
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Wed Nov 22 07:25:29 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov 22 07:25:29 2023 daemon.info pppd[17082]: Exit.
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan' is now down
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan' is setting up now
Wed Nov 22 07:25:29 2023 daemon.info pppd[17387]: Plugin pppoe.so loaded.
Wed Nov 22 07:25:29 2023 daemon.info pppd[17387]: PPPoE plugin from pppd 2.4.9
Wed Nov 22 07:25:29 2023 daemon.notice pppd[17387]: pppd 2.4.9 started by root, uid 0
Wed Nov 22 07:25:29 2023 daemon.info pppd[17387]: PPP session is 1796
Wed Nov 22 07:25:29 2023 daemon.warn pppd[17387]: Connected to 84:03:28:62:f8:68 via interface wan
Wed Nov 22 07:25:29 2023 kern.info kernel: [  223.127523] pppoe-wan: renamed from ppp0
Wed Nov 22 07:25:29 2023 daemon.info pppd[17387]: Renamed interface ppp0 to pppoe-wan
Wed Nov 22 07:25:29 2023 daemon.info pppd[17387]: Using interface pppoe-wan
Wed Nov 22 07:25:29 2023 daemon.notice pppd[17387]: Connect: pppoe-wan <--> wan
Wed Nov 22 07:25:29 2023 daemon.warn odhcpd[1580]: No default route present, overriding ra_lifetime!
Wed Nov 22 07:25:29 2023 daemon.err odhcp6c[17342]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 07:25:29 2023 daemon.notice netifd: Interface 'wan_6' is now down
2

I've enabled the debug option in /etc/ppp/options, and now I get some more information in the logs, like:

Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: sent [LCP TermAck id=0x9f]
Wed Nov 22 08:01:53 2023 daemon.notice pppd[16773]: Modem hangup
Wed Nov 22 08:01:53 2023 daemon.notice pppd[16773]: Connection terminated.

Not that I know what it means.

Debug logs (censored some numbers) 
Wed Nov 22 08:01:53 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Wed Nov 22 08:01:53 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: Script /lib/netifd/ppp-down started (pid 16855)
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: sent [LCP TermAck id=0x9f]
Wed Nov 22 08:01:53 2023 daemon.notice pppd[16773]: Modem hangup
Wed Nov 22 08:01:53 2023 daemon.notice pppd[16773]: Connection terminated.
Wed Nov 22 08:01:53 2023 daemon.info pppd[16773]: Connect time 0.0 minutes.
Wed Nov 22 08:01:53 2023 daemon.info pppd[16773]: Sent 124 bytes, received 8 bytes.
Wed Nov 22 08:01:53 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Nov 22 08:01:53 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Wed Nov 22 08:01:53 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: Script /lib/netifd/ppp-down finished (pid 16853), status = 0x1
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: Waiting for 1 child processes...
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]:   script /lib/netifd/ppp-down, pid 16855
Wed Nov 22 08:01:53 2023 daemon.debug pppd[16773]: Script /lib/netifd/ppp-down finished (pid 16855), status = 0x1
Wed Nov 22 08:01:53 2023 daemon.info pppd[16773]: Exit.
Wed Nov 22 08:01:53 2023 daemon.notice netifd: Interface 'wan' is now down
Wed Nov 22 08:01:53 2023 daemon.notice netifd: Interface 'wan' is setting up now
Wed Nov 22 08:01:54 2023 daemon.info pppd[16893]: Plugin pppoe.so loaded.
Wed Nov 22 08:01:54 2023 daemon.info pppd[16893]: PPPoE plugin from pppd 2.4.9
Wed Nov 22 08:01:54 2023 daemon.err odhcp6c[16848]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 08:01:54 2023 daemon.err odhcp6c[16848]: Failed to send RS (Network unreachable)
Wed Nov 22 08:01:54 2023 daemon.notice netifd: Interface 'wan_6' is now down
Wed Nov 22 08:01:54 2023 daemon.notice pppd[16893]: pppd 2.4.9 started by root, uid 0
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  dst ff:ff:ff:ff:ff:ff  src d4:5d:64:86:3e:44
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  [service-name] [host-uniq  fd 41 00 00]
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 40
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  dst d4:5d:64:86:3e:44  src 84:03:28:62:f8:68
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  [AC-name J960] [host-uniq  fd 41 00 00] [service-name] [AC-cookie  8c 19 5d f2 3a 02 f0 dd e2 99 58 97 56 1d 63 18]
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: Send PPPOE Discovery V1T1 PADR session 0x0 length 32
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  dst 84:03:28:62:f8:68  src d4:5d:64:86:3e:44
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  [service-name] [host-uniq  fd 41 00 00] [AC-cookie  8c 19 5d f2 3a 02 f0 dd e2 99 58 97 56 1d 63 18]
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: Recv PPPOE Discovery V1T1 PADS session 0x115f length 40
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  dst d4:5d:64:86:3e:44  src 84:03:28:62:f8:68
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]:  [service-name] [host-uniq  fd 41 00 00] [AC-name J960] [AC-cookie  8c 19 5d f2 3a 02 f0 dd e2 99 58 97 56 1d 63 18]
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: PADS: Service-Name: ''
Wed Nov 22 08:01:54 2023 daemon.info pppd[16893]: PPP session is 4447
Wed Nov 22 08:01:54 2023 daemon.warn pppd[16893]: Connected to 84:03:28:62:f8:68 via interface wan
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: using channel 69
Wed Nov 22 08:01:54 2023 kern.info kernel: [  211.606334] pppoe-wan: renamed from ppp0
Wed Nov 22 08:01:54 2023 daemon.info pppd[16893]: Renamed interface ppp0 to pppoe-wan
Wed Nov 22 08:01:54 2023 daemon.info pppd[16893]: Using interface pppoe-wan
Wed Nov 22 08:01:54 2023 daemon.notice pppd[16893]: Connect: pppoe-wan <--> wan
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x26b6abfe>]
Wed Nov 22 08:01:54 2023 daemon.debug pppd[16893]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x26b6abfe>]
Wed Nov 22 08:01:55 2023 daemon.warn odhcpd[1579]: No default route present, overriding ra_lifetime!
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [LCP ConfReq id=0x38 <mru 1492> <auth chap MD5> <magic 0x6bc0c3e0>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [LCP ConfAck id=0x38 <mru 1492> <auth chap MD5> <magic 0x6bc0c3e0>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [LCP EchoReq id=0x0 magic=0x26b6abfe]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [CHAP Challenge id=0xe5 <b7b1d *long number* c69c056a>, name = "J***S"]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [CHAP Response id=0xe5 <40b7de55 *long number* d1574>, name = "300***54"]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [LCP EchoRep id=0x0 magic=0x6bc0c3e0]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [CHAP Success id=0xe5 ""]
Wed Nov 22 08:01:57 2023 daemon.info pppd[16893]: CHAP authentication succeeded
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: CHAP authentication succeeded
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: peer from calling number 84:03:28:62:F8:68 authorized
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [IPV6CP ConfReq id=0x1 <addr fe80::4ddb:58b1:2152:1c85>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [IPCP ConfReq id=0xd9 <addr 10.1.1.1>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [IPCP ConfAck id=0xd9 <addr 10.1.1.1>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [IPCP ConfNak id=0x1 <addr 10.255.149.34> <ms-dns1 193.27.209.10> <ms-dns2 193.27.209.5>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [IPCP ConfReq id=0x2 <addr 10.255.149.34> <ms-dns1 193.27.209.10> <ms-dns2 193.27.209.5>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [IPV6CP ConfReq id=0x20 <addr fe80::8603:28ff:fe62:f868>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: sent [IPV6CP ConfAck id=0x20 <addr fe80::8603:28ff:fe62:f868>]
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [IPCP ConfAck id=0x2 <addr 10.255.149.34> <ms-dns1 193.27.209.10> <ms-dns2 193.27.209.5>]
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: local  IP address 10.255.149.34
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: remote IP address 10.1.1.1
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: primary   DNS address 193.27.209.10
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: secondary DNS address 193.27.209.5
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-up started (pid 17105)
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: rcvd [IPV6CP ConfAck id=0x1 <addr fe80::4ddb:58b1:2152:1c85>]
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: local  LL address fe80::4ddb:58b1:2152:1c85
Wed Nov 22 08:01:57 2023 daemon.notice pppd[16893]: remote LL address fe80::8603:28ff:fe62:f868
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp6-up started (pid 17106)
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Interface 'wan' is now up
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.10#53
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using nameserver 193.27.209.5#53
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Nov 22 08:01:57 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-up finished (pid 17105), status = 0x1
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Interface 'wan_6' is enabled
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity
Wed Nov 22 08:01:57 2023 daemon.notice netifd: Interface 'wan_6' is setting up now
Wed Nov 22 08:01:57 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp6-up finished (pid 17106), status = 0x0
Wed Nov 22 08:01:58 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: rcvd [LCP TermReq id=0x39]
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: LCP terminated by peer
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: Connect time 0.1 minutes.
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: Sent 276 bytes, received 8 bytes.
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-down started (pid 17164)
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Interface 'wan_6' is disabled
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-down started (pid 17166)
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: sent [LCP TermAck id=0x39]
Wed Nov 22 08:01:58 2023 daemon.notice pppd[16893]: Modem hangup
Wed Nov 22 08:01:58 2023 daemon.notice pppd[16893]: Connection terminated.
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: Connect time 0.1 minutes.
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: Sent 276 bytes, received 8 bytes.
Wed Nov 22 08:01:58 2023 daemon.err odhcp6c[17153]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 08:01:58 2023 daemon.err odhcp6c[17153]: Failed to send RS (Network unreachable)
Wed Nov 22 08:01:58 2023 daemon.err odhcp6c[17153]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Wed Nov 22 08:01:58 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-down finished (pid 17164), status = 0x1
Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: Script /lib/netifd/ppp-down finished (pid 17166), status = 0x1
Wed Nov 22 08:01:58 2023 daemon.info pppd[16893]: Exit.
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Interface 'wan_6' is now down
Wed Nov 22 08:01:58 2023 daemon.notice netifd: Interface 'wan' is now down
3

FYI, my router is connected with twisted pair to an Access Point provided by ISP, which is connected by a fiber cable. I'm also in a multi-NAT environment, so I don't get a public IP, but a 100.100.xx.xx one.

4

Your ISP is sending you a termionation request:

Wed Nov 22 08:01:58 2023 daemon.debug pppd[16893]: rcvd [LCP TermReq id=0x39]

your OpenWrt PPPoE client is simply following that request. Maybe you can ask your ISP's technicians?

1 Like
5

Thanks for the answer. I have another router still on the OEM firmware, and it works just fine (as it did on this router's OEM firmware). Is there a way to troubleshoot this without contacting the technicians? As it seems that the problem is with my configuration compared to a typical one. I'm not sure if they will be happy troubleshooting people with custom ROMs.

6

You could try to get a packet capture for the PPPoE connection establishment from the ISP router and see what happens on the wire there... could be something like your ISP using a specific host-uniq number or similar...
At least Fritzbox modemrouters allow to run a packet capture, not sure about your ISPs devices, otherwise you might need to put a transparent bridge between the ISP router and ISP access point to get a packet capture...

7

I don't actually have an ISP router, they only provided the access point. I have an Asus RT-AC750 with the default firmware, and its PPPoE configuration looks as follows:

image
image763Ɨ532 24.4 KB

Alt text 
"Account Settings" table
PPP Username ā€” censored
Password ā€” censored
Disconnect after time of inactivity (in seconds) ā€” 0
MTU ā€” 1492
MRU ā€” 1492
Service Name ā€” empty
Access Concentrator Name ā€” empty
Host-Uniq (Hexadecimal) ā€” empty
Internet Detection ā€” PPP Echo
PPP Echo Interval ā€” 6
PPP Echo Max Failures ā€” 10
Additional pppd options ā€” empty
8

P.S. I tried setting MTU to the same value as on the screenshot, as well as LCP Echo Interval and LCP Echo Max Failures to the values of PPP counterparts on the screenshot. But this only added the following warning:

Wed Nov 22 10:43:46 2023 daemon.err pppd[4662]: Interface wan has MTU of 1492 -- should be at least 1500.
Wed Nov 22 10:43:46 2023 daemon.err pppd[4662]: This may cause serious connection problems.

I don't see the option to set MRU, though

9

obviously not using zeoip0 as dev.

10

Thanks. Set that as well, but it didn't help.

Edit ā€” now that I look at previous logs, it was already set to 1492, as per screenshot.

11

On the ethernet interface you need MTU1500, as the PPPoE header(s) are part of the ethernet payload, the MRU 1492 is basically the effective MTU for traffic between the ISP's PPPoE servers and the internet... I think MRU is deduced automatically from interface MTU, and since the interface MTU is 1500 by default the MRU = 1500 -8, as the PPPoE overhead sums up to 8 bytes.
OpenWrt then uses MSS clamping for TCP connections over such a link...

It stands to hope that someday ISPs will do away with PPPoE (not so much because of the 8 byte overhead and reduced effective internet MTU, and more because PPPoE en/decapsulation is pretty CPU intensive), but that day is not today.

12

After carefully reading paper with instructions left by a technician, it turned out that my ISP has a limit for 3 MAC addresses, and I have spent it. I called the support, and they cleared the list, and now everything works. Thanks everyone for the help!

3 Likes
13

That brings back memories... I had a single ISP doing that, but that was in 2009 so I had completely forgotten about this...

1 Like
14

could have cloned one of the old MACs too, but it's tricky, if you're not aware of the limit.

1 Like
15

You would guess an ISP to implement some automatic age-out of MACs not seen in a while to cut short on avoidable support calls... or offer a self help website where customers can reset that limit...

16

yup,
that's what my ISP does, they list all MACs known to them, and asks me to select
the one I'd like to have assigned an IP.

1 Like
17

My ISP does not care for my MAC, using PPPoE they simply enforce a single session only and that is that (in addition they have the ID of the DSLAM port, aka the lineID).

With DHCP it makes some mild sense to introduce MAC locking, but with PPPoE that IMHO more pain than gain... yet it is not a totally uncommon configuration, so I a curius about its justification...

18

getting OT, I guess.

here MAC = public v4 IP, so there's some logic behind the restriction, since they don't have an infinite amount of IPs.

also, I'm not on PPPoE.

1 Like
19

OT indeed, sorry.
Yes, my point is that for PPPoE a MAC lock is a bit like belt and suspenders, as one can simply limit the number of concurrently allowed PPPoE sessions per credential tupel, while for DHCP a MAC lock makes more sense exactly for your one-IPv4-per-MAC policy...
But even then the lock could be reduced to X concurrent MACs instead of X MACs over the whole duration of a contract. I guess likely X is selected such that most users never exhaust it and so the support effort is negligible?

20

I believe they mentioned on the call a possibility of managing MAC addresses through their website, but I didn't bother to check it.