Hi,
Longtime user of BT Infinity 1 FTTC service here - 3 years plus. I use an Openreach Huawei EchoLife Hg612 2b modem and ASUS RT-AC66U Router. (Also have access to an Openreach ECI modem and ASUS RT-AC68U router).
I power off my kit when I am away and when I'm back I power back on and I can see the router receiving a new WAN IP address within a few seconds and away I go - never had any issues with line stability - no dropouts at all.
Then yesterday when I got back home, I powered the kit on and had no connection. Logging into the router I noticed it struggling to get the WAN IP address it was alternating between showing 0.0.0.0 and various other ip addresses for several minutes until settling down to finally accept a stable IP address. Once this happened everthing was OK with a stable line and no dropouts.
When I tested the situation by manually disabling the "Internet Connection" button on my router I could replicate the issue, whereas previously it would take seconds to connect with a new WAN IP Address now it takes several minutes where you can see the "WAN IP" alternating between showing eirther "Disconnected", 0.0.0.0 or a fluctuating IP number until it finally settles on a stable IP address.
OK I thought maybe I have a faulty modem or router, but then I swapped out both units for the ECI modem and AC68U router and exactly the same thing happens with them.
I do have the BT supplied Hub6 still in its box which I confess I have never used. TBH I much prefer to use the ASUS router, and the OpenReach modem/ASUS router combo has worked impeccably for the last three years or so.
Has BT recently changed the way it provides IP addresses when making a new connection to the BT broadband service ?
Solved! Go to Solution.
Some more info, this is my router syslog when the connection fails ...
May 21 18:32:11 pppd[1875]: CHAP authentication succeeded: CHAP authentication success
May 21 18:32:11 pppd[1875]: CHAP authentication succeeded
May 21 18:32:11 pppd[1875]: peer from calling number F8:13:08:40:F7:CD authorized
May 21 18:32:11 pppd[1875]: local IP address 217.42.60.204
May 21 18:32:11 pppd[1875]: remote IP address 172.16.14.212
May 21 18:32:11 pppd[1875]: LCP terminated by peer
May 21 18:32:11 pppd[1875]: Connect time 0.0 minutes.
May 21 18:32:11 pppd[1875]: Sent 0 bytes, received 0 bytes.
and this is my router syslog when the connection succeeds ...
May 21 18:32:25 pppd[1875]: CHAP authentication succeeded: CHAP authentication success
May 21 18:32:25 pppd[1875]: CHAP authentication succeeded
May 21 18:32:25 pppd[1875]: peer from calling number F8:13:08:40:F7:CD authorized
May 21 18:32:25 pppd[1875]: local IP address 217.42.111.84
May 21 18:32:25 pppd[1875]: remote IP address 172.16.14.212
May 21 18:32:25 rc_service: ip-up 2439:notify_rc start_firewall
May 21 18:32:25 dnsmasq[288]: read /etc/hosts - 5 addresses
May 21 18:32:25 dnsmasq[288]: read /etc/hosts.dnsmasq - 1 addresses
May 21 18:32:25 dnsmasq-dhcp[288]: read /etc/ethers - 1 addresses
May 21 18:32:25 dnsmasq[288]: using nameserver 8.8.8.8#53
May 21 18:32:25 dnsmasq[288]: using nameserver 8.8.4.4#53
May 21 18:32:25 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 21 18:32:25 rc_service: ip-up 2439:notify_rc stop_upnp
May 21 18:32:25 rc_service: ip-up 2439:notify_rc start_upnp
May 21 18:32:25 rc_service: waitting "stop_upnp" via ip-up ...
Strangely I have noitced the same IP address "217.42.60.204" being offered to me repeatedly - and the connection will always fail! I have to wait a while for a different address to be offered like the one shown above "217.42.111.84" for the connection to be successful. Something very strange is going on.
This morning everything seems to be working again as normal - I think BT must have had issues with their login procedures yesterday.