Mt6000 wan cable not connected.

I've just purchased an Mt6000 (Flint 2) to replace my current router. I have BT full fibre to prem, and have used the 'bthomehub@btbroadband.com' user name and 'BT' password (same as current working to-link router). The Mt6000 looks like trying to connect, but then reports no cable plugged in. I've tried both WAN ports, and same issue. Any ideas?

Do you know if you are allowed to switch your router or do you need to change something on ISP side for it, like registering the new MAC for example?

Can you do this:

  1. Clone the old router's mac to Flint 2, or
  2. Reboot the modem, or wait longer so that the modem accept new router.

What firmware are you on?

Can you try to flash 4.6.2 with all settings erased?

Pretty sure I'm running the latest firmware. I checked for a update when it didn't connect. I also tried to clone the Mac of the previous router but it wouldn't accept an manual mac address.

I should be able to change the router, as I was using my own tp-link one, not the BT provided one.

It should work fine as long as you have PPPoE specified as the Protocol on the WAN interface and the right port connected to the ONT (and the correct username and password, as you've already mentioned). No MAC cloning or anything should be required.

It is possible the isp has put you under a cooldown period this is how they do it in my country and why often spoofing the mac is usefull but not a requirement.

The isp wants to avoid their own supplied internet isn't shared across multiple instances.

So when they detect 2 different mac addresses on that link it will put either the new mac on the cooldown or both, so yeah... If you cloned the mac later likely the isp already detected it.

But don't worry it will be a small grace period it will use the new mac or default mac of your flint 2 :wink:, just avoid changing it again because it will just do that again :yum:

Its always usefull too to post the pppoe messages from the log :wink:, from my experience my isp can give a time out or access deny message.

If you are really really sure the pppoe user and password are correct also the tagged vlan then its also likely the log shows time outs or refusing messages to it :wink:, but it can also be a wrong vlan if they require it.

No I am 99% sure this ISP does none of those things. Their requirement is just PPPoE with the correct username and password.

1 Like

are you setting any additional vlans or anything?

iirc the ONT does the VLAN stuff for you.

What lights does the ONT show?

1 Like