Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
New Contributor
•
2 Messages
Closed
Hi,
I am unable to get to, ping or trace route raspbian.org, you appear to be blocking access to this site? Can someone please look into why this is being done and either fix it or let me know the reasoning?
Thanks,
Discussions
•
Updated
3.7K
4
0
0
They don’t care
Discussions
1
0
Outages
Discussions
1
Daily outages
Discussions
2
0
SSID & Password
Discussions
1
0
Variety pack
Discussions
1
0
Wifi 7
Discussions
1
0
Frequent Outages
Discussions
1
Outages
Discussions
1
Variety pack
Discussions
1
0
ChrisL
Former Moderator
•
C:\Users\Home User>ping raspbian.org
Pinging raspbian.org [5.153.225.206] with 32 bytes of data:
Reply from 5.153.225.206: bytes=32 time=99ms TTL=49
Reply from 5.153.225.206: bytes=32 time=99ms TTL=49
Reply from 5.153.225.206: bytes=32 time=100ms TTL=49
Reply from 5.153.225.206: bytes=32 time=99ms TTL=49
Ping statistics for 5.153.225.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 100ms, Average = 99ms
0
0
Health_Edge
+5 more
Valued Contributor III
•
Is this a issue accessing it from the Pi or any computer on the network? I can also confirm I can get to the site. Who are you using as a DNS and are you using any kind of proxy?
Tracing route to raspbian.org [5.153.225.206]
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out. (I block this)
3 8 ms 7 ms 8 ms wwcksysc01-gex0103000.ri.ri.cox.net [68.9.8.13]
4 12 ms 8 ms 8 ms ip98-190-33-32.ri.ri.cox.net [98.190.33.32]
5 7 ms 23 ms 8 ms provdsrj01-ae3.0.rd.ri.cox.net [98.190.33.20]
6 13 ms 13 ms 13 ms 68.1.5.157
7 14 ms 16 ms 18 ms xe-11-2-1.edge1.NewYork1.Level3.net [4.78.132.29
]
8 95 ms 95 ms 95 ms vlan80.csw3.NewYork1.Level3.net [4.69.155.190]
9 95 ms 95 ms 94 ms ae-81-81.ebr1.NewYork1.Level3.net [4.69.134.73]
10 98 ms 95 ms 95 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
11 95 ms 94 ms 95 ms ae-46-46.ebr2.Amsterdam1.Level3.net [4.69.143.73
]
12 95 ms 94 ms 94 ms ae-24-24.ebr1.Amsterdam1.Level3.net [4.69.143.65
]
13 96 ms 95 ms 95 ms ae-5-5.car2.Manchesteruk1.Level3.net [4.69.143.4
1]
14 95 ms 94 ms * ae-11-11.car1.Manchesteruk1.Level3.net [4.69.133
.97]
15 101 ms 101 ms 101 ms te3-5.cr2.man.bytemark.co.uk [195.50.119.78]
16 107 ms 101 ms 101 ms po12.cr1.man.bytemark.co.uk [91.223.58.132]
17 106 ms 104 ms 101 ms te0-1.cr1.lds.bytemark.co.uk [91.223.58.69]
18 103 ms 104 ms 103 ms po1.cr1.yrk.bytemark.co.uk [91.223.58.76]
19 104 ms 103 ms 102 ms raspbian.org [5.153.225.206]
Trace complete.
0
0
GlennDCitrix
New Contributor
•
Thanks for responding. So it appears to be something with my Router after all, which is really odd as it's only a month or two old and has not had any configuration changes made to it that would block any website. Going to try digging around in it some more and if nothing turns up I'll do a factory reset and try that.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Factory reset? ::blink:: That doesn't sound like the mind set of someone programming a Pi. Don't you want to know what the problem is?
What kind of router do you have? How do you have DNS set up?
What happens when you ping the domain? Does it not resolve to a IP or does it resolve, but not route?
0
0