Hi all,
Does BT block IP ranges?
Just got FTTP installed yesterday and i'm having issues VPN'ing into my remote Virtual server (I've a server hosted on Google Cloud that I use to keep my networking skills up to date as well as playing around on safely)
My old ISP (PlusNet) their was no issue connection via SSH or a VPN but since I've switched to BT I've not been able to access it.
Basic "pings" go through but other services won't connect. Yeah it could be a "google problem" but it's strange it's only started when I move to BT.
Ping:
ping -c 5 35.209.113.89
PING 35.209.113.89 (35.209.113.89) 56(84) bytes of data.
64 bytes from 35.209.113.89: icmp_seq=1 ttl=51 time=117 ms
64 bytes from 35.209.113.89: icmp_seq=2 ttl=51 time=116 ms
64 bytes from 35.209.113.89: icmp_seq=3 ttl=51 time=117 ms
64 bytes from 35.209.113.89: icmp_seq=4 ttl=51 time=116 ms
64 bytes from 35.209.113.89: icmp_seq=5 ttl=51 time=116 ms
--- 35.209.113.89 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 116.043/116.350/116.711/0.260 ms
Tracepath:
tracepath 35.209.113.89
1?: [LOCALHOST] pmtu 1492
1: _gateway 0.856ms
1: _gateway 0.667ms
2: no reply
3: no reply
4: 31.55.185.184 15.001ms asymm 6
5: core1-hu0-8-0-5.colindale.ukcore.bt.net 15.026ms asymm 6
6: peer7-et-0-1-1.telehouse.ukcore.bt.net 22.894ms asymm 7
7: 166-49-214-194.gia.bt.net 13.427ms
8: ix-ae-68-0.tcore1.ldn-london.as6453.net 14.006ms
9: if-ae-65-2.tcore2.ldn-london.as6453.net 106.571ms asymm 12
10: if-ae-32-2.tcore3.nto-newyork.as6453.net 96.131ms asymm 11
11: if-ae-26-2.tcore1.ct8-chicago.as6453.net 113.621ms asymm 9
12: 206.82.141.94 106.814ms asymm 15
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1492
Resume: pmtu 1492
Solved! Go to Solution.
Not a BT problem, the IP you used shows exactly the same for me using my VPN, which you didn't use for your TracePath.
I'm with a different provider so it points to a problem elsewhere.
Thanks,
Seems to be working as normal today.
Didn't mind the IP address being exposed, I had to reset my router anyway due to the Advances Digital Phone "Synchronising handset data" error/bug/annoyance, so I've a new IP address.