Issues with BT Infinity

[Joppsta]

I switched from my HH3 to the Billion BiPAC 7800N and it worked like a charm using this guide here:

http://www.billion.uk.com/esupport/inde ... re-network

It seems to have somehow borked my connection after less than 24 hours of uptime. I'm accessing the web from the second line in the house, a really crappy 12mbps/0.5mpbs. I would much prefer my 60-70/14 that infinity is giving me. What i find odd is that switching from HH3 to 7800N gave me a speed boost in the upload department from the 8-9 I was able to achieve. Not really shocking, HH3 is garbage in my opinion, nonetheless... it keeps looping through the following in the syslog:

Jan 01 00:01:51 daemon pppd[651]: PPP: Start to connect ...
Jan 01 00:02:14 daemon pppd[651]: Couldn't get channel number: Transport endpoint is not connected
Jan 01 00:02:14 daemon pppd[651]: PPP: PPP Server No Response !!!
Jan 01 00:02:14 daemon pppd[651]: Doing disconnect

I tried using the HH3 but that no longer connects also and trying to troubleshoot with that thing is torture. Contacted BT via livechat and they were as useless as a chocolate teapot.

Help?

- Joppsta

[Joppsta]

I should also add I'm running firmware version 1.06f

[Joppsta]

Nobody have any ideas? I got a BT engineer coming out tomorrow so I'm guessing that means there's some sort of issue with the line.. after all it is a new line, only installed less than a month ago so maybe some teething problems.

[billion_fan]

Nobody have any ideas? I got a BT engineer coming out tomorrow so I'm guessing that means there's some sort of issue with the line.. after all it is a new line, only installed less than a month ago so maybe some teething problems.

It might be the BT open reach modem that is at fault as both the BT home hub and 7800N are exhibiting the same issue

[Joppsta]

Nobody have any ideas? I got a BT engineer coming out tomorrow so I'm guessing that means there's some sort of issue with the line.. after all it is a new line, only installed less than a month ago so maybe some teething problems.

It might be the BT open reach modem that is at fault as both the BT home hub and 7800N are exhibiting the same issue

Any ideas on a way to mess with it? I can't seem to find any info online regarding accessing it.

[billion_fan]

Nobody have any ideas? I got a BT engineer coming out tomorrow so I'm guessing that means there's some sort of issue with the line.. after all it is a new line, only installed less than a month ago so maybe some teething problems.

It might be the BT open reach modem that is at fault as both the BT home hub and 7800N are exhibiting the same issue

Any ideas on a way to mess with it? I can't seem to find any info online regarding accessing it.

You should be able to unlock the open reach modem and then use LAN port 2 to access the device with a static IP, the IP address if I remember is 192.168.1.1

[Joppsta]

Doesn't seem to work... guess I shall just wait until tomorrow.

[tinytim]

You should be able to unlock the open reach modem and then use LAN port 2 to access the device with a static IP, the IP address if I remember is 192.168.1.1

It's easy if it's a Huawei as it's just an unlocked firmware, with an ECI one it's quite tricky.

[Joppsta]

You should be able to unlock the open reach modem and then use LAN port 2 to access the device with a static IP, the IP address if I remember is 192.168.1.1

It's easy if it's a Huawei as it's just an unlocked firmware, with an ECI one it's quite tricky.

I believe it's ECI, I'll just wait for the engineer tomorrow though. Hopefully won't take too long to get operational again.

[Joppsta]

So.... I did nothing and the router connected to the internet for some reason. However I'm not achieving full download speeds that I should be expecting, with the Billion anyway, not tried the HH3 yet.

Jan 02 09:37:26 daemon pppd[18074]: PPP: Start to connect ...
Jan 02 09:37:28 daemon pppd[18074]: PPP server detected.
Jan 02 09:37:29 daemon pppd[18074]: PPP session established.
Jan 02 09:37:29 daemon pppd[18074]: Using interface pppewan_1
Jan 02 09:37:29 daemon pppd[18074]: Connect: ppp_ewan_1 <--> eth0
Jan 02 09:37:29 daemon pppd[18074]: Couldn't increase MTU to 1500.
Jan 02 09:37:29 daemon pppd[18074]: Couldn't increase MRU to 1500
Jan 02 09:37:29 daemon pppd[18074]: Couldn't increase MRU to 1500
Jan 02 09:37:29 daemon pppd[18074]: PPP LCP UP.
Jan 02 09:37:29 daemon pppd[18074]: Remote message: CHAP authentication success, unit 5210
Jan 02 09:37:29 daemon pppd[18074]: local IP address 81.152.133.41
Jan 02 09:37:29 daemon pppd[18074]: remote IP address 217.32.142.109
Jan 02 09:37:29 daemon pppd[18074]: primary DNS address 194.72.9.38
Jan 02 09:37:29 daemon pppd[18074]: secondary DNS address 194.74.65.69
Jan 02 09:37:29 daemon dnsmasq[91]: using nameserver 194.74.65.69#53
Jan 02 09:37:29 daemon dnsmasq[91]: using nameserver 194.72.9.38#53
Jan 02 09:37:29 daemon pppd[18074]: Received valid IP address from server. Connection UP.
Jan 02 09:37:30 user syslog: begin: interface: ppp_ewan_1 go to up
Jan 02 09:37:31 daemon dnsmasq[91]: using nameserver 194.74.65.69#53
Jan 02 09:37:31 daemon dnsmasq[91]: using nameserver 194.72.9.38#53
Jan 02 09:37:31 daemon UPNPD[543]: received signal 15, good-bye
Jan 02 09:37:33 daemon UPNPD[10731]: HTTP listening on port 2800
Jan 02 09:37:34 user syslog: end: interface: ppp_ewan_1 go to up
May 02 21:37:09 syslog -- MARK --
May 02 22:37:09 syslog -- MARK --
May 02 23:03:27 daemon DHCP SERVER: DHCPDISCOVER from 54:04:a6:d9:32:94 via br0
May 02 23:03:28 daemon DHCP SERVER: DHCP offer to 54:04:a6:d9:32:94
May 02 23:03:28 daemon DHCP SERVER: DHCP request from 54:04:a6:d9:32:94
May 02 23:03:28 daemon DHCP SERVER: DHCP ack to 54:04:a6:d9:32:94
May 02 23:03:35 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
May 02 23:03:38 daemon DHCP SERVER: DHCPINFORM from 192.168.1.100
May 02 23:04:24 user syslog: web: logout (timeout)
May 02 23:04:26 user syslog: web: ::ffff:192.168.1.100 login

Rather confused. It's been looping the stuff in the OP all day and then all of a sudden decides to connect? I'm posting this here for you guys to see and for reference when the BT engineer visits.