Issues with PPPoE on Flint 2 (GL-MT6000)

kryoz · December 4, 2023, 12:05pm

Hi there!
I have been trying to set up my Flint 2 to be my main router at home with no success. I have a fiber connection with a Media converter from my service provider, meaning I get my connection via regular ethernet. My current router is a Beryl AX and it works great with the PPPoE configuration required by the ISP via the GL.iNET UI.

Here are my current (working) settings in the Beryl:

User: XXXXX@ISP
Password: ********
VLAN ID: 10

Here is what I tried with the Flint 2:

Same settings as above via GL.iNET UI [Wan1 port] - not working
Same settings as above via LuCI (eth1.10) [Wan1 port] - not working
Backed up OpenWRT Beryl settings in LuCI and restored in Flint 2 [Wan1 port] - worked on the first attempt, broke wireless and other interfaces, other attempts after restoring firmware with Uboot failed
Copied Beryl MAC address to Flint 2 MAC address [Wan1 port] - not working
Mirrored Beryl OpenWRT configuration for networking and firewall under /etc/config adapting the devices according to Flint 2 - not working
Tried 1 and 2 on Wan/Lan port [Wan2 port] configured for WAN - not working
Tried 1 reverting the firmware to 4.5.0 - not working
Restarted the ISP modem as instructed by GL.iNET troubleshooting - not working
Contacted my ISP and confirmed I am allowed 3 devices simultaneously on PPPoE (Confirmed by linking the ISP router and OpenWRT VM instance, both working; the total number of MAC addresses exceeds 3 as I connected the interface to other devices in the past)

Based on the above, I suspect something may be wrong with the firmware, but I am looking for others who may have been successful with connecting the Flint 2 via PPPoE with VLAN to exclude some bizarre device malfunction (DHCP connection works fine so I see no reason for a hardware defect).

Of course, if you can think of other solutions I can try, please go ahead.

I am using factory firmware version (4.5.2) in the Flint 2, GL.iNET released 4.5.3 recently and I haven’t tried that one yet, but the release notes do only mention some PPPoE fixes in ipv6 native mode, but I am using ipv4 on my Beryl, so it may not impact - I will update nonetheless and try and keep you posetd.

Thank you for your input.

admon · December 4, 2023, 12:11pm

May you share the logs with us?

xize11 · December 4, 2023, 4:17pm

hmm your isp hasn’t doing a name change recently?

Just asking because some time ago I had a similar situation, but because they changed their brand from T-mobile to Odido in the Netherlands, instead of vlan 640 and 300 I was forced to use iPoE it took me some time figuring out what that was, but they made it simplier by just a dhcp request, also for iptv.

Besides logs, the isp may be also relevant

admon · December 4, 2023, 5:37pm

I can confirm that there is something odd with the PPPoE connection. When I restart my Flint2 the PPPoE will fail multiple times.

Have to reset it by open the config and save it.
Not sure yet why, will further troubleshoot.

kryoz · December 5, 2023, 3:11pm

Thank you for your input.

ISP did not change its name recently.

PPPoE is now able to connect after the update to firmware version 4.5.3. I am not seeing issues at this stage (just did the update and rebooted a couple of times).

Will let the router run for a while and come back if any odd behavior is detected. I will deploy the router as the main router later this week and see if the PPPoE connection throws any issues.

I added the system & kernel logs attached (not sure what is the best way to share).
(I have tried to hide sensitive information, sorry if that makes your life harder - I may be a bit overzealous)
logs.zip (14.4 KB)

Jounouchi · December 10, 2023, 1:21am

My scenario is difference, I disable IPv6 but get below issue, however after free retry attempts it reconnect.

Fri Dec 8 19:13:00 2023 daemon.notice pppd[7525]: Connect: pppoe-wan ↔ eth1.500
Fri Dec 8 19:13:03 2023 daemon.notice pppd[7525]: PAP authentication succeeded
Fri Dec 8 19:13:03 2023 daemon.notice pppd[7525]: peer from calling number XX:XX:XX:XX:XX:XX authorized
Fri Dec 8 19:13:03 2023 daemon.err pppd[7525]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 3011)
Fri Dec 8 19:13:03 2023 daemon.warn pppd[7525]: cif6addr: ioctl(SIOCDIFADDR): No such address
Fri Dec 8 19:13:03 2023 daemon.info pppd[7525]: LCP terminated by peer
Fri Dec 8 19:13:03 2023 daemon.notice pppd[7525]: Modem hangup
Fri Dec 8 19:13:03 2023 daemon.notice pppd[7525]: Connection terminated.
Fri Dec 8 19:13:03 2023 daemon.info pppd[7525]: Connect time 0.2 minutes.
Fri Dec 8 19:13:03 2023 daemon.info pppd[7525]: Sent 82 bytes, received 60 bytes.
Fri Dec 8 19:13:03 2023 daemon.info pppd[7525]: Exit.

kryoz · December 10, 2023, 5:49am

On my end, PPPoE issues seem to have disappeared for the most part after the latest firmware update. Have you tried bumping the version to 4.5.3?

Logs do not show any error/disconnect and the connection has been stable even after rebooting the router a couple of times.

kryoz · December 15, 2023, 12:24pm

Hi all,

I updated the firmware to 4.5.4 and the behavior I was seeing at the beginning is back. I leave the logs below - I have since rolled back to 4.5.3 and got PPPoE working again with no issue.

Something is happening here but is above my knowledge level. I noticed a difference in the interface and IPv6 being used to join mDNS multicast in the logs - maybe that is related to the issue. When the connection fails the router uses eth1.IPv6, while when it succeeds it uses pppoe-wan.IPv6 with a different IPv6 address.

Fri Dec 15 12:37:48 2023 daemon.notice netifd: Network device 'eth1' link is up
Fri Dec 15 12:37:48 2023 daemon.notice netifd: VLAN 'eth1.10' link is up
Fri Dec 15 12:37:48 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Dec 15 12:37:48 2023 daemon.notice netifd: Interface 'wan' is setting up now
Fri Dec 15 12:37:48 2023 kern.info kernel: [65461.682707] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Fri Dec 15 12:37:48 2023 kern.info kernel: [65461.691007] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Fri Dec 15 12:37:48 2023 daemon.info pppd[2135]: Plugin pppoe.so loaded.
Fri Dec 15 12:37:48 2023 daemon.info pppd[2135]: PPPoE plugin from pppd 2.4.9
Fri Dec 15 12:37:49 2023 daemon.notice pppd[2135]: pppd 2.4.9 started by root, uid 0
Fri Dec 15 12:37:49 2023 daemon.info pppd[2135]: PPP session is 1
Fri Dec 15 12:37:49 2023 daemon.warn pppd[2135]: Connected to [Media_converter_MAC_add] via interface eth1.10
Fri Dec 15 12:37:49 2023 kern.info kernel: [65461.950670] pppoe-wan: renamed from ppp0
Fri Dec 15 12:37:49 2023 daemon.info pppd[2135]: Renamed interface ppp0 to pppoe-wan
Fri Dec 15 12:37:49 2023 daemon.info pppd[2135]: Using interface pppoe-wan
Fri Dec 15 12:37:49 2023 daemon.notice pppd[2135]: Connect: pppoe-wan <--> eth1.10
Fri Dec 15 12:37:50 2023 daemon.info avahi-daemon[5375]: Joining mDNS multicast group on interface eth1.IPv6 with address xxxx::xxxx:xxxx:xxxx:xxxx.
Fri Dec 15 12:37:50 2023 daemon.info avahi-daemon[5375]: New relevant interface eth1.IPv6 for mDNS.
Fri Dec 15 12:37:50 2023 daemon.info avahi-daemon[5375]: Registering new address record for xxxx::xxxx:xxxx:xxxx:xxxx on eth1.*.
Fri Dec 15 12:37:52 2023 daemon.info pppd[2135]: CHAP authentication succeeded: CHAP authentication success
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: CHAP authentication succeeded
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: peer from calling number [Media_converter_MAC_add] authorized
Fri Dec 15 12:37:52 2023 daemon.err pppd[2135]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 3011)
Fri Dec 15 12:37:52 2023 daemon.warn pppd[2135]: cif6addr: ioctl(SIOCDIFADDR): No such address
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: local  IP address YYY.YYY.YYY.YYY
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: remote IP address ZZZ.ZZZ.ZZZ.ZZZ
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: primary   DNS address 195.238.2.21
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: secondary DNS address 195.238.2.22
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address YYY.YYY.YYY.YYY.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: New relevant interface pppoe-wan.IPv4 for mDNS.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Registering new address record for YYY.YYY.YYY.YYY on pppoe-wan.IPv4.
Fri Dec 15 12:37:52 2023 daemon.info pppd[2135]: LCP terminated by peer
Fri Dec 15 12:37:52 2023 daemon.info pppd[2135]: Connect time 0.0 minutes.
Fri Dec 15 12:37:52 2023 daemon.info pppd[2135]: Sent 0 bytes, received 4 bytes.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address YYY.YYY.YYY.YYY.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Withdrawing address record for 80.200.150.76 on pppoe-wan.
Fri Dec 15 12:37:52 2023 daemon.notice netifd: Interface 'wan' is now up
Fri Dec 15 12:37:52 2023 daemon.notice netifd: Interface 'wan' has lost the connection
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: Modem hangup
Fri Dec 15 12:37:52 2023 daemon.notice pppd[2135]: Connection terminated.
Fri Dec 15 12:37:52 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Fri Dec 15 12:37:52 2023 daemon.info pppd[2135]: Exit.
Fri Dec 15 12:37:52 2023 daemon.notice netifd: Interface 'wan' is now down
Fri Dec 15 12:37:52 2023 kern.info kernel: [65465.468638] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Interface eth1.IPv6 no longer relevant for mDNS.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Leaving mDNS multicast group on interface eth1.IPv6 with address xxxx::xxxx:xxxx:xxxx:xxxx.
Fri Dec 15 12:37:52 2023 daemon.info avahi-daemon[5375]: Withdrawing address record for xxxx::xxxx:xxxx:xxxx:xxxx on eth1.
Fri Dec 15 12:37:52 2023 daemon.notice netifd: Interface 'wan' is disabled
Fri Dec 15 12:37:53 2023 kern.info kernel: [65465.887956] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY] (irq=62)
Fri Dec 15 12:37:53 2023 kern.info kernel: [65465.898232] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/sgmii link mode
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' is enabled
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' is setting up now
Fri Dec 15 12:37:53 2023 daemon.notice netifd: VLAN 'eth1.10' link is down
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Network device 'eth1' link is down
Fri Dec 15 12:37:53 2023 daemon.notice netifd: wan (2313): Command failed: ubus call network.interface notify_proto { "action": 1, "command": [ "\/usr\/sbin\/pppd", "nodetach", "ipparam", "wan", "ifname", "pppoe-wan", "lcp-echo-interval", "1", "lcp-echo-failure", "5", "lcp-echo-adaptive", "set", "PEERDNS=1", "nodefaultroute", "usepeerdns", "maxfail", "1", "user", "user@isp", "password", "safepassword", "ip-up-script", "\/lib\/netifd\/ppp-up", "ip-down-script", "\/lib\/netifd\/ppp-down", "mtu", "1492", "mru", "1492", "plugin", "pppoe.so", "nic-eth1.10" ], "interface": "wan" } (Permission denied)
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' is now down
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' is disabled
Fri Dec 15 12:37:53 2023 kern.info kernel: [65466.587577] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY] (irq=62)
Fri Dec 15 12:37:53 2023 kern.info kernel: [65466.597826] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/sgmii link mode
Fri Dec 15 12:37:53 2023 daemon.notice netifd: Interface 'wan' is enabled
Fri Dec 15 12:37:53 2023 user.notice firewall: Reloading firewall due to ifdown of wan ()
Fri Dec 15 12:37:54 2023 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }

when rolling back the logs are a bit all over (i.e. there are other things happening in between these steps (namely firewall and wlan setups)

Fri Dec 15 12:47:11 2023 daemon.notice netifd: Network device 'eth1' link is up
Fri Dec 15 12:47:11 2023 daemon.notice netifd: VLAN 'eth1.10' link is up
Fri Dec 15 12:47:11 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Dec 15 12:47:11 2023 daemon.notice netifd: Interface 'wan' is setting up now
Fri Dec 15 12:47:12 2023 daemon.info pppd[5238]: Plugin pppoe.so loaded.
Fri Dec 15 12:47:12 2023 daemon.info pppd[5238]: PPPoE plugin from pppd 2.4.9
Fri Dec 15 12:47:12 2023 daemon.notice pppd[5238]: pppd 2.4.9 started by root, uid 0
Fri Dec 15 12:47:12 2023 daemon.info pppd[5238]: PPP session is 1
Fri Dec 15 12:47:12 2023 daemon.warn pppd[5238]: Connected to [Media_converter_MAC_add] via interface eth1.10
Fri Dec 15 12:47:12 2023 kern.info kernel: [   22.268641] pppoe-wan: renamed from ppp0
Fri Dec 15 12:47:12 2023 daemon.info pppd[5238]: Renamed interface ppp0 to pppoe-wan
Fri Dec 15 12:47:12 2023 daemon.info pppd[5238]: Using interface pppoe-wan
Fri Dec 15 12:47:12 2023 daemon.notice pppd[5238]: Connect: pppoe-wan <--> eth1.10
Fri Dec 15 12:47:15 2023 daemon.notice pppd[5238]: peer from calling number [Media_converter_MAC_add] authorized
#This IPV6 is different from the above and the connection is done in pppoe-wan.IPv6 rather than eth1.IPv6
Fri Dec 15 12:47:15 2023 daemon.info avahi-daemon[4781]: Joining mDNS multicast group on interface pppoe-wan.IPv6 with address wwww::wwww:wwww:wwww:wwww. 
Fri Dec 15 12:47:15 2023 daemon.info avahi-daemon[4781]: New relevant interface pppoe-wan.IPv6 for mDNS.
Fri Dec 15 12:47:15 2023 daemon.notice pppd[5238]: local  LL address wwww::wwww:wwww:wwww:wwww
Fri Dec 15 12:47:15 2023 daemon.notice pppd[5238]: remote LL address yyyy::yyyy:yyyy:yyyy:yyyy
Fri Dec 15 12:47:15 2023 daemon.info avahi-daemon[4781]: Registering new address record for fe80::34d9:6611:7cf7:2260 on pppoe-wan.*.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 80.200.150.76.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: New relevant interface pppoe-wan.IPv4 for mDNS.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Registering new address record for 80.200.150.76 on pppoe-wan.IPv4.
Fri Dec 15 12:47:16 2023 daemon.notice pppd[5238]: local  IP address YYY.YYY.YYY.YYY
Fri Dec 15 12:47:16 2023 daemon.notice pppd[5238]: remote IP address ZZZ.ZZZ.ZZZ.ZZZ
Fri Dec 15 12:47:16 2023 daemon.notice pppd[5238]: primary   DNS address 195.238.2.21
Fri Dec 15 12:47:16 2023 daemon.notice pppd[5238]: secondary DNS address 195.238.2.22
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Withdrawing address record for 80.200.150.76 on pppoe-wan.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address 80.200.150.76.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 80.200.150.76.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: New relevant interface pppoe-wan.IPv4 for mDNS.
Fri Dec 15 12:47:16 2023 daemon.info avahi-daemon[4781]: Registering new address record for 80.200.150.76 on pppoe-wan.IPv4.
Fri Dec 15 12:47:16 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
Fri Dec 15 12:47:16 2023 daemon.notice netifd: Interface 'wan' is now up
Fri Dec 15 12:47:16 2023 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Fri Dec 15 12:47:17 2023 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "pppoe-wan", "track_mode": "force", "addr_type": 4, "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Fri Dec 15 12:47:17 2023 kern.debug kernel: [   27.268511] [add_dev_config 307]add node success. iface:wan, dev:pppoe-wan, ifindex:15
Fri Dec 15 12:47:17 2023 kern.debug kernel: [   27.276451] [__set_fib_nh 94]ifindex:15 route_flag:2

I hope this helps with troubleshooting!

cafebug · December 15, 2023, 12:38pm

I have similar issue about PPPoE, if IPv6 is disabled under Multi-WAN then PPPoE never connected.
If I turn on IPv6 then the PPPoE connect immediately. (FW 4.5.4 stable release)

routeruser1 · January 14, 2024, 4:44pm

Similar issues here, migrated from a x86 OpenWrt setup that was fine - my logs were exactly the same after switching to the router

Had to make the pppoe interface promiscuous and enable ipv6.

Annoyingly the settings are reset when the interface goes down, such as removing the cable

Barryboom · January 25, 2024, 7:15pm

having issues as well with Flint2 connecting to PPPOE was connected fine for hours yesterday but at sometime possibly during IP refresh it now fails to connect and gives error below:

PPPoE Connection Log

Connection terminated.
Modem hangup
Exit.
Plugin pppoe.so loaded.
PPPoE plugin from pppd 2.4.9
pppd 2.4.9 started by root, uid 0

going to try some of the fixes above enabling ipv6 or rolling back to 4.5.3 currently on 4.5.6

admon · January 25, 2024, 7:22pm

What ISP and modem do you use?

Barryboom · January 25, 2024, 7:37pm

Vodafone in the UK and Flint2mt6000

IPV6 enabled never seemed to help but reverted to 4.5.3 and was able to type this message but whilst doing so internet dropped.

Going to try putting in my MT1300 and see if it keeps the connection or will need to revert to ISP provided router but loose the functions of GL-Inet that i bought the router for like WG

slesar · January 25, 2024, 7:56pm

I am using Vodafone in the UK and the same router Flint 2. But there 2 differences between Openreach and CityFibre. Anyway, are you using a black small box ONT? Does first-time PPPoE?
If the first time PPPoE then it means the issue is not clear login and details. For example password hard to read " l "(lowest letter L, not number 1).

username should be: dsl123456789@broadband.vodafone.co.uk
VLAN ID: 911

Barryboom · January 25, 2024, 8:03pm

username and password for PPPoE are correct and i dont have a VLAN ID for me that is blank. i have switched router to another GL-inet router the AR750s just to test and so far with the exact same details on the Flint2 its working just very slow seen as its a travel router.

Also the ONT box i have is white and supplied by openreach in my area. What firmware are you using at the moment ?

slesar · January 25, 2024, 8:09pm

At the moment 4.5.5 and my area is supplied by CityFibre. Yes, we are different supplies but same provider. So you need to find out VLAN ID for Openreach

Barryboom · January 25, 2024, 8:17pm

it is working just now without the VLAN on my AR750s. VLAN is not a requirement for everyone however i believe it is 101 if needed for openreach and 911 for cityfibre.

Going to leave it running on my AR750s for a few days see if it remains stable which will then conclude it is something with the router hopefully just firmware that can be fixed.

slesar · January 25, 2024, 8:20pm

Well done. Remember your wan IP is not static, dynamic IP. So any time to restart PPPoE if need to change IP depend on the situation.

Barryboom · January 25, 2024, 8:23pm

well not ideal as the AR750s only has a 100mb NIC so it will be well done when i get the Flint2 working solid instead of randomly and able to use my full internet speed. But thanks for the advice for now.

austinmrs · March 16, 2024, 9:59pm

Same here. In the UK, using openReach.

PPPoe is not working. It connects, but says “connect but cant get internet connection” and stays in “Getting DNS” and never manages to get a connection.

Using latest Firmware. definitely an issue with the official firmware. ive installed the latest openwrt sysupgrade snapshot and pppoe worked immediately.

EDIT: Ive tried to enable IPV6 and it still didnt work.