Linux Bridging (part 1)

Подписаться 619

Просмотров 13 тыс.

50% 1

A simple lab where I will demonstrate linux bridging. I am using 2 veth interfaces and two network namespaces to simulate distinct broadcast domains.
If you follow this video you will learn how to configure a basic bridge in linux using only iproute2 package.

Наука

Опубликовано:

29 ноя 2021

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 9

@vojtechstoklasa3417 29 дней назад

this looks like my budget-friendly homelab will finally work properly network-wise! Thanks, great work!

@rouabahoussama Год назад

Very good video, thank you for sharing!

@robertphillips124714 Год назад

I am SO upset that you put your 1s and 2s the opposite way around for the namespaces on the diagram!!! 😂 great explanation though, thanks very much!

@volkan1005 Год назад

finally i got sth worth for like/subscribe. thanks a lot :)

@vrbadarla1 3 месяца назад

very nice.. excellent

@RebeliousSapien Год назад

what is veth? ... is this different from when i use virsh attach-interface ... ? i'm having a really hard time understanding what this KVM, QEMU stuff are ? .. is this veth you created the same thing created in a VM by virsh when setting a bridge interface? are the namespaces the same as a LAN? is that what they're for .. creating a LAN and adding domains to it ?

@VigilanceTech 2 года назад

Hi, thanks for the video. I have a question. I'm trying to bring up a container in proxmox and I'm having a hard time getting it to see the internet. I think it's supposed to be bridged. What would the advantage be to using different name spaces for the interfaces as you've done, rather than just giving them different names for instance, and do you think it's something I should look into? It's been years since I bridged, long before these namespaces, and I don't recall seeming to be needing any such thing.

@routerologyblog1111 2 года назад

Hi, Containers are running in their own network namespaces. The whole ideea is to have a way to bridge or connect somehow the interface of the container from a private namespace to your real network. If you are using proxmox you don't need to do any of these things, you just need to take care of the networking config in proxmox (linux bridge or ovs) and that's it. I did this videos as an in depth explanation to understand what's really happening with regards to containers networking.