RIPE61 technical report
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

RIPE61 technical report

on

  • 468 views

 

Statistics

Views

Total Views
468
Views on SlideShare
468
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

RIPE61 technical report Presentation Transcript

  • 1. RIPE 61Technical ReportErik Romijn <eromijn@ripe.net>Senior Software Engineer
  • 2. IntroductionErik Romijn - RIPE 61 2
  • 3. The Technical Team Ben, Benedetto, Brian, Darius, Erik, Menno, Oleg, Paolo, Răzvan, SjoerdErik Romijn - RIPE 61 3
  • 4. What Do We Do?• If it has wires, it’s ours – (except for beamers, lighting, audio and stenography)• Some highlights: – Local servers running DHCP(v6), IRC, ripe61.ripe.net, registration software, ... – Webcasts / audiocast / recordings – (Wireless) network – Presentation system – Services centreErik Romijn - RIPE 61 4
  • 5. What do we do?Erik Romijn - RIPE 61 5
  • 6. Network setup RIPE meeting venuePublic network Service network Private network Wireless Streaming Registration Terminal room TTM / Rosie Network mgt Erik Romijn - RIPE 61 6
  • 7. Network setupErik Romijn - RIPE 61 7
  • 8. Network setupErik Romijn - RIPE 61 8
  • 9. New setupsErik Romijn - RIPE 61 9
  • 10. Presentation system in side roomErik Romijn - RIPE 61 10
  • 11. Presentation system in side roomErik Romijn - RIPE 61 11
  • 12. Remote switcherErik Romijn - RIPE 61 12
  • 13. New serversErik Romijn - RIPE 61 13
  • 14. iPad/iPhone streamErik Romijn - RIPE 61 14
  • 15. Video stream for breakout roomErik Romijn - RIPE 61 15
  • 16. Terminal room Mac Mini’sErik Romijn - RIPE 61 16
  • 17. Issues encounteredErik Romijn - RIPE 61 17
  • 18. IPv6 Duplicate Address Detection (DAD)• An IPv6 stack keeps a new address in tentative state – Until DAD is completed – This is usually completed after a few seconds• On the meeting wireless, this sometimes takes up to a minute, having no IPv6 connectivity in that time• Initial investigations show possible blocking of multicast by the switches in certain conditions• Thanks to Lorenzo Colitti & Jen Linkova from GoogleErik Romijn - RIPE 61 18
  • 19. Other IPv6 issues• Several issues in upstreams of upstreams – heise.de intermittently unreachable over IPv6 – packetloss Wednesday morning to/from some destinations – beyond our control• Printer advertising IPv6 on Bonjour, but not actually accepting printing jobs over it – Delay of several minutes in printing – Removed IPv6 address from printerErik Romijn - RIPE 61 19
  • 20. Slowness on ripe61.ripe.net• ripe61.ripe.net intermittently slow in the first couple of days• Resolved on Tuesday – Added extra memory to the virtual machine – Added two layers of caching to the webserver – WP Super Cache plugin for WordPress – APC for PHP cachingErik Romijn - RIPE 61 20
  • 21. Access point reachabilityErik Romijn - RIPE 61 21
  • 22. StatsErik Romijn - RIPE 61 22
  • 23. TTM ObservationsErik Romijn - RIPE 61 23
  • 24. TTM ObservationsErik Romijn - RIPE 61 24
  • 25. TTM observations Internet Office of the Holy See: inbound IPv6 latency 50x lowerErik Romijn - RIPE 61 25
  • 26. TTM observationstraceroute to tt134.ripe.net (212.77.0.252), 64 hops max, 52byte packets 1 gw.mtgrtr-j1.ripemtg.ripe.net 4.172 ms 3.999 ms [...] 2 ru-ripe-meeting-l1-rt-rm2.rm2.garr.net 1.232 ms [...] 3 83-103-94-182.ip.fastwebnet.it 28.082 ms 25.652 ms [...] 4 tt134.ripe.net 26.605 ms 26.882 ms 26.700 ms Internet Office of the Holy See: inbound IPv6 latency 50x lower Erik Romijn - RIPE 61 26
  • 27. tt134# /usr/local/bin/traceroute6 tt51 TTM observationstraceroute6 to tt51.ripe.net (2001:67c:64:44::51) from2a01:b8:0:1::2, 64 hops max, 12 byte packets 1 multigigapop-re.vatican.va 0.470 ms 0.427 ms 0.489 ms 2 2001:760:ffff:1c00::11 0.729 ms 10.395 ms 0.694 ms 3 rt-rm2-ru-ripe-meeting-l1 3.022 ms [...] 4 tt51 1.105 ms 1.028 ms 1.282 mstt134# /usr/local/bin/traceroute tt51traceroute to tt51.ripe.net (193.0.31.51): 1-30 hops, 38 bytepackets 1 multigigapop-re.vatican.va 0.303 ms 0.314 ms 0.224 ms 2 if-0-0-7.core1.RCT-Rome.as6453.net 0.462 ms [...] 3 if-7-0.core3.MLT-Milan.as6453.net 44.5 ms 8.38 ms [...] 4 208.178.58.109 24.5 ms 38.9 ms 25.1 ms 5 Dante-Milan-3.so-5-0-0.ar2.LIN1.gblx.net 24.4 ms [...] 6 rt1-mi1-rt-mi2.mi2.garr.net 24.6 ms 24.4 ms 24.5 ms 7 rt-mi2-rt-rm2.rm2.garr.net 24.4 ms 25.0 ms 24.6 ms 8 rt-rm2-ru-ripe-meeting-l1.rm2.garr.net See: ms [...] Internet Office of the Holy 28.1 24.9 ms 9 tt51.ripe.net (193.0.31.51) 24.8 ms 24.7 ms inbound IPv6 latency 50x lower Erik Romijn - RIPE 61 27
  • 28. RIPE Atlas monitoringErik Romijn - RIPE 61 28
  • 29. RIPE Atlas measurements: F-rootErik Romijn - RIPE 61 29
  • 30. Webcast 150 120Webcast viewers 90 60 30 0 15:00 17:00 8:00 10:00 12:00 14:00 16:00 18:00 9:00 11:00 13:00 15:00 17:00 8:00 10:00 12:00 14:00 Time (local) Other IPv4 Other IPv6 Venue IPv4 Venue IPv6 Office IPv4 Office IPv6 Erik Romijn - RIPE 61 30
  • 31. Uplink traffic Peak: 50 Mbit/s in, 21 Mbit/s out Average: 8 Mbit/s in, 6.3 Mbit/s outErik Romijn - RIPE 61 31
  • 32. IPv6 traffic 10.8% of upli traffic nk is IPv6 Peak: 9.3 Mbit/s in, 1.6 Mbit/s outAverage: 1.4 Mbit/s in, 208 kbit/s outErik Romijn - RIPE 61 32
  • 33. IPv6 traffic on the RIPE meeting network 100% of uplink traffic being IPv6 75 50 25 0 60 62 64 66 68 70 72 74 76 78 80 82 84 RIPE meeting Erik Romijn - RIPE 61 Exponential Linear 33
  • 34. Wireless 24 base stations deployed Peak: 340 associationsErik Romijn - RIPE 61 34
  • 35. High-density access point distributionErik Romijn - RIPE 61 35
  • 36. Questions?Erik Romijn<opsmtg@ripe.net>