Linux Bridges, IP Tables, and CNI Plug-Ins - A Container Networking Deepdive

[@vikas87922]

I was looking for deep dive into container networking, this is extremely well organised and explained. Thanks Matt and Hank for creating such wonderful content.

[@jigneshpatel5469]

Very nice explanation covering lots of inner networking in depth. Thanks a lot

[@Vladerrama21]

fantastic session guys! great how you built the container networking manually! thx Matt!

[@FunFactScoop]

Crisp and concise ! Couldn't be better . Nice job Matt !

[@nenunene2400]

Wow .. Pure Gold .. better than any paid courses

[@ChrisgammaDE]

Thank you! This is the first good talk I found in 40min

[@aimene_tayebbey]

i like the way of breaking things down, u should really post more videos like these get into the intricacies of how netwoking works, keep up the good work and thanks

[@maciaren]

Extremely clear explanation - great work.

[@jjbb7010]

Ahhh I see so we’re not abstracting and assuming responsibilities not just for networking but also for container and switch/vnic networks... awesome!!! It’s about time!!!

[@rafaelmartineztomas4911]

Quality stuff , thanks very much!!

[@karicallegra8194]

Love the addition of the Cisco hold music lmao

[@mostafaemami8331]

I wonder do I need to have a bridge necessarily, can I connect couple of network namespaces vi mulitple veth interfaces?

[@wtt1296]

Not working for me when I test through telnet, I get "no route to host" if I use host IP but if I use 127.0.0.1, successfully connect

[@pablogoulart9500]

Amazing video!

[@robfielding8566]

Does anybody know how to use the normal docker command to either... setup a reverse tunnel (ie: inside the container, 127.0.0.1:27017 binds to a port in the host so that the container can get --network=none and just be given tunnels to what it needs. or: without using Kubernetes, bind two containers into the same localhost. I need this because I can't use DNS to connect between machines. I want to disable connections to anything but 127.0.0.1 ports created by a sidecar, and have the sidecar transparently do TLS between the sidecars. I would like to not use Kubernetes. I can make a much much simpler system if I can just use straight Docker commands. Right now, the only solution seems to be to Dockerfile re-package containers to have the sidecar running along side the container.

[@code-to-clouds]

I can not find github repo. does any one has it?

[@yashmenpara8311]

Did you watch till the end ? he did post all the links - Webinar Resources @58:31

[@jjbb7010]

NetOps Automation or NetDevOps Analyst/Engineer/Architect/Fox - Generalized for new Networkers including Cloud...

[@Oswee]

`sudo plotnetcfg | dot -Tpdf > topology.pdf` to generate the pdf of the current net topology on the host.

[@cryp0g00n4]

I wonder if he is aware of his watch and did it on purpose.

[@jjbb7010]

Why are we using docker instances? Instead of Cisco virtual devices... ;/ ugh... I understand you want to share the toys but this is a Cisco Cert...