cancel
Showing results for 
Search instead for 
Did you mean: 
914 Views
Message 31 of 53

Re: Routing problems at BT

Wired.

 

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

 

and

 

Uptime:    4 days, 16:34:42
Modulation:    G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]:    1,179 / 14,335
Data Transferred (Sent/Received) [MB/GB]:    163.60 / 1.46
Output Power (Up/Down) [dBm]:    11.5 / 0.0
Line Attenuation (Up/Down) [dB]:    9.5 / 17.5
SN Margin (Up/Down) [dB]:    7.0 / 3.5
Vendor ID (Local/Remote):    TMMB / IFTN
Loss of Framing (Local/Remote):    0 / 0
Loss of Signal (Local/Remote):    0 / 0
Loss of Power (Local/Remote):    0 / 0
Loss of Link (Remote):    0
Error Seconds (Local/Remote):    45,375 / 0
FEC Errors (Up/Down):    0 / 0
CRC Errors (Up/Down):    0 / 2,462,529
HEC Errors (Up/Down):    0 / 1,445,532
Line Profile:    Fast

0 Ratings
CharlieF
Aspiring Expert
906 Views
Message 32 of 53

Re: Routing problems at BT

Ip looks fine, but 2 million crc errors on the down link Sounds bad.

Not my area I'm afraid

Charlief
0 Ratings
891 Views
Message 33 of 53

Re: Routing problems at BT

Still on the same IP 86.145

but now going ok.

 

fwiw I see the S/N margin is now 6.5

 

Thanks for the suggestions and comments guys.

 

Uptime:    4 days, 21:39:31
Modulation:    G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]:    1,179 / 14,335
Data Transferred (Sent/Received) [MB/GB]:    172.09 / 1.55
Output Power (Up/Down) [dBm]:    11.5 / 0.0
Line Attenuation (Up/Down) [dB]:    9.5 / 17.5
SN Margin (Up/Down) [dB]:    7.0 / 6.5

.....

Error Seconds (Local/Remote):    48,335 / 0

CRC Errors (Up/Down):    0 / 2,652,286
HEC Errors (Up/Down):    0 / 1,579,803

0 Ratings
Distinguished Guru
881 Views
Message 34 of 53

Re: Routing problems at BT

 


@CharlieF wrote:

The hub is allocated an IP address with a limited time lease.  When this expires, the hub requests a new one from the BT pool.  I think this lasts 3-6 days, matching your 4 day experience.

 

Although it is fairly random, I expect that your geographic location and exchange will have some bearing on the set you get allocated from. 

 

 

It is challenging to unpick all of these symptoms.

 

109 not getting to the news groups is due to the news servers blocking non-BT IP addresses (not a routing issue as such).  Poor speed could be a number of things - as this forum aptly demonstrates.  tracert is the only real way to show a routing issue on the BT network IMHO.

 

 

ChalrleF

 

 


 

Hi. Frankly, the IP address can stay with a user for weeks. The hub doesn't necessarily get a new one, since this can interfere with a connection. It doesn't need to have a new IP address or have an expiry time.

 

The 109 not getting to the newsserver is actually a firewall or issue with Giganews being told that BT has these certain ranges. True, the firewalls (or the Giganews access from BT) don't let any non BT IP addresses - however there are a few 109.xxx.xxx.xxx BT IP addresses in the dynamic pool.

 

860 Views
Message 35 of 53

Re: Routing problems at BT

Connection seemed sluggish so did a BT speedtest:

 

Speedtest26Apr2011.jpg

 

Fed up with all these problems so did a Hub power cycle, then a thinkbroadband test (too soon to repeat BT's speedtest) and got 11.3 Mbps.

Compare that to 5571 Kbps, 648 Kbps, 186 Kbps over the last few days.

 

86.147.xxx.xx now

0 Ratings
845 Views
Message 36 of 53

Re: Routing problems at BT

and at about 8am today BT speedtest gives me

13.8 Mbps/0.8 Mbps     

thinkbroadband 4.6Mbps/0.9Mbps

speedtest.net 8.7Mbps/0.9Mbps

 

I don't mind 4.6 Mbps as long as it's constant, and it's been all over the place the last few days, and when allocated the 109 IP range, impossible to connect to the newsgroups, but I have a feeling there are two different issues here.

 

However I do wish BT would fix the 109 IP range issue. There's no excuse for wilfully ignoring what seems to be a simpe and identifiable problem that is preventing customers from accessing an important area of the internet.

0 Ratings
CharlieF
Aspiring Expert
813 Views
Message 37 of 53

Re: Routing problems at BT


@FloFosterJenkins wrote:

More problems yesterday (Easter day). Browsing impossibly slow all day. Speedtest failed to work after interminable wait and then said there was a fault.

IP address 86.148.xxx.xx

 

Just gave up and hit Disconnect in the Hub interface and immediately Connect.

Acquired IP address 86.144.xxx.xxx and back to normal.

 


Interesting... See this previous post from last year..

 

http://community.bt.com/t5/BB-Speed-Connection-Issues/No-Web-Pages-DNS-Failure/m-p/25642

 

They had exactly the problem I am experiencing, and stated they had an IP address starting 86.148.  That problem was marked as solved, but it was only because they reset and got a new WAN IP address.

 

Can it really be coincidence that FloFosterJenkins had problems with 86.148 as well, that went away with a new WAP IP?

 

Is it possible that 86.148 and 86.160 both have routing issues in the core network, that BT can't actually find and fix?  Maybe they get so few reports from customers with details (and a hub reset makes the problem appear to go away), that they don't do anything.

 

 

Engineer at my house right now.  I've demonstrated the routing issue, making it appear and disappear, he's calling the real helpline now.

 

 

The forum mods have also been in touch with me and are on the case Smiley Happy 

 

CharlieF

 

 

0 Ratings
CharlieF
Aspiring Expert
797 Views
Message 38 of 53

Re: Routing problems at BT

...Update. Engineer now replacing my hub, although I have pointed out that my neighbour doesn't route with an 86.160 address either. Perhaps he's going to replace all the hubs in my street.

0 Ratings
CharlieF
Aspiring Expert
781 Views
Message 39 of 53

Re: Routing problems at BT

Ok, engineer has left, problem still not resolved.  New hub didn't seem to make any difference.  DSL signal and line to exchange all fine (of course).

 

He spoke to the help desk and demonstrated the routing issue, but it seems to be beyond them to identify it.  The engineer took away loads of screen shots of trace routes stating that he'd "never seen anything like this before".

 

I'll take this up with the forum mods now and see where we go from here.

 

I must say that everyone at BT has been very helpful and polite over this issue, and the engineer invested a lot of time experimenting with the hubs and talking to his helpdesk for over an hour.

 

The problem seems to be that if there is an IP routing issue on the BT network, that there isn't a point within the support operation where this can be raised and addressed (the mods help not withstanding of course).  Every new person you speak to is determined that the problem is with the hub/phone line/filters/PC and that they can fix it.  Alas, not.

 

 

CharlieF

 

0 Ratings
CharlieF
Aspiring Expert
601 Views
Message 40 of 53

Re: Routing problems at BT


@CharlieF wrote:

Ok, engineer has left, problem still not resolved.  New hub didn't seem to make any difference. 


 

I've left this a month to give BT every chance, but it is still not resolved.

 

To recap, when everything is working I can ping everywhere, no problem..

 

C:\>ping www.google.co.uk

 

Pinging www.l.google.com [209.85.227.106] with 32 bytes of data:

Reply from 209.85.227.106: bytes=32 time=78ms TTL=50

Reply from 209.85.227.106: bytes=32 time=85ms TTL=50

Reply from 209.85.227.106: bytes=32 time=63ms TTL=50

Reply from 209.85.227.106: bytes=32 time=80ms TTL=50

 

C:\>tracert -d 209.85.227.106

 

Tracing route to 209.85.227.106 over a maximum of 30 hops

 

  1    82 ms    99 ms    99 ms  192.168.1.254

  2    49 ms    58 ms    57 ms  217.47.154.142

  3    78 ms    80 ms    85 ms  217.47.154.125

  4    42 ms    58 ms    51 ms  213.1.69.26

  5    88 ms    80 ms    80 ms  217.41.222.50

  6    61 ms    60 ms    51 ms  217.41.222.182

  7    42 ms    53 ms    44 ms  109.159.248.206

  8    66 ms    58 ms    53 ms  109.159.248.138

  9    67 ms    59 ms    74 ms  109.159.254.110

 10    36 ms    37 ms    36 ms  195.99.126.111

 11    46 ms    36 ms    36 ms  66.249.94.76

 12    42 ms    43 ms    44 ms  72.14.232.134

 13    44 ms    42 ms    44 ms  216.239.49.45

 14    43 ms    48 ms    43 ms  209.85.243.89

 15    41 ms    41 ms    41 ms  209.85.227.106

 

Trace complete.

But if my home hub is assigned a public IP address beginning 86.160.x.x, it doesn't work...See below

 

C:\>ping www.google.co.uk

Pingrequest could not find host www.google.co.uk. Please check the name and try

 again.

 

C:\>tracert -d 209.85.227.106

 

Tracing route to 209.85.227.106 over a maximum of 30 hops

 

  1    85 ms    99 ms    99 ms  192.168.1.254

  2    29 ms    28 ms    29 ms  217.47.154.142

  3    29 ms    29 ms    28 ms  217.47.154.125

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22  ^C

 

 

It does it on my HH V1.0 and HH V2.0

It happens to my neighbour on their BT connection

An engineer called, and couldn't fix it

 

I've sent a message to the forum mods, and although they have tried escalating this within BT, I've not had any messages back for a couple of weeks.

 

Can anyone help me here?  More suggestions, tests?

 

Charlie


 

0 Ratings