Hi,
Since November 2006 we announce our 3 new prefixes:
194.60.78.0/24
194.60.204.0/24
194.153.114.0/24
from new AS41961.
It seems that somewhere our announcements are blocked probably due to bogon
lists.
Our ASN is is in AS block allocated by RIPE on 13 April 2006 then somebody can
have it still in as-path ACLs.
Could you please check your configuration or help us to isolate the problem?
Hi Sebastian,
SRusek@axit.pl (Sebastian Rusek) wrote:
Since November 2006 we announce our 3 new prefixes:
194.60.78.0/24
194.60.204.0/24
194.153.114.0/24from new AS41961.
It seems that somewhere our announcements are blocked probably due to bogon
lists.
To make it easier for everyone - could you provide hosts in each
network that are pingable?
Yours,
Elmar.
They are seen here, through Cogent :
*> 194.60.78.0 38.101.161.116 4001 0 174 13237 41961 i
*> 194.60.204.0 38.101.161.116 4001 0 174 13237 41961 i
*> 194.153.114.0 38.101.161.116 4001 0 174 13237 41961 i
Regards
Marshall
Dnia czwartek 04 stycznia 2007 15:06, napisałeś:
now pingable addresses are:
194.60.78.254
194.60.204.254
194.153.114.254They should be accessible via LambdaNET. Routes inside LambdaNET can be
diffrent to each address.
Everything looks fine from here (AS 2116), prefixes reachable and
addresses pingable. Example traceroute below.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
traceroute to 194.60.78.254 (194.60.78.254), 64 hops max, 60 byte packets
1 nethelp-gw (195.1.209.46) 1.190 ms 1.139 ms 1.144 ms
2 gi1-0-6000034.ar4.o-d.no.catchbone.net (81.0.129.174) 5.982 ms 6.819 ms 6.617 ms
3 ge-0-2-3-15.cr1.osls.no.catchbone.net (193.75.3.165) 6.138 ms 5.709 ms 6.145 ms
4 c10G-ge-3-0-0.cr2.osls.no.catchbone.net (81.0.128.54) 5.824 ms 6.041 ms 5.841 ms
5 c2488-so-1-3-0.cr1.mejv.se.catchbone.net (193.75.3.239) 13.195 ms 13.066 ms 13.011 ms
6 ge-0-1-0.br1.stcy.se.catchbone.net (81.0.128.210) 13.321 ms 13.379 ms 19.719 ms
7 netnod-ge-a.sto-1-eth020-15.se.lambdanet.net (194.68.123.141) 13.021 ms 13.050 ms 13.328 ms
8 HAN-7-pos720-0.de.lambdanet.net (81.209.190.17) 34.421 ms 36.609 ms 34.856 ms
9 DUS-1-pos012.de.lambdanet.net (217.71.105.126) 39.065 ms 38.768 ms 38.776 ms
10 217.71.96.66 (217.71.96.66) 41.873 ms 41.597 ms 41.889 ms
11 FRA-2-pos600.de.lambdanet.net (217.71.96.102) 42.342 ms 42.251 ms 42.032 ms
12 194.60.78.254 (194.60.78.254) 42.655 ms 42.673 ms 42.662 ms
Sebastian Rusek wrote:
Dnia czwartek 04 stycznia 2007 15:06, napisałeś:
Since November 2006 we announce our 3 new prefixes:
194.60.78.0/24
194.60.204.0/24
194.153.114.0/24from new AS41961.
It seems that somewhere our announcements are blocked probably due to
bogon lists.To make it easier for everyone - could you provide hosts in each
network that are pingable?now pingable addresses are:
194.60.78.254
194.60.204.254
194.153.114.254They should be accessible via LambdaNET. Routes inside LambdaNET can be diffrent to each address.
From one location, things die as soon as they hit AT&T, another location things work perfectly.
From AS29979
jcheney@katahdin jcheney $ traceroute 194.60.78.254
traceroute to 194.60.78.254 (194.60.78.254), 30 hops max, 38 byte packets
1 66.231.214.33 (66.231.214.33) 0.689 ms 0.703 ms 0.607 ms
2 208.252.22.1 (208.252.22.1) 7.160 ms 7.948 ms 7.620 ms
3 12.125.39.69 (12.125.39.69) 9.630 ms !H * 10.049 ms !H
now pingable addresses are:
194.60.78.254
194.60.204.254
194.153.114.254From one location, things die as soon as they hit AT&T, another location things work perfectly.
I have a couple of networks off AT&T and I am not seeing these routes in my tables. I do see them off other networks, however.
-Don
And aren't seen through gblx. I also think I can't see those prefixes
through verizon.
Gustavo.
Marshall Eubanks wrote:
And aren't seen through gblx. I also think I can't see those prefixes
through verizon.
Also not seen via Telia (1299) or Level3 (3356).
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Yes, I should have made that clear, not received through Level 3 at AS 16517. (But, Cogent has them.)
Sebastian Rusek wrote:
Hi,
Since November 2006 we announce our 3 new prefixes:
[..]
Could you please check your configuration or help us to isolate the problem?
You could also check http://www.ris.ripe.net/ and use that tool to
determine exactly which networks are not seeing you and then contact
those operators to fix their setups.
And for people not peering with RIS yet, PEER! (info at the url)
Greets,
Jeroen
Qwest appears not show it (traceroute dies at the first IP in their network) and Cogent and LambdaNET show a jump from 90ms to 170ms between their networks (in two different places depending on IP tracerouted) - but it does go through.
Hi,
> Since November 2006 we announce our 3 new prefixes:
> 194.60.78.0/24
> 194.60.204.0/24
> 194.153.114.0/24
> from new AS41961.
> It seems that somewhere our announcements are blocked
> probably due to bogon lists.
I don't think this is anything to do with bogons. I see those routes
via Cogent and _only_ via Cogent - none of our other transit providers
have them at all.
I suspect a problem with your announcements themselves.
Not seeing any of the routes, or any routes from AS41961. UUNET, Sprint,
and AT&T connectivity.
Not seen from ASN7046
Since November 2006 we announce our 3 new prefixes:
194.60.78.0/24
194.60.204.0/24
194.153.114.0/24from new AS41961.
you may want to use the views from route-views.org and ripe's ris
project, as opposed to getting email from the very same folk who
contribute to them :).
looks to me as if the problem is very near you, perhaps even at
your border.
randy
not seeing any routes through Level3 or INAP
> And aren't seen through gblx. I also think I can't see those prefixes
> through verizon.
probably gustavo means verizonbusiness here, and probably vzb-US (as701),
it's in 702 though.
Well, the undocumented fact is that RIS does not accept multi-hop BGP peerings, which may somewhat limit its coverage.
Why then do I have one? They do such things, they indeed do.
-ako