GL-iNet GL-MT6000 Flint 2 - not connecting to TalkTalk

I bought the GL-iNet GL-MT6000 Flint 2 to replace the Sagemcom Fast 5464 router that TalkTalk gave me.

It won't connect. I've tried switching off the ONT box for 30 minutes, but it still won't connect. It seems to be trying to connect but just wont, even if I leave it on for 15 minutes.

I know the GL-MT6000 has MAC cloning. I tried this but the Sagemcom Fast 5464 has two MAC addresses - one is on the product info page and the other is listed as the "Local Ethernet MAC address". This second MAC address is also on the rear sticker.

I tried both and again they didn't work, although I didn't disconnect the ONT box this time.

Anyone have this issue and could offer any pointers? :neutral_face:

You need to setup VLAN 101 as described here: Set up a non-TalkTalk router - TalkTalk Help & Support

Unfortunately, I don't know if this is possible using the GL GUI and using DHCP.
(For PPPoE it is possible, but this should not be the case here.)

Maybe @bruce can check this tomorrow.

Hi,

  1. Please confirm if the ONT box is responsible for the dial-up with ISP (like PPPoE)?
  2. If yes, the GL routers WAN work mode is DHCP, and support the VLAN setting for the WAN: Ethernet - GL.iNet Router Docs 4

2 Likes

Hi.

This is the ONT box that was fitted by CityFibre.

https://support.aa.net.uk/CityFibre_ONT

I'm at work right now so I'll try this when I get home.

Important: The customer's router will need to talk PPPoE on VLAN 911.

Can you input the PPPoe Password and set VLAN 911?

1 Like

I have same box ONT from city fibre and router Flint 2. You need call support Talk Talk for get user and password for pppoe and vlanid.


Mine is Vodafone broadband UK

Thanks for the suggestion.

If you dont mind me asking, did you do this and if so I assume it worked ok?

There is no PPPoE password. The TalkTalk router connects via DHCP.

Sure about that?
Could be just the ISPs one.

I'm sure. TalkTalk is the ISP.

The supplied TT router, Sagemcom Fast 5464, connects via DHCP.

I cant even find a config file to have a look around inside.

I just had an extended online chat with a member to the TalkTalk help team.

I specifically asked for a username and password for PPPoE.

He said they weren't allowed to give out that information, but instead suggested it could be found in the config file of the provided router that I've had for the last 3 weeks, i.e. the TalkTalk Sagemcom Fast 5464.

Problem is, I cant see no config file for the TalkTalk Sagemcom Fast 5464. :neutral_face:

To say it's interface is basic is the understatement of the year....

So you are not allowed to bring your own router with this ISP?

According to this one particular TalkTalk goon I got a hold of on the online chat, yes.

But he didn't seem to know much and just kept copying & pasting the same stock responses.

Talktalk does indeed use DHCP not PPPoe so there is no username and password / config. No idea what the Talktalk support rep is talking about...

I currently have Vdsl and I use my modem in bridge mode however from what I've read your modem doesn't do bridge / modem mode.

Try connecting the ONT directly to WAN port on the Flint 2 (taking your Sagemcom Fast 5464 out of the connection) and set the VLAN ID: 0, making sure you use DHCP as the connection type.

Edit: I see we can't set the VLAN ID to 0 however try just leaving it blank and see if that works.

Edit 2:

So I managed to set VLAN ID on WAN to .0 via Luci

Go here flint2ip/cgi-bin/luci/admin/network/network

Scroll down and Find WAN, check under the icon what the device name is for WAN, probably eth0, click edit and find the device drop down "eth0" click drop down and go to "custom" type the name of the interface, in this case eth0 followed by the Vlan id name. So for you it will be: eth0.0

Click save and then save / apply.

Let us know how that works.

I'm basing my guide from this post over on the Talktalk forums

Vlan ID is enabled on the Sagefast etc router/s you will need an intervention from TT HQ unless the 3rd party router can be set to Vlan ID 0 zero there is no other way.

If that is the case and setting to zero from within the Luci interface works then maybe the Devs can change the client GUI to accept 0 in the VLAN ID field.

Please try leaving the VLAN id blank in the glinet gui and see if you can connect. If this fails then do the Luci / vlan id zero "0" to confirm if that resolves the connection.

Where talktalk is refering to VLAN id 101 I know that's used for the vdsl connection but as the post over at talktalk suggest VLAN ID: 0 for the ONT connection then I would go that route first. The Talktalk setup pages are mainly refering to the FTTC vdls connections hence the Vlan id 101 might be incorrect for the ONT devices and as you have noted, the support chat rather make stuff up or just read a script.

2 Likes

Does isp router have modem mode? If yes then plug port to Flint 2. Should be auto dhcp.
I know you have pay more power sockets :expressionless: (3 power sockets, ONT, isp router and flint 2)

Thank you so much. This works! :grin:

In my router it was listed as eth1, so I changed this to eth1.0 and it connected right away.

:+1: :+1: :+1:

Just an addendum to the above.

I went into the WAN settings on the main interface and removed the value 101 from the VLAN box, and the router disconnected.

I then went back in the Luci interface and it had changed the eth1.0 setting to eth1.101. I edited this back to eth1.0 and rebooted but it didn't look like it was going to connect. Luckily, I had already created a backup file before I did this so I restored this and it connected again.

I'm now out of the house so I'll have a look at this again this evening.

Great news. So it looks like you do indeed need a zero value in the VLAN ID.

I went into the WAN settings on the main interface and removed the value 101 from the VLAN box, and the router disconnected.

^ I should have mentioned about leaving the glinet gui settings blank and then going via Luci to amend.

Out of curiosity, you said you removed the 101 VLAN ID and your connection dropped. Now I'm wondering if 101 VLAN was actually working for you, I doubt it was but it might have a been a ghost setting since you amended Luci directly

Can you test again with the default values in luci and just adding VLAN 101 on the main glient GUI (not Luci) rebooting after adding applying / saving. I am only asking just so it is clear that you indeed do need VLAN zero (which again I presume you do based of you connecting / talktalk post)

Also do the same but with no VLAN in the field, so it's blank

Seems odd having a VLAN ID "0" but anything is possible with ISPs these days.

But if you can, just re test and give confirmed results per method you tried.

If you need VLAN ID zero "0" then the Devs on here will need to look at allowing a zero value on the main glinet gui.

1 Like

Ok.

I got rid of the 101 entry in the VLAN field. The connection dropped immediately.

Then I went into the Luci interface, went to WAN and it had reset eth1 to eth1.101 and wasn't connecting. I changed it back to eth1.0 and clicked save.

There was a message in the WAN field saying something like "4 IP settings to apply" (I think). I clicked on this link and then clicked "save and restart".

The router then connected ok and eth1 is now eth1.0 once again.

I think that's enough messing about for now. :smiley:

It WOULD help if you could enter 0 in the main VLAN interface screen.

But VLAN 0 does not exist. I think the problem is somewhere else.