Vodafone Servers Unreachable

[7ony]

Our two VSS 1 boxes have been down all week, presuming there was a DSL issue, but today I run some checks and the issue points to Vodafone.

We did a 'Tracert' to address 212.183.133.181 and the packets don't reach the destination (request timed out). So we did just a ping to the same address. No reply (100% packet loss). We did the same thing with the address 212.183.133.182 and this was OK. Pinging it was OK as well. Then we tried destinations between 212.183.131.128 and 212.183.131.191. Tracert timed out and we got 100% packet loss on pinging.

As so many people are having problems with BT (as we are with them) we tried the same procedure with an external website based in the UK. Same results.

Anyone else came the same conclusion as me?

Please investigate.

[7ony]

Saying that... doing a network test shows that there is a delay of 556ms for the packets to make a round trip.

But doesn't explain why we are getting 100% packet loss on most of the addresses.

[grolschuk]

Not all endpoints are configured to reply to ping requests, this is normal for public facing routers that have services behind them

Did the tracert work upto that last hop, or was it timing out all the way?

a constant 500ms to a destination is a very poor or congested line.

If you were to do a tracert to google.co.uk does that give the same kind of results?

[7ony]

It's timing out all the way. Tracert to google.co.uk works fine.

I know that 500ms is poor and I need to work on that, but doesn't explain why they are unreachable.

[grolschuk]

How strange

I would expect the first few hops leaving your router to be the same or close to that as the google route is taking, and then split off in a different direction around 3 or 4

It's almost as if your computer or network doesn't have a clue where the VF IP address is, so doesn't forward it onto your router to then get passed out to the internet.

I am sure the VF Tech guys may have some ideas to try.

On mine, the hop before the timeout is 192.2.22.217, can you get a tracert path to there ok?

[7ony]

It seems to time out just as it's trying to leaves my ISP (166.49.211.254) on the the 11th hop.

It's the same on all address, apart from 212.183.133.182. Hops 12-17 time out, then it reaches the destination on hop 18.

[Retired-James]

Hi 7ony,

Please take a look at our Sure Signal Troubleshooting thread. If this doesn’t resolve your query, please post your reply either below, or in the relevant thread, together with the details requested, including the following information.

Your speed test results from here.

Your ping test results from here.

Your external IP address from here.

The results of a traceroute.

Your Sure Signal serial number:

VSS Traceroute command

On a PC:

Click on Start and select Run

Type CMD into the Run box and press enter/click ok

A black box will appear.

In this box type tracert 212.183.133.177 press Enter

Paste the output of this command into your reply.

This will help us get the quickest possible resolution for you.

Thanks

James

[Scuffers]

currently on hold for the 'tech team'

My VSS looks like it;s on and OK, but it's doing nothing usfull, no phone is registered via it.

been like this all day...:smileyfrustrated:

[Scuffers]

update...

Apparently, they have been rolling out a firmware update, and for whatever reason, mine has not got it?

it's supposed to be being updated (remotley) now, so might be working again in a few hours?

Be helpfull if there was a service status page for users to see what's going on?

[7ony]

Below is the results:

Speed Test:

Ping - 42ms

Download - 4.09Mbps

Upload - 0.34Mbps

Ping Test:

Packet Loss - Unable to test

Ping - 48ms

Jitter - 1ms

Grade - B*

External IP Address:

IPv4 - 81.136.166.93

IPv6 - ::ffff:5188:a65d

Serial Numbers:

21197211572
21197211291

Tracetote Result:

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.16.1
  2    25 ms    24 ms    24 ms  host81-134-112-1.in-addr.btopenworld.com [81.134
.112.1]
  3    25 ms    24 ms    24 ms  213.120.182.141
  4    25 ms    25 ms    25 ms  213.120.161.82
  5    24 ms    24 ms    25 ms  213.120.182.67
  6    25 ms    26 ms    25 ms  31.55.164.107
  7    26 ms    25 ms    25 ms  109.159.248.89
  8    30 ms    33 ms    32 ms  core2-te-0-2-5-0.ilford.ukcore.bt.net [109.159.2
48.2]
  9    29 ms    30 ms    30 ms  peer2-xe2-1-0.telehouse.ukcore.bt.net [109.159.2
54.142]
 10    32 ms    29 ms    31 ms  t2c3-xe-1-2-1-0.uk-lon1.eu.bt.net [166.49.211.18
6]
 11    31 ms    29 ms    29 ms  166-49-211-254.eu.bt.net [166.49.211.254]
 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     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.