11-06, 14:00–15:30 (Europe/Vienna), Ballroom A+B+C
A troubleshooters tale
I routinely help large global enterprises to find problems in their network when our Online conferencing products do not work as expected. The problems range from very low level like broken packet fragmentation to high level like wrong Geolocation detection.
This brings me in contact with network security in various ways, and I learn about their ideas of securing networks and also how to configure such security systems and have to come up with ideas to make the conferencing software work.
As there is obviously no way around making our networks more secure, the question remains, how do we keep them working at the same time. I will show my approach to these problems.
High level network requirements of online communication (WebRTC and the other big ones)
Security requirements in modern corporate networks
The everlasting conflict: tighter security vs. faster and more diverse communication connections
Some typical problems with field examples and how to identify them in Wireshark
- Analysing UDP performance
- DNS - a story of misunderstandings
- VPN - what could possibly go wrong?
History excurse : Why is it so complicated
- The wild-west times of networked software
- Things not to do in your software and why not
- Things not to do in your network and why not
The perfect network - how would it look like?
Starting with a small Web conferencing startup in Germany in 1999 and still with the same people after a long chain of acquisitions and mergers.
These days I help transitioning the venerable GoToMeeting to the modern WebRTC based GoTo.
My day job is helping our developers as well as our customers to analyse and understand intricate network problems in the context of various communication protocols and complex corporate networks. As such I'm proficient in network analysis tools like Wireshark as well as in log analysis tools like Splunk. In my spare time, I read, do the odd triathlon together with my colleagues and fancy ice bathing.