240 likes | 400 Views
IPv6. @RCTS2. cfriacas@fccn.pt GEANT-TF, Rome, 31/03/2003. PORTUGAL + Small Country + 10 million people + Lisbon: 2 million + Oporto: 1 million + Few Telcos = Circuits very expensive! + But GSM did great! + FCCN manages Research Network + STM-4 Connection to Geant (in Madrid)
E N D
IPv6 @RCTS2 cfriacas@fccn.pt GEANT-TF, Rome, 31/03/2003
PORTUGAL + Small Country + 10 million people + Lisbon: 2 million + Oporto: 1 million + Few Telcos = Circuits very expensive! + But GSM did great! + FCCN manages Research Network + STM-4 Connection to Geant (in Madrid) + One IXP, Gigapix, managed by FCCN + ccTLD .pt also managed by FCCN Portugal
Addressing • 2001:690::/32 for RCTS2 • 2001:07f8:000a::/48 for GIGAPIX (IXP)
Addressing Plan • /48s for each Access Point. (Universities, Labs, …) • /56s for each of the 12.000 schools and libraries connected to the Internet@School Network • /126 for point-to-point backbone links • We reserved some bits for future use • We did preemptive allocations to each access (94 /48s), can be seen on RIPEdb.
BGP4+ • Over 12 Tunnels and Native (RNP & Gigapix) • Getting around 430 prefixes (3FFE:: and 2001::) from peers • Filtering (using prefix-lists)
External Routing • Access to prefixes through • Access to : difficult, due to topology: high roundtrips • M40 will connect to GEANT, one C3640 is connecting to RNP natively (Brazil)
Cantino Link • Dual-Stack (IPv4/IPv6) • 2Mbps Circuit (E1) • First direct connection between Europe and South America (Lisbon-Rio) for R&D purposes • RNP has several ASes, and already got a 2001:: prefix from ARIN • Traffic Testing over IPv6 using MGEN6
Internal Routing • Current IGP: IS-IS • Running on 4 Junipers (3xM10 and 1xM40) and around a dozen Ciscos (1x12xxx, 3x75xx, 3x36xx, 6x26xx, …) • OSPFv3, in the future (3Q 2003?) • The network is basically «two stars», with its centers located in Lisbon and Oporto.
Topology • Core (Lisbon-Oporto) running on GigEthernet over a Lambda, and using a POS STM-1 as a backup. • Two Tunnel Gateways (in Lisbon and Oporto). • Members joining the IPv6 network establish a tunnel to both tunnel gateways. Keepalives are configured on all ends.
Topology - Known Problems #1 • Our Cisco 72xx (Access Routers) are not running an IOS version with IPv6 support: Main reason is T family not being accepted as best solution in terms of stability
Topology - Known Problems #2 • Some Academic Network members don’t have support contracts with some Vendors (ex:Cisco). This way they can’t get newer/improved IOS version with IPv6 support
Testbed • ~50% of our IPv6 routers are part of the TESTBED • Not easy to get memory upgrades for Cisco routers!!! (but already got some!) • Old PCs (i586/i686) reassigned to IPv6 testing are running Linux (Redhat)
Testing • Equipments: Cisco, 6WIND, PC/Zebra • Native connections over IPv6: • ATM (E3 and STM-1) • Giga/Fast/Ethernet • Serial/V.35 • Packet Over Sonet • E1 • HSSI
Transition Mechanisms • We are providing a 6to4 gateway to the world (2002:C188:2F6::1). • We will focus on NAT-PT. • Battery of tests being written (delayed due to backbone upgrade).
Gigapix • 18 Members • IPv6: Started March 2003, with 3 members peering natively.
Gigapix • 3 more LIRs in Portugal already have a RIPE allocation (KPN, ONI and NFSI) • The first two are already on the IXP, but only on IPv4. • NFSI is planning to connect soon (both on IPv4 and IPv6)
Work to do! • Transition Mechanisms • PT ccTLD IPv6 support supervision • Direct the Backbone to native connections • “Key-on-hand” IPv6 solutions for members • Security • Marketing
Last, but not least… • E-Mail • ip6adm@fccn.pt • helpdesk@fccn.pt • Links • http://www.ip6.fccn.pt