main_icn_My_Vodafone main_icn_Search main_icn_Chevron_right main_icn_Chevron_down main_icn_Close main_icn_Menu social-facebook social-google-plus social-linkedin social-twitter social-youtube main_icn_Community_or_Foundation main_icn_Location main_icn_Network_signal
Menu Toggle

Welcome to Vodafone Community

Broadband & Home Phone

Routing to vie.valve.net broken

2: Seeker

I'm a gamer and constantly need reliable access to the hosts

vie.valve.net

lux.valve.net

 

Althought those hosts are 99.99% uptime many times I cannot reach them from home. I can ssh or RDesktop into work and both host are reachable from there at the same time (i can leave the terminal window at home running a ping and at the same time ping from work). It goes away minutes at a time and seems to happen every hour or so.

 

From home when it breaks traceroute stops after the 1st hop in my router:

Desktop:~ $ traceroute vie.valve.net
traceroute to vie.valve.net (146.66.155.1), 64 hops max, 52 byte packets
 1  vodafone (192.168.1.1)  0.907 ms  0.616 ms  0.511 ms
 2  * * *

 

If I get ssh from home into another host in UK (it has BT internet) at the same time access to vie.valve.net is broken from home I can still reach it:

$ traceroute vie.valve.net
traceroute to vie.valve.net (146.66.155.1), 30 hops max, 60 byte packets
 1  10.20.24.1 (10.20.24.1)  0.319 ms  0.302 ms  0.338 ms
 2  81.145.207.249 (81.145.207.249)  1.410 ms  1.406 ms  1.395 ms
 3  194.75.118.34 (194.75.118.34)  6.268 ms  6.347 ms  6.427 ms
 4  core3-te0-0-0-5.faraday.ukcore.bt.net (213.121.193.88)  6.417 ms 109.159.255.215 (109.159.255.215)  6.500 ms  6.556 ms
 5  213.137.183.34 (213.137.183.34)  6.105 ms 213.137.183.36 (213.137.183.36)  6.203 ms 213.137.183.38 (213.137.183.38)  6.283 ms
 6  ldn-b3-link.telia.net (213.248.67.97)  6.525 ms  5.834 ms  5.891 ms
 7  ldn-bb3-link.telia.net (62.115.117.6)  8.136 ms  7.091 ms ldn-bb4-link.telia.net (62.115.116.240)  6.187 ms
 8  * hbg-bb4-link.telia.net (62.115.122.160)  18.271 ms *
 9  win-bb2-link.telia.net (62.115.119.51)  36.833 ms  36.818 ms  36.818 ms
10  win-b4-link.telia.net (62.115.136.227)  38.147 ms win-b4-link.telia.net (62.115.112.195)  37.427 ms win-b4-link.telia.net (62.115.136.155)  38.390 ms
11  vie.valve.net (146.66.155.1)  38.021 ms valve-ic-156665-win-b4.c.telia.net (195.12.255.186)  37.558 ms vie.valve.net (146.66.155.1)  38.007 ms

 

From home when it works the hops are:

Desktop:~ $ traceroute vie.valve.net
traceroute to vie.valve.net (146.66.155.1), 64 hops max, 52 byte packets
1 vodafone (192.168.1.1) 0.940 ms 0.617 ms 0.596 ms 2 host-212-158-250-37.dslgb.com (212.158.250.37) 8.600 ms 8.763 ms 8.188 ms 3 63.130.105.134 (63.130.105.134) 10.746 ms 10.842 ms 10.715 ms 4 ae13-100-xcr1.ltw.cw.net (195.2.23.77) 11.623 ms 11.364 ms 15.789 ms 5 ae27.0-xcr1.hex.cw.net (195.2.28.149) 17.470 ms 15.131 ms 15.942 ms 6 ldn-b4-link.telia.net (62.115.61.190) 34.796 ms 18.003 ms 19.607 ms 7 ldn-bb3-link.telia.net (62.115.134.134) 11.848 ms ldn-bb4-link.telia.net (62.115.134.138) 17.854 ms ldn-bb3-link.telia.net (62.115.134.134) 22.833 ms 8 hbg-bb1-link.telia.net (80.91.249.11) 24.426 ms 114.448 ms hbg-bb4-link.telia.net (62.115.122.160) 33.653 ms 9 win-bb2-link.telia.net (62.115.119.51) 55.010 ms prag-bb1-link.telia.net (62.115.139.209) 41.233 ms 46.653 ms 10 win-b4-link.telia.net (62.115.137.19) 58.834 ms win-b4-link.telia.net (213.155.132.177) 56.169 ms win-b4-link.telia.net (62.115.137.23) 53.043 ms 11 vie.valve.net (146.66.155.1) 56.776 ms valve-ic-156665-win-b4.c.telia.net (195.12.255.186) 40.481 ms 41.371 ms

 

Oddly routes to other hosts seem fine (note when I cannot traceroute I also cannot ping the address).

For me it seems something is breaking when you are updating routing tables or something on those lines.

View more options
7 REPLIES
Moderator

So one of our Broadband team can take a look into your query and help you further @kursancew, please contact us by following the instructions in this private message.

View more options
2: Seeker

Still not sorted, outrageous. I wrote a script last night and left it running overnight to track when things go wrong:

 

****** OUTAGE START: Sat 30 Jun 2018 00:29:36 BST
****** OUTAGE END: Sat 30 Jun 2018 00:32:36 BST
****** OUTAGE START: Sat 30 Jun 2018 03:51:32 BST
****** OUTAGE END: Sat 30 Jun 2018 03:51:38 BST
****** OUTAGE START: Sat 30 Jun 2018 03:52:28 BST
****** OUTAGE END: Sat 30 Jun 2018 03:52:33 BST
****** OUTAGE START: Sat 30 Jun 2018 03:53:11 BST
****** OUTAGE END: Sat 30 Jun 2018 03:53:20 BST
****** OUTAGE START: Sat 30 Jun 2018 03:53:56 BST
****** OUTAGE END: Sat 30 Jun 2018 03:54:05 BST
****** OUTAGE START: Sat 30 Jun 2018 03:54:20 BST
****** OUTAGE END: Sat 30 Jun 2018 03:54:30 BST
****** OUTAGE START: Sat 30 Jun 2018 07:15:52 BST
****** OUTAGE END: Sat 30 Jun 2018 07:16:07 BST
****** OUTAGE START: Sat 30 Jun 2018 09:16:56 BST
****** OUTAGE END: Sat 30 Jun 2018 09:17:00 BST
****** OUTAGE START: Sat 30 Jun 2018 11:17:38 BST
****** OUTAGE END: Sat 30 Jun 2018 11:17:43 BST
****** OUTAGE START: Sat 30 Jun 2018 13:18:32 BST
****** OUTAGE END: Sat 30 Jun 2018 13:18:47 BST
****** OUTAGE START: Sat 30 Jun 2018 14:39:47 BST
****** OUTAGE END: Sat 30 Jun 2018 14:40:02 BST

 

View more options
2: Seeker

Try changing your DNS to 8.8.8.8,4.4.4.4

View more options
2: Seeker

Did you get this resolved? Having exactly the same issue with the WOT servers and Steam. 

View more options
2: Seeker

No

absolute rubbish, very annoying I keep getting low prio and lose me because I get disconnected mid games.

its very spurious, sometimes resolves very quickly sometimes in 10 minutes

View more options
2: Seeker

And even worse the people who I can talk on Vodafone are clueless, all they know is suggesting to use a different dns, reboot my router or connect it to the service socket while the problem is clearly in their backbone network routing table update.

but to be honest last week I played 4 or 5 games without dropping out, i’ll wait and see

View more options
2: Seeker

Well that's annoying to hear.

Had a reasonable run tonight with minimal spikes.
Running pingplotter and it quite clear that the issue is caused by either 212.158.250.37 or, earlier in the evening, ae13-600-xcr1.ltw.cw.net

Funny thing is, running a diagnostic test on the router seems to resolve the problem when it's a 100% loss over a few minutes, plus whilst the packet loss is going on, the router fails 'connectivity test;, but I can still surf the internet.. Go figure. 


View more options