CenturyLink Fiber on GL.iNet GL-MT6000: "DEVICE_CLAIM_FAILED" in PPPoE WAN + vlan after factory reset

Hello. My old modem was having some issues and I wanted some functionality from OpenWRT, so I upgraded to the GL.iNet GL-MT6000 "Flint 2" modem, and immediately flashed it with the latest version OpenWRT firmware.

I set it up with PPPoE primarily by following this Github gist and the comment by user "autophotomoto" attached, because as they say, the UI has changed since the original comment.

Some items mentioned in the gist and the comment still do not match my user interface:

  1. I have no option for a device type of VLAN (802.1g). I have VLAN (802.1q) (which... a "q" looks like a "g"? Could the original be a typo?) and, I think VLAN (802.1ad)?
  2. The recommended MTU is 14.92 but the UI does not let you input an MTU below a certain 4-digit number, so I tried it with 1492.

As well, the PAP/CHAP username this person recommends is {my_username}@qwest.com, which is odd for two reasons: (1) because I'm CenturyLink. (Possibly CenturyLink is the same as Qwest?) and (2) in my old router I only send my username. No qwest.com or anything else.

Either way, I followed the directions to the best of my ability, making a couple guesses for the parts I was confused about... And then: bing-bang-boom, my Internet was up and working!

--

...Fast-forward 2 weeks: I do something dumb and lock myself out of the device, so I say, "No worries" and hold down the "reset" button. It comes back on with all the default settings again.

I go through the same directions again, but this time, when I click the "Restart" button on my WAN interface (eth0), it comes back with "Error: Unknown error (DEVICE_CLAIM_FAILED)".

The Internet is completely-non-working while I'm using this device, so I have to read on (or tether to) my phone, and I'm trying every combination of change that I can think. Things I tried:

  • Different MTUs
  • Different versions of my username (qwest.com; qwest.net; centurylink.net (per this guy); and with just the username).
  • Both VLAN 802.1q and VLAN 802.1ad.
  • Restarting the ONT that connects to my WAN port.
  • Re-flashing the router (again, after doing the hardware button reset) with the firmware I had originally downloaded, choosing not to save any settings.

None of them have worked. I contacted CenturyLink and the technician I talked to said the following:

  • For the username, I should "use '{myusername}@qwest.net', but you don't need to type the 'qwest.net' part because it's already filled in on the interface" which, I explained to her I'm not using their router and hence obviously this advice is not particularly accurate or helpful
  • I confirmed her advice and said, "OK I'm using the qwest.com" username, with the typo (of ".com", which is what the Gist uses, although she wrote ".net") and she said, "Yep, that's right." Possibly all of them work, and/or none of them are even necessary??
  • I asked about a proper "MTU" and she didn't know what I was talking about, so I said nevermind.
  • She said to her knowledge their system does not somehow bind to a MAC address or something, such that my new router shouldn't be "locked out" or anything if its configuration changes.

So in summary, the new GL.iNet router worked perfectly fine for 2 weeks or so, but has not worked since resetting it. To my knowledge I have changed almost nothing in the configuration from the defaults, but it worked originally and now does not.

I have been using (and am currently using) my old TP-Link router to continue working and using the Internet in the meantime, but I have disconnected it and tried again several times on the GL.iNet router to no avail.

It seems possible I made a mistake the first time that caused it to work when it "shouldn't" have worked the way I'm trying now. For instance: while I have not found a thread that seems to replicate this issue, there seems to be talk of something called "DSA" which I do not understand but was maybe a major change? Perhaps the instructions are slightly different again now?

Any help offered would be greatly, greatly appreciated! Thank you!

Get any necessary pppoe username and password from the working TP-Link router, ISP website, or ask the ISP directly. Many ISP pppoe connections still require a username and password be entered, but the ISP does not actually validate them so you can use any text. In other words the pppoe server requires going through the motions of collecting a username and password but won't check them against any list of customers. It knows you are a paying customer by the MAC of your ONT, your physical line, etc.

I think the mt6000 2.5 Gb wan port is eth0 directly connected to the CPU but the other Ethernet ports have a DSA switch. A default configuration should identify the proper wan Device and pre-populate it. From the default configuration, edit the wan Interface. Change the protocol to pppoe, add your VLAN to the device with the dot notation (e.g. eth0.200), and enter username and password.

If it still fails to connect, more detailed error messages will be found in the System Log.

1 Like

Thank you for your help. I realize I wrote a lot so I apologize that it may have been very difficult to parse.

Get any necessary pppoe username and password from the working TP-Link router, ISP website, or ask the ISP directly.

Indeed I had a PPPoE username and password both from the working router and from the ISP directly, although as I say, their response was somewhat contradictory and probably inaccurate.

It's fascinating about the name/password being unnecessary, however.

I think the mt6000 2.5 Gb wan port is eth0 directly connected to the CPU but the other Ethernet ports have a DSA switch. A default configuration should identify the proper wan Device and pre-populate it. From the default configuration, edit the wan Interface. Change the protocol to pppoe, add your VLAN to the device with the dot notation (e.g. eth0.200), and enter username and password.

If it still fails to connect, more detailed error messages will be found in the System Log.

This is what I have done, although while double-checking this, you actually seem have tangentially helped me identify the problem, although I still have some confusion:

The "fix": I was using the "wrong" (??) eth device.

This device has two "WAN" ports. One is labeled "WAN", and the other is labeled "WAN/LAN 1". I have only ever used the "WAN" port. I assumed that was eth0 and the other was eth1.

I am almost positive that 2 weeks ago during my initial setup (when this worked), I configured my VLAN on eth0. After the reset, I have continued only using eth0.

I have looked in both the "System Log" and "Kernel Log" but despite that the time on the router is correct, the System Log dates were all from yesterday. And the Kernel Log dates are based off seconds (? or something) since boot and due to the other, I was not sure if they were accurate. (It seems like coming back 10 minutes later, the System Log is now showing a few items from today. So maybe it's on a delay?)

Anyway: while navigating back, I hit the main menu and noticed that the "Port status" section has a "lan1", "lan2", "lan3", "lan4", "lan5", and (shown before all of these) only an eth1.

There is NO eth0 listed. And eth1 is shown as plugged in.

I modified my VLAN (802.1q) to be connected to eth1 as the interface, and immediately everything started working.

So now:

  1. I do not know why I was using eth0 before (again, I could be wrong but I am almost certain) but now have to use eth1.
  2. I do not know whether I "want" 802.1q or 802.1ad, but I'm using 802.1q because it worked. (EDIT: I just tried it with 802.1ad and it broke. Switching back to 802.1q works.)

And I have Internet for the moment!

802.1ad is double-tagging also known as Q in Q. It's only used inside an ISP not on customer lines. 802.1q is a single VLAN tag. When an ad packet is de-tagged once, the result is a q packet, not a plain untagged packet.

Thank you! It sounds like, then, the instructions from the gists most genuinely be typos then?? Since they refer to "802.1g". I assume it was "q" and someone got 802.11g stuck in their head and wrote that.