Request

kleefarr

Could some people who are on the Vodafone network please do..

1. Traceroute to www.vodafone.ie
2. Ping Test to the vodafone.ie IP address 213.233.129.155

And post their results please.

TIA.

Vico1612

From the HG658 itself
traceroute to www.vodafone.ie (213.233.129.155), 20 hops max, 38 byte packets
1 89.19.68.133 (89.19.68.133) 5.301 ms
2 89.19.68.110 (89.19.68.110) 5.399 ms
3 89.19.69.69 (89.19.69.69) 5.769 ms
4 213.233.129.76 (213.233.129.76) 5.244 ms
5 213.233.129.69 (213.233.129.69) 5.758 ms
6 213.233.129.76 (213.233.129.76) 5.817 ms
7 213.233.129.69 (213.233.129.69) 5.705 ms
8 213.233.129.76 (213.233.129.76) 149.489 ms
9 213.233.129.69 (213.233.129.69) 6.358 ms
10 213.233.129.76 (213.233.129.76) 5.745 ms
11 213.233.129.69 (213.233.129.69) 6.009 ms
12 213.233.129.76 (213.233.129.76) 6.269 ms
13 213.233.129.69 (213.233.129.69) 6.292 ms
14 *
15 213.233.129.69 (213.233.129.69) 6.721 ms
16 213.233.129.76 (213.233.129.76) 5.981 ms
17 213.233.129.69 (213.233.129.69) 6.553 ms
18 213.233.129.76 (213.233.129.76) 6.975 ms
19 213.233.129.69 (213.233.129.69) 6.515 ms
20 *

C:\Users\victo_000>ping 213.233.129.155

Pinging 213.233.129.155 with 32 bytes of data:
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

5starpool

C:\Users\D>tracert www.vodafone.ie

Tracing route to www.vodafone.ie [213.233.129.155]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 26 ms 25 ms 25 ms 89.19.64.135
3 29 ms 28 ms 26 ms 89.19.65.190
4 27 ms 26 ms 27 ms 89.19.69.77
5 29 ms 29 ms 69 ms 213.233.129.94
6 26 ms 28 ms 27 ms 213.233.129.76
7 27 ms 27 ms 27 ms 213.233.129.69
8 28 ms 28 ms 27 ms 213.233.129.76
9 27 ms 30 ms 27 ms 213.233.129.69
10 37 ms 27 ms 27 ms 213.233.129.76
11 27 ms 27 ms 41 ms 213.233.129.69
12 33 ms 27 ms 41 ms 213.233.129.76
13 27 ms 28 ms 53 ms 213.233.129.69
14 37 ms 27 ms 44 ms 213.233.129.76
15 53 ms 35 ms 32 ms 213.233.129.69
16 27 ms 32 ms 52 ms 213.233.129.76
17 27 ms 30 ms 31 ms 213.233.129.69
18 27 ms 44 ms 37 ms 213.233.129.76
19 29 ms 30 ms 42 ms 213.233.129.69
20 30 ms 43 ms 27 ms 213.233.129.76
21 59 ms 36 ms 35 ms 213.233.129.69
22 33 ms 39 ms 28 ms 213.233.129.76
23 60 ms 35 ms 29 ms 213.233.129.69
24 28 ms 29 ms 29 ms 213.233.129.76
25 29 ms 29 ms 44 ms 213.233.129.69
26 29 ms 28 ms 28 ms 213.233.129.76
27 38 ms 43 ms 54 ms 213.233.129.69
28 32 ms 37 ms 37 ms 213.233.129.76
29 46 ms 87 ms 29 ms 213.233.129.69
30 29 ms 29 ms 46 ms 213.233.129.76

Trace complete.

C:\Users\D>ping 213.233.129.155

Pinging 213.233.129.155 with 32 bytes of data:
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

nilhg

C:\Users\Dell>tracert www.vodafone.ie

Tracing route to www.vodafone.ie [213.233.129.155]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 6 ms 6 ms 6 ms 89.19.65.161
3 7 ms 7 ms 6 ms 89.19.64.234
4 7 ms 7 ms 7 ms 89.19.69.73
5 8 ms 8 ms 7 ms 213.233.129.254
6 8 ms 7 ms 7 ms 213.233.129.76
7 8 ms 8 ms 8 ms 213.233.129.69
8 7 ms 7 ms 7 ms 213.233.129.76
9 8 ms 8 ms 10 ms 213.233.129.69
10 7 ms 8 ms 7 ms 213.233.129.76
11 8 ms 8 ms 7 ms 213.233.129.69
12 7 ms 7 ms 8 ms 213.233.129.76
13 8 ms 8 ms 7 ms 213.233.129.69
14 8 ms 8 ms 8 ms 213.233.129.76
15 8 ms 9 ms 8 ms 213.233.129.69
16 8 ms 7 ms 8 ms 213.233.129.76
17 9 ms 9 ms 8 ms 213.233.129.69
18 8 ms 8 ms 8 ms 213.233.129.76
19 9 ms 11 ms 8 ms 213.233.129.69
20 9 ms 10 ms 8 ms 213.233.129.76
21 9 ms 9 ms 8 ms 213.233.129.69
22 9 ms 9 ms 8 ms 213.233.129.76
23 9 ms 9 ms 9 ms 213.233.129.69
24 9 ms 8 ms 9 ms 213.233.129.76
25 9 ms 9 ms 9 ms 213.233.129.69
26 9 ms 8 ms 9 ms 213.233.129.76
27 10 ms 9 ms 8 ms 213.233.129.69
28 9 ms 9 ms 9 ms 213.233.129.76
29 9 ms 9 ms 9 ms 213.233.129.69
30 9 ms 9 ms 9 ms 213.233.129.76

Trace complete.

C:\Users\Dell>ping 213.233.129.155

Pinging 213.233.129.155 with 32 bytes of data:
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Dell>ping www.vodafone.ie

Pinging www.vodafone.ie [213.233.129.155] with 32 bytes of data:
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.
Reply from 213.233.129.76: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Dell>

ED E

Somebody needs to reconfigure their big irons.

AlanS181824

Not a clue what you need this for but I'll oblige nonetheless!

traceroute to www.Vodafone.ie (213.233.129.155), 20 hops max, 38 byte packets
1 89.19.65.164 (89.19.65.164) 13.100 ms
2 89.19.64.230 (89.19.64.230) 13.166 ms
3 89.19.69.69 (89.19.69.69) 13.914 ms
4 213.233.129.76 (213.233.129.76) 13.158 ms
5 213.233.129.69 (213.233.129.69) 13.690 ms
6 213.233.129.76 (213.233.129.76) 13.384 ms
7 213.233.129.69 (213.233.129.69) 14.149 ms
8 213.233.129.76 (213.233.129.76) 61.158 ms
9 213.233.129.69 (213.233.129.69) 14.154 ms
10 213.233.129.76 (213.233.129.76) 13.700 ms
11 213.233.129.69 (213.233.129.69) 14.127 ms
12 213.233.129.76 (213.233.129.76) 13.981 ms
13 213.233.129.69 (213.233.129.69) 14.387 ms
14 213.233.129.76 (213.233.129.76) 14.155 ms
15 213.233.129.69 (213.233.129.69) 104.753 ms
16 *
17 213.233.129.69 (213.233.129.69) 15.566 ms
18 213.233.129.76 (213.233.129.76) 14.762 ms
19 213.233.129.69 (213.233.129.69) 14.493 ms
20 213.233.129.76 (213.233.129.76) 15.226 ms

I get a fail for the ping test and it's way too early for me to try figure out why!:pac:

kleefarr

ED E wrote: »

Somebody needs to reconfigure their big irons.

Seems like something needs reconfigured, but what do you mean by Big Irons?

Looks like there is reoccurring problem with the route hops and the ping test is weird as well.

I am convinced that a lot of the complaints coming from vodafone customers is related to this.

Its Only Ray Parlour

C:\Users\George>tracert www.vodafone.ie

Tracing route to www.vodafone.ie [213.233.129.155]
over a maximum of 30 hops:

1 5 ms 1 ms 1 ms 192.168.1.1
2 10 ms 6 ms 6 ms 89.19.68.133
3 11 ms 6 ms 6 ms 89.19.68.110
4 13 ms 6 ms 6 ms 89.19.69.69
5 10 ms 6 ms 6 ms 213.233.129.76
6 10 ms 6 ms 8 ms 213.233.129.69
7 10 ms 6 ms 6 ms 213.233.129.76
8 9 ms 6 ms 8 ms 213.233.129.69
9 10 ms 7 ms 7 ms 213.233.129.76
10 10 ms 7 ms 6 ms 213.233.129.69
11 9 ms 7 ms 7 ms 213.233.129.76
12 10 ms 7 ms 7 ms 213.233.129.69
13 7 ms 6 ms 7 ms 213.233.129.76
14 10 ms 8 ms 7 ms 213.233.129.69
15 10 ms 7 ms 9 ms 213.233.129.76
16 10 ms 7 ms 8 ms 213.233.129.69
17 10 ms 7 ms 8 ms 213.233.129.76
18 10 ms 7 ms 8 ms 213.233.129.69
19 10 ms 7 ms 8 ms 213.233.129.76
20 11 ms 9 ms 10 ms 213.233.129.69
21 9 ms 7 ms 7 ms 213.233.129.76
22 12 ms 7 ms 7 ms 213.233.129.69
23 9 ms 8 ms 7 ms 213.233.129.76
24 10 ms 7 ms 8 ms 213.233.129.69
25 10 ms 9 ms 7 ms 213.233.129.76
26 10 ms 7 ms 8 ms 213.233.129.69
27 10 ms 8 ms 8 ms 213.233.129.76
28 11 ms 8 ms 8 ms 213.233.129.69
29 8 ms 8 ms 8 ms 213.233.129.76
30 15 ms 8 ms 8 ms 213.233.129.69

Trace complete.

C:\Users\George>ping 213.233.129.155

Pinging 213.233.129.155 with 32 bytes of data:
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

ED E

kleefarr wrote: »

Seems like something needs reconfigured, but what do you mean by Big Irons?

Looks like there is reoccurring problem with the route hops and the ping test is weird as well.

I am convinced that a lot of the complaints coming from vodafone customers is related to this.

Its slang for larger routers like the ones vodafone would have on the network edges.

You need to get somebody to bring this to the attention of their network operations staff.

kleefarr

This is why I am collating results.
I intend to bring it to someones attention.

foggy_lad

traceroute to www.vodafone.ie (213.233.129.155), 20 hops max, 38 byte packets
1 89.19.68.133 (89.19.68.133) 14.698 ms
2 89.19.68.110 (89.19.68.110) 13.909 ms
3 89.19.69.69 (89.19.69.69) 14.164 ms
4 213.233.129.76 (213.233.129.76) 13.986 ms
5 213.233.129.69 (213.233.129.69) 14.137 ms
6 213.233.129.76 (213.233.129.76) 13.900 ms
7 213.233.129.69 (213.233.129.69) 14.141 ms
8 213.233.129.76 (213.233.129.76) 94.165 ms
9 213.233.129.69 (213.233.129.69) 14.677 ms
10 213.233.129.76 (213.233.129.76) 14.416 ms
11 213.233.129.69 (213.233.129.69) 14.185 ms
12 213.233.129.76 (213.233.129.76) 14.689 ms
13 213.233.129.69 (213.233.129.69) 14.854 ms
14 213.233.129.76 (213.233.129.76) 14.765 ms
15 213.233.129.69 (213.233.129.69) 101.638 ms
16 *
17 213.233.129.69 (213.233.129.69) 15.030 ms
18 213.233.129.76 (213.233.129.76) 14.335 ms
19 213.233.129.69 (213.233.129.69) 15.117 ms
20 213.233.129.76 (213.233.129.76) 14.553 ms


C:\Users\User>ping 213.233.129.155

Pinging 213.233.129.155 with 32 bytes of data:
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.
Reply from 213.233.129.69: TTL expired in transit.

Ping statistics for 213.233.129.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

kleefarr

Have posted this thread to Vodafone at home support forum..

Vodafone at Home

Not sure how else to get in contact with their Network Operations Staff.

Keep those reports coming guys.

Vico1612

kleefarr wrote: »

Have posted this thread to Vodafone at home support forum..

Vodafone at Home

Not sure how else to get in contact with their Network Operations Staff.

Keep those reports coming guys.

You could try the contact here :

http://whois.domaintools.com/213.233.129.69

kleefarr

Thanks, will forward him the info.

heroics

From router. Ping failed. Tracert below

traceroute to www.vodafone.ie (213.233.129.155), 20 hops max, 38 byte packets
1 89.19.65.161 (89.19.65.161) 13.400 ms
2 89.19.64.238 (89.19.64.238) 13.715 ms
3 89.19.69.77 (89.19.69.77) 14.043 ms
4 213.233.129.94 (213.233.129.94) 15.466 ms
5 *
6 213.233.129.69 (213.233.129.69) 68.971 ms
7 213.233.129.76 (213.233.129.76) 66.943 ms
8 213.233.129.69 (213.233.129.69) 67.723 ms
9 213.233.129.76 (213.233.129.76) 67.232 ms
10 213.233.129.69 (213.233.129.69) 67.461 ms
11 213.233.129.76 (213.233.129.76) 67.445 ms
12 213.233.129.69 (213.233.129.69) 67.991 ms
13 213.233.129.76 (213.233.129.76) 67.725 ms
14 213.233.129.69 (213.233.129.69) 68.269 ms
15 *
16 *
17 213.233.129.76 (213.233.129.76) 68.460 ms
18 213.233.129.69 (213.233.129.69) 68.809 ms
19 213.233.129.76 (213.233.129.76) 67.846 ms
20 *

kleefarr

That looks like the worst one yet Heroics.

Email sent to Alex Dempsey. No reply yet.

kleefarr

Still no reply. Guess they are busy.
Keep the reports coming guys.

kleefarr

Clearly no interest in replying to my query.

amdaley28

I have been following your saga on the vodafone forum as well.
The only thing I can suggest is move your problem further up the food chain but I'm not sure who that might be.
I too am waiting for a reply from vodafone about a vodafone sales agent lying to a potential customer in order to get a contract signature.
This will be my next port of call.
Maybe it might be of some use to you ?

"Escalation of a dispute
If your enquiry is a dispute with Vodafone and you are not satisfied with the response or solution from our Customer Service Representative, you can ask at any time for your enquiry to be transferred to a Customer Service Team Leader. If a Customer Service Team Leader is not immediately available, a call-back from them will be arranged within 24 hours.
Where the Customer Service Team Leader cannot resolve your dispute to your satisfaction, you can escalate your dispute to the Call Centre Manager. If you are calling outside office hours, your contact details will be taken and the Call Centre Manager will contact you after 9am or on the next working day, whichever is applicable.
In the event that you are still not satisfied you can put your complaint in writing to:
Customer and Channel Management
Vodafone
Second floor, Block B
MountainView
Leopardstown
Dublin 18
Your letter will be acknowledged within three working days.
In your correspondence, you must state clearly the background and nature of the complaint and the redress sought by you. The Office of Customer and Channel Management will endeavour to address your complaint within a reasonable period of time. The decision of The Office of Customer and Channel Management shall be final in all cases."

Alun

As ED_E says, it's a cock up somewhere in their infrastructure that's causing a routing loop. It's the same for me using UPC so it's not confined to Vodafone customers.

Marlow

It's not really a cock up.

It's quite simple. The IP in question ( 213.233.129.155 ) belongs to Vodafone and the overall range ( 213.233.128.0/22 ) is advertised to the internet.

So a traceroute will get as far as their network and depending on their routing setup also a good bit into the network.

Now, what happens next is that you reach the router, that dynamically allocates it to whatever device is going to get that ip.

Normally, if that device is not online, then the IP wouldn't answer. But because the parent router has no blackhole route configured, it just bounces back to the router before, who sends it back again. Hence the forth and back hops between the last 2 routers.

The issue here at hand: whatever device/host/router/server is supposed to have that IP is not online and the ip has not been allocated to it because of that.

That's all. Nothing more, nothing less.

In this case the host itself seems to be routing back on traceroute/ping. It's just a bad way of configurating thing. But ping/traceroute is not essential for service. Obviously their webserver answers correctly.

Why is it a problem to you ?

/M

kleefarr

Downstream SNR (dB) 5.6

Dropping again.

Laggy.

AlanS181824

kleefarr wrote: »

Downstream SNR (dB) 5.6

Dropping again.

Laggy.

Any response from them yet?

kleefarr

Nope.

kleefarr

Internet is particularly crap tonight!

SNR down 4.4. Grr.

May see some double posts tonight.

kleefarr

Visited the Eircom forum out of curiosity.

Have reached the conclusion that in general, Broadband at the moment is just farking rubbish. Seems it is country wide. :mad:

Cathalog

This is really interesting for me as I'm learning about networks and comms this year in college.
So it seems that somewhere in the network, two routers are routing packets to each other, causing this endless loop, yes?

But I'm curious.. How come, if I navigate to vodafone.ie in my browser, that the webpage loads without any problems?

dalta5billion

Cathalog wrote: »

This is really interesting for me as I'm learning about networks and comms this year in college.
So it seems that somewhere in the network, two routers are routing packets to each other, causing this endless loop, yes?

But I'm curious.. How come, if I navigate to vodafone.ie in my browser, that the webpage loads without any problems?

As someone said it's possible that ICMP packets are handled differently than other forms of traffic (e.g. a TCP connection) by this router.

Cathalog

dalta5billion wrote: »

As someone said it's possible that ICMP packets are handled differently than other forms of traffic (e.g. a TCP connection) by this router.

Ah yes, I missed Marlow's post somehow. Makes sense. Cheers!

kleefarr

Cathalog wrote: »

This is really interesting for me as I'm learning about networks and comms this year in college.
So it seems that somewhere in the network, two routers are routing packets to each other, causing this endless loop, yes?

But I'm curious.. How come, if I navigate to vodafone.ie in my browser, that the webpage loads without any problems?

I was hoping that a reply from Mr Dempsey may have explained this, but still no reply.

My main issue seems to be SNR down. It is not stable enough most of the time to be able to do much without dropping or lagging.
The efforts to check line, cabinet and settings out by Vodafone, who say there is nothing wrong, have not made any difference in the end. For a couple of weeks after the line check etc, there had been some improvement, but it's now back to square one.

I am on an unbundled 24mb line that was BT operated before Vodafone took over. I had no problems then.

kleefarr

I'm guessing, but I think this is not good is it?

Downstream output power (dBmV) 0