Jared Naude (77)
Weather map of the traffic following through congress. The YoloColo saturated the 100 Gbps link. 300 Gbit of capacity was provided by several partners. #39c3
Time for my favorite talk of #39c3, the infrastructure review. It truly shows the scale and effort evolved to put the congress together, from networking, communication, video recoding / streaming, power co-ordination, angels and much more. It demonstrates the saying "it takes a village" to put a community event together.
🧵
ChaosPost - 7849 post cards were forwarded to Deutsche Post of which 2145 were international and 5704 were national. #39c3
This is the spectrum analysis of various 2.4 Ghz, 5 and 6 Ghz bands. IPv6 was about 35% of the usage. The team is considering making the YoloColo IPv6 only. Juniper SRX cluster was used as a NAT64 gateway. #39c3
Some more interesting stats about the kidspace around noise levels (LOL) and the Herald system. #39c3
Next up is the Phone Operations Center (POC). They deployed:
* ~ 11 300 configured extenstions (8500 last year), increasing by more than 32%
* 6 100 configured DECT phones
* 4 600 concurrent DECT phones
* Max 110 calls in parallel
* More than 400k calls were made (>206k DECT)
Congress is powered by a 10kV ring through 2 transformers. There is an emergency "thomas the tank engine" generator for emergency power. #39c3
The congress used +/- 6Mwh of power (for the monitored usage) and the following used the most power:
1) Halle H (ceiling lights)
2) YoloColo
3) House of Tea
Time for CCC Internetmanufaktur™:
All of these links are 100Gbps. Backbone and distribution was done by Juniper. The optics were provided by Flex Optics. EVPN-VXLAN CRB for building wide L3. #39c3
The team managed to deploy WiFi 6 across the bulding with a peak of 10277 clients. Planning was done in Hamina which made the wifi deployment better. Almost a third of capacity was over 6Ghz. #39c3
