Hi folks,
I'm hoping someone can shed some light on the situation.
The 192.250.24 addresses have been reachable for several months in the current configuration with no reported issues. Since the 16th we have been hearing reports that destinations in that block are unavailable for some.
Several looking glass' report network not in table.
Can someone lend a hand? What is the best way to improve this situation? How do we find where the problem is?
B
The 192.250.24 addresses have been reachable for several months in the
current configuration with no reported issues. Since the 16th we have
been hearing reports that destinations in that block are unavailable
for some.Several looking glass' report network not in table.
Which ones?
Can someone lend a hand? What is the best way to improve this
situation? How do we find where the problem is?
Do you have a pingable IP address in the range which is problematic?
That would help others who are willing to debug your issue enormously.
Kind regards,
Job
> The 192.250.24 addresses have been reachable for several months in the
> current configuration with no reported issues. Since the 16th we have
> been hearing reports that destinations in that block are unavailable
> for some.
>
> Several looking glass' report network not in table.
Visible from here (AS 2116, Norway).
Do you have a pingable IP address in the range which is problematic?
That would help others who are willing to debug your issue enormously.
192.250.24.1 and 192.250.24.2 (for example) are pingable from 2116.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Same from AS 19171 (Canada). Shows up in all our transits and the IPs Steinar noted are pingable and traceable. We're currently reaching it through 577 812 23034. All our transits are showing the route through 812 (Rogers).
global crossing, XO
> The 192.250.24 addresses have been reachable for several months in
> the current configuration with no reported issues. Since the 16th we
> have been hearing reports that destinations in that block are
> unavailable for some.
Reachable from New Zealand -
192.250.24.0/24 *[BGP/170] 02:42:04, MED 0, localpref 90
AS path: 4826 174 812 23034 I, validation-state:
unverified
> to 175.45.102.9 via ae1.526
64 bytes from 192.250.24.1: icmp_seq=0 ttl=242 time=193.274 ms
64 bytes from 192.250.24.1: icmp_seq=1 ttl=242 time=196.312 ms
64 bytes from 192.250.24.1: icmp_seq=2 ttl=242 time=197.578 ms
Pingable from Montreal area as well
Gary Baribault
Courriel: gary@baribault.net
GPG Key: 0x685430d1
Fingerprint: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1
Hum, Traceroute is not as nice
traceroute to 192.250.24.1 (192.250.24.1), 30 hops max, 60 byte packets
1 GW (192.168.0.2) 0.459 ms 0.435 ms 0.422 ms
2 * * *
3 10.170.182.81 (10.170.182.81) 18.417 ms 18.711 ms 18.702 ms
4 216.113.124.126 (216.113.124.126) 16.611 ms 17.774 ms 17.774 ms
5 216.113.122.74 (216.113.122.74) 45.746 ms 46.035 ms 46.025 ms
6 144.232.7.250 (144.232.7.250) 44.529 ms 45.507 ms 45.178 ms
7 be3013.ccr21.ord03.atlas.cogentco.com (154.54.10.37) 38.741 ms
35.537 ms 37.036 ms
8 24.156.159.153 (24.156.159.153) 31.433 ms 32.658 ms 29.417 ms
9 24.156.144.177 (24.156.144.177) 34.106 ms 32.621 ms
van58-10-228-225.dynamic.rogerstelecom.net (209.148.228.225) 30.299 ms
10 24.156.144.126 (24.156.144.126) 30.339 ms 30.329 ms 30.055 ms
11 24.153.4.185 (24.153.4.185) 32.955 ms 34.112 ms 34.146 ms
12 gi-3-0-0.agw02.hrnr.phub.net.cable.rogers.com (24.153.7.82) 30.935
ms 32.375 ms 32.356 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * 206.186.1.10 (206.186.1.10) 37.869 ms
Gary Baribault
Courriel: gary@baribault.net
GPG Key: 0x685430d1
Fingerprint: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1
Hi,
looks like you mainly use one transit provider (AS812) or your other
transit providers correctly filter that prefix.
According to https://stat.ripe.net/data/prefix-routing-consistency/data.json?preferred_version=0.7&resource=192.250.24.0%2F22
there is no route object for the 192.250.24.0/22.
As a result the AS6453(TATA COMMUNICATIONS (AMERICA) INC) seemed to
have started filtering the prefix from AS812. Which reduced the
visibility of that prefix. Check the BGplay from the last days:
https://stat.ripe.net/192.250.24.0%2F22#tabId=routing
so create the correct route object and the prefix should come up over
the next day(s)
Also get the more specific route objects removed which point to other AS.
192.250.24.0/23 AS702
192.250.24.0/24 AS19294
Karsten
Karsten,
Thank you I am not sure why those 702 and 19294 old entries would still be there.
We have engaged 812 for help.
Shall I assume cleaning up the old entries will solve the problems?
The more specific objects are more cosmetic issue.
The main problem is the missing object for your /22. As well as your
AS23034 does not seem to be listed in AS-ROGERS:AS-CUSTOMERS
http://bgp.he.net/AS812#_irr
Karsten
Which ones ? I see you via just Rogers (AS812). Do you have transit with anyone else ?
TATA (AS6453) does not seem to know about you for some reason. They peer directly with Rogers. Perhaps the RADB entries are not there for you ? I think they create their filters based on that.
% whois -h whois.ra.net 192.250.24.0
route: 192.250.24.0/24
descr: PNAP-ACS inflow route
origin: AS19294
mnt-by: MAINT-SGNS
changed: corey.drake@sungard.com 20070201
source: RADB
route: 192.250.24.0/23
descr: Encompass Europe
origin: AS702
member-of: RS-UUNETNL
remarks: -------------------------------------------
remarks: E-mail is the preferred contact method!
remarks: -------------------------------------------
remarks: Please use one of the following addresses:
remarks: abuse@nl.uu.net - for abuse notification
remarks: support@nl.uu.net - for technical questions
remarks: info@nl.uu.net - for anything else
remarks: -------------------------------------------
notify: ripe-guardian@NL.UU.NET
mnt-by: AS1890-MNT
mnt-by: UUNET-MNT
changed: marcel@eu.uu.net 20011030
source: RIPE
remarks: ****************************
remarks: * THIS OBJECT IS NOT VALID
remarks: * Please note that all personal data has been removed from this object.
remarks: * To view the original object, please query the RIPE Database at:
remarks: * http://www.ripe.net/whois
remarks: ****************************
route: 192.250.24.0/24
descr: Descartes-Inflow-ATL
origin: AS19294
mnt-by: ASN-INFLOW-NET
changed: rdarrow@inflow.com 20040330
source: SAVVIS