Has anyone come across a scenario where a carrier blocks IP traffic?
atlas.cogentco.com is the point which drops any packet to 95.130.9.210
The server is up and running internal monitoring says its OK. The ISP doesn't provide an interface to the Server so I can not log on to do any other validating.
Trace routes to any IP with the ISP (active or not)terminates in the ISP's network. Trace route from any point on the planet times out as soon as you hit atlas.cogentco.com
Any thoughts...
**IPonU could you ping from one of your servers at Digicube please and let me know.
Paul
On Wed, Oct 18, 2017 at 11:48:33PM +0000, Paul Templeton wrote:
Has anyone come across a scenario where a carrier blocks IP traffic?
atlas.cogentco.com is the point which drops any packet to 95.130.9.210
From where I sit it looks like .210 is null-routed. All of my ISPs drop the packets as soon as I hit their core network. By contrast, if I trace to .211 the trace goes as normal.
https://en.wikipedia.org/wiki/Null_route
Whoever runs that node will need to talk to their ISP support team to get it unblocked.
-andy
Whoever runs that node will need to talk to their ISP support team to
get it unblocked.
Thanks Andy - the reason I asked because its not with the Service Provider it's there upstream carrier - I have lodged a ticket with the carrier and waiting to here back. The ISP doesn't know anything. I haven't received any notification - it was dropped with no indication... Plus when have major international carriers started to drop IP address???
I'll keep you all posted...
Paul
On Thu, Oct 19, 2017 at 01:19:21AM +0000, Paul Templeton wrote:
Whoever runs that node will need to talk to their ISP support team to
get it unblocked.
Thanks Andy - the reason I asked because its not with the Service Provider it's there upstream carrier - I have lodged a ticket with the carrier and waiting to here back. The ISP doesn't know anything. I haven't received any notification - it was dropped with no indication... Plus when have major international carriers started to drop IP address???
Null routing a /32 is a standard technique for dealing with massive DDoS attacks. Your netblock is operated by DigiCube, they have someone who manages their BGP configuration and they are likely the one who needs to restore access (assuming whatever issue caused them to null route it is now resolved).
-andy
I don't really get it... You want me to ping 95.130.9.210 ?
If so, ping & traceroute works great from both my exits
Le mercredi 18 octobre 2017 à 23:48 +0000, Paul Templeton a écrit :
Has anyone come across a scenario where a carrier blocks IP traffic?
atlas.cogentco.com is the point which drops any packet to 95.130.9.210
The server is up and running internal monitoring says its OK. The ISP doesn't provide an interface to the Server so I can not log on to do any other validating.
Trace routes to any IP with the ISP (active or not)terminates in the ISP's network. Trace route from any point on the planet times out as soon as you hit atlas.cogentco.com
Any thoughts...
**IPonU could you ping from one of your servers at Digicube please and let me know.
Paul _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Andy Isaacson -
IPonU -
Paul Templeton