IPv6

1
IPv6

• _at_RCTS2

cfriacas_at_fccn.pt GEANT-TF, Rome, 31/03/2003
2
Portugal
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
3
History 6bone
4
History - Linux
5
Addressing

• 2001690/32 for RCTS2
• 200107f8000a/48 for GIGAPIX (IXP)

6
Addressing Plan

• /48s for each Access Point. (Universities, Labs,
  )
• /56s for each of the 12.000 schools and libraries
  connected to the Internet_at_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.

7
BGP4

• Over 12 Tunnels and Native (RNP Gigapix)
• Getting around 430 prefixes (3FFE and 2001)
  from peers
• Filtering (using prefix-lists)

8
BGP4 Map
9
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)

10
Cantino Link

• Dual-Stack (IPv4/IPv6)
• 2Mbps Circuit (E1)
• First direct connection between Europe and South
  America (Lisbon-Rio) for RD purposes
• RNP has several ASes, and already got a 2001
  prefix from ARIN
• Traffic Testing over IPv6 using MGEN6

11
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.

12
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.

13
Network Diagram
14
Members
15
Tunnels Traffic (Comparative)
16
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

17
Topology - Known Problems 2

• Some Academic Network members dont have support
  contracts with some Vendors (exCisco).
• This way they cant get newer/improved IOS
  version with IPv6 support

18
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)

19
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

20
Transition Mechanisms

• We are providing a 6to4 gateway to the world
  (2002C1882F61).
• We will focus on NAT-PT.
• Battery of tests being written (delayed due to
  backbone upgrade).

21
Gigapix

• 18 Members
• IPv6 Started March 2003, with 3 members peering
  natively.

22
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)

23
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

24
Last, but not least

• E-Mail
• ip6adm_at_fccn.pt
• helpdesk_at_fccn.pt
• Links
• http//www.ip6.fccn.pt