Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[faqinel]

A little background:

We have three BT FTTP connections, made via third party Omada routers.  These were all working fine up until Monday this week, when all three connections went down.  On investigation all three were found to be authenticating and connecting but receiving an external IP address in the private 10.0.0.0/8 range.  A call to BT revealed that all three connections had been blocked and we were told to wait 4-7 hours for them to be unblocked.  Two of them went live within 30 minutes but the third remains down four days later.  This is still presenting the same symptoms.

I have tried an alternative Netgear router, which produces the same result.  However a BT Hub will connect.  Am I correct that the Hub does not present credentials when making a connection?  If so, how does it authenticate itself?  I have drawn a blank with BT support; they cannot explain why I am assigned a private IP when connecting with the supplied credentials (they confirmed them to be correct), couldn't see that the connection had been blocked and didn't seem to think that it was a problem as long as the BT Hub was working.

Can anyone shed any light on this issue?  I am not sure what questions I need to be asking.  Can I request the connection to be rebuilt/reset?

Any help would be greatly appreciated.

Thanks in advance,

Faqinel.

[Alex Atkin UK]

The BT Hub should not authenticate any differently to what you have been given for your own routers.  However perhaps the block has been placed on the MAC address of the router which is why the BT Hub works, a different Omada router would maybe work too, or if you changed the MAC address on the existing one.

I'm more curious why they were blocked in the first place and how?

[faqinel]

Pretty sure the hubs don't store any credentials, you can plug in any BT Hub and get a connection if it's a BT service.  It's been a while since I've used one but I seem to remember, for this reason, they could not be used with other service providers because you could not enter PPPoE credentials.

I did try with a Netgear router and got the same result, so I don't think the block is against MAC address in this instance.

What else with BT other than a billing dispute.  They were charging thousands instead of hundreds for the three FTTP connections plus a very limited VOIP system.  After getting nowhere through the normal channels, it had got to the point where it was raised with corporate, who as a gesture of goodwill (sic) stopped our direct debit whilst the issue was resolved.  This apparently triggered some other system to block all three connections plus the VOIP service.

[j0hn]

The BT broadband PPP login credentials are generic.
There's a few that work (or used to be a few) such as bthomehub@btbroadband.com with a blank password or a password of BT.

I believe the BT hubs simply use these generic credentials. The credentials are already filled in on many previous versions of the hub.

BT's VOIP (Digital Voice) requires a BT hub handing the PPP to work however 2 neighbours could both swap their BT hubs and their lines would authenticate and the VOIP would still work.
Credentials for VOIP are passed to the hub encrypted after authentication.

There's a user on Thinkbroadband who managed to setup an Asus router connected directly to the ONT and handling the PPP connection with a BT hub connected to the LAN is the Asus.
He relays the PPP session to/from the BT hub to truck it in to thinking it is connected and VOIP works.

To me that suggests even the newer BT Hubs still use the same genetic credentials to authenticate.

So I've no idea why they have blocked some of your devices from connecting but I think the credentials are a red herring.

I would go with Alex'S thinking and try clone the Mac address of a BT hub to your router connected to the 3rd line and see if that works.

[meritez]

A little background:

We have three BT FTTP connections, made via third party Omada routers.  These were all working fine up until Monday this week, when all three connections went down.  On investigation all three were found to be authenticating and connecting but receiving an external IP address in the private 10.0.0.0/8 range.  A call to BT revealed that all three connections had been blocked and we were told to wait 4-7 hours for them to be unblocked.  Two of them went live within 30 minutes but the third remains down four days later.  This is still presenting the same symptoms.

I have tried an alternative Netgear router, which produces the same result.  However a BT Hub will connect.  Am I correct that the Hub does not present credentials when making a connection?  If so, how does it authenticate itself?  I have drawn a blank with BT support; they cannot explain why I am assigned a private IP when connecting with the supplied credentials (they confirmed them to be correct), couldn't see that the connection had been blocked and didn't seem to think that it was a problem as long as the BT Hub was working.

Can anyone shed any light on this issue?  I am not sure what questions I need to be asking.  Can I request the connection to be rebuilt/reset?

Any help would be greatly appreciated.

Thanks in advance,

Faqinel.

Which Omada routers, the ER605 v1 and v2 has never truly supported IPv6 WAN and was reported heavily a couple of years ago, BT can block any router that does not support IPv6.