CANLI
5 ASN PEERING YAPIYORIPv4 1.068.736 PREFIXIPv6 241.981 PREFIXRPKI 1.003.746 VRP17 FENER ÇEVRİMİÇİSON GÜNCELLEME AZ ÖNCE
TREN
Rasat
RASAT / AS

AS42064

France IX Services SASU
0 duyuru0 upstream0 komşu
KAYITRIPE
aut-num
AS42064
as-name
FRANCE-IX-MRS-AS
remarks
-------------------------------------------------------------
remarks
Information: http://www.franceix.net/
remarks
Peering requests: [email protected]
remarks
Members technical support: [email protected]
remarks
-------------------------------------------------------------
remarks
The following communities can be used by members on our Route-Servers:
remarks
remarks
CDN Control (handled by AS39801, connected to the RS) :
remarks
40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks
39801:990:0 - DO NOT announce to any local CDN cache
remarks
39801:990:1 - DO NOT announce to Netflix Cache [Default]
remarks
39801:991:0 - DO announce to all local CDN caches
remarks
39801:991:1 - DO announce to Netflix OpenConnect cache (and add 40027:40000)
remarks
-------------------------------------------------------------
remarks
Large BGP communities (RFC8092) :
remarks
RFC8092 communities ("Large" BGP communities) are the preferred way
remarks
of signalling between peers and the RS. Prefer using them !!!
remarks
remarks
Communities handled by the RS (peers can set on routes announced to the RS):
remarks
42064:0:0 = Do not send route to any peer unless explicitly signaled
remarks
42064:0:peeras = Do not send route to this peer AS
remarks
42064:1:0 = [DEFAULT] Send route to all peers
remarks
42064:1:peeras = DO Send route to this peer AS (if 42064:0:0 specified)
remarks
42064:101:peeras = Prepend 1x to this peer AS
remarks
42064:102:peeras = Prepend 2x to this peer AS
remarks
42064:103:peeras = Prepend 3x to this peer AS
remarks
42064:901:peeras = Set MED to 50 for this peer AS
remarks
42064:902:peeras = Set MED to 100 for this peer AS
remarks
42064:903:peeras = Set MED to 200 for this peer AS
remarks
remarks
Communities set by the RS (on routes peers receive):
remarks
42064:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks
42064:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks
42064:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks
42064:1001:6 [*] = IRR NotFound : No IRR route object for prefix
remarks
remarks
Communities for filtered routes, only visible on looking-glass:
remarks
(routes tagged with these communities are NOT re-announced to RS peers)
remarks
42064:1000:4 = RPKI Invalid
remarks
42064:1001:4 = IRR Invalid/NotFound
remarks
42064:1001:5 = IRR Invalid - Origin AS not in peer's AS-Set
remarks
42064:1101:9 = FILTERED : IRR Invalid/NotFound
remarks
42064:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks
42064:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks
42064:1101:13 = FILTERED : RPKI Invalid
remarks
42064:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks
remarks
[*] = A route without a valid IRR route object is only re-announced if:
remarks
- the origin AS is in the peer's AS-Set
remarks
- AND there is a VALID ROA for the origin AS
remarks
-------------------------------------------------------------
remarks
Legacy/"standard" BGP communities (RFC1997):
remarks
RFC1997 BGP communities are still accepted, but their use will be
remarks
reduced progressively. Please use RFC8092 "Large" communities instead.
remarks
remarks
0:peer-as = Do NOT send route to this peer as
remarks
0:42064 = Do NOT send route to any peer
remarks
42064:peer-as = DO Send route to this peer as
remarks
42064:42064 = DO Send route to all peers [Default]
remarks
remarks
The following communities are applied by the route-server:
remarks
42064:64611 = Prefix received from a peer on RS1 Marseille
remarks
42064:64612 = Prefix received from a peer on RS2 Marseille
remarks
42064:64648 = Prefix received from a FranceIX Lille peer
remarks
42064:64649 = Prefix received from a FranceIX Marseille peer
remarks
42064:64650 = Prefix received from a FranceIX Paris peer
remarks
42064:64652 = Prefix received from a FranceIX Lyon/AURA peer
remarks
42064:64655 = Prefix received from a FranceIX Toulouse peer
remarks
42064:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks
42064:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks
42064:65012 = Prefix has RPKI status: VALID
remarks
42064:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks
42064:65023 = Prefix has RPKI status: UNKNOWN
remarks
remarks
65101:peer-as = Prepend 1x to this peer
remarks
65102:peer-as = Prepend 2x to this peer
remarks
65103:peer-as = Prepend 3x to this peer
remarks
65201:peer-as = Set MED 50 to this peer
remarks
65202:peer-as = Set MED 100 to this peer
remarks
65203:peer-as = Set MED 200 to this peer
remarks
remarks
*************************************************************
remarks
** All communities are evaluated on a "first match win" basis
remarks
*************************************************************
remarks
All other BGP communities in the public range
remarks
(1-64495:x, 1-64495:x:y) and (131072-4199999999:x:y)
remarks
will be preserved and passed along by the route-servers
remarks
-------------------------------------------------------------
remarks
Well-known communities are propagated to all peers
remarks
65535:666 = BLACKHOLE [RFC7999] - interpreted
remarks
more details at https://www.franceix.net/en/technical/blackholing/
remarks
All other well-known communities are NOT interpreted and passed along to peers
remarks
-------------------------------------------------------------
remarks
You can filters prefixes with our AS-SET :
remarks
All members AS-SETs : AS-FRANCEIX-MRS
remarks
All members AS List : AS-FRANCEIX-MRS-LIST
remarks
Route-Servers members AS-SETs : AS42064:AS-MEMBERS
remarks
Route-Servers members AS List : AS42064:AS-MEMBERS:AS-MRS-RS
remarks
Please make sure to have at least one of theses lines in your aut-num object :
remarks
export: to AS42064 announce ASxxxx
remarks
export-via: AS42064 to AS-ANY announce ASxxxx
remarks
export-via: afi ipv6.unicast AS42064 to AS-ANY announce ASxxxx
remarks
mp-export: afi ipv4.unicast,ipv6.unicast to AS42064 announce ASxxxx
remarks
(ASxxxx can be your ASN or your AS-SET)
remarks
-------------------------------------------------------------
remarks
Routes rejected:
remarks
- Prefix too short : IPv4 :
remarks
- Prefix too long : IPv4 : >/24, IPv6 : >/48
remarks
- RFC5735 prefixes for IPv4 (includes RFC1918, RFC6598, and others)
remarks
- RFC5156 prefixes for IPv6
remarks
- RFC6996 - routes containing private ASNs in path
remarks
- RPKI Invalid - routes having ROAs, and no ROA matches the announce
remarks
- IRR AS Invalid - routes whose origin is NOT in Peers AS-Set
remarks
- Invalid origin - routes that have NO valid ROA and NO matching IRR route object
remarks
- routes where next_hop != announcing_peer
remarks
- routes where first_ASN != peer_ASN
remarks
- routes already having the OTC attribute (RFC9234) set
remarks
-------------------------------------------------------------
remarks
We support ADD-PATHS. If negotiated via BGP, you will receive extended NLRI.
remarks
We support RFC9234 - our role is RS_Server.
remarks
We set the OTC attribute
remarks
If you implement RFC9234 your role will be RS_Client
remarks
-------------------------------------------------------------
remarks
==PEERS==
import
from AS42064:AS-MEMBERS:AS-MRS-RS accept AS42064:AS-MEMBERS
export
to AS42064:AS-MEMBERS:AS-MRS-RS announce AS42064:AS-MEMBERS
remarks
==END PEERS==
admin-c
FXAD1-RIPE
status
ASSIGNED
created
2020-03-19T14:36:14Z
last-modified
2025-10-03T15:26:14Z
source
RIPE

Kayıt, numaranın bağlı olduğu kayıt otoritesinden geliyor ve olduğu gibi gösteriliyor. Rasat bu bilgiyi üretmiyor, doğruluğu kaydı tutan tarafa ait. Tanıtıcılar RIPE veritabanınabağlı.