RIPE 61 Technical Report · Service network Streaming TTM / Rosie Private network Registration Network mgt RIPE meeting venue. Erik Romijn - RIPE 61 Network setup 7. Erik Romijn -

RIPE 61Technical ReportErik Romijn <[email protected]>Senior Software Engineer

mailto:[email protected]

mailto:[email protected]

Erik Romijn - RIPE 61 2

Introduction

Erik Romijn - RIPE 61

Ben, Benedetto, Brian, Darius, Erik,

Menno, Oleg, Paolo, Răzvan, Sjoerd

The Technical Team

3


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 centre

4

http://ripe61.ripe.net



What do we do?

5


Network setup

6

Public networkWireless

Terminal room

Service networkStreaming

TTM / Rosie

Private networkRegistrationNetwork mgt

RIPE meeting venue


Network setup

7


Network setup

8


New setups


Presentation system in side room

10


Presentation system in side room

11


Remote switcher

12


New servers

13


iPad/iPhone stream

14


Video stream for breakout room

15


Terminal room Mac Mini’s

16


Issues encountered


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 upto 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 Google

18


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 printer

19


Slowness on ripe61.ripe.net

• ripe61.ripe.net intermittently slow in the firstcouple 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 caching

20




Access point reachability

21


Stats


TTM Observations

23


TTM Observations

24


TTM observations

25

Internet Office of the Holy See:

inbound IPv6 latency 50x lower


TTM observations

26



traceroute to tt134.ripe.net (212.77.0.252), 64 hops max, 52 byte 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


TTM observations

27



tt134# /usr/local/bin/traceroute6 tt51traceroute6 to tt51.ripe.net (2001:67c:64:44::51) from 2a01: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 ms

tt134# /usr/local/bin/traceroute tt51traceroute to tt51.ripe.net (193.0.31.51): 1-30 hops, 38 byte packets 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 28.1 ms [...] 9 tt51.ripe.net (193.0.31.51) 24.8 ms 24.7 ms 24.9 ms


RIPE Atlas monitoring

28


RIPE Atlas measurements: F-root

29


Webcast

30

0

30

60

90

120

150

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

Web

cast

vie

wer

s

Time (local)

Other IPv4 Other IPv6 Venue IPv4 Venue IPv6Office IPv4 Office IPv6


Uplink traffic

31

Peak: 50 Mbit/s in, 21 Mbit/s outAverage: 8 Mbit/s in, 6.3 Mbit/s out


IPv6 traffic

32

Peak: 9.3 Mbit/s in, 1.6 Mbit/s outAverage: 1.4 Mbit/s in, 208 kbit/s out

10.8% of uplink traffic is IPv6


IPv6 traffic on the RIPE meeting network

33

0

25

50

75

100

60 62 64 66 68 70 72 74 76 78 80 82 84

% o

f up

link

traf

fic b

eing

IPv6

RIPE meetingExponential Linear


Wireless

34

Peak: 340 associations

24 base stations deployed


High-density access point distribution

35

Questions?Erik Romijn<[email protected]>

mailto:[email protected]?subject=

mailto:[email protected]?subject=

Documents

RIPE 61 Technical Report · Service network Streaming TTM / Rosie Private network Registration Network mgt RIPE meeting venue. Erik Romijn - RIPE 61 Network setup 7. Erik Romijn -