I know I have my part in starting it, but this is the wrong thread for this discussion. Let's agree that we disagree and get back to Open vSwitch specifics.
Thanks
Can some one explain to me what openvswitch is supposed to do? I feel like I know what it does, but I am missing something big.
I know its supposed to allow you to create vlans, QoS, and network usage monitoring for each VM, but why do we need openvswitch for it? is there supposed to be a network performance benefit since it is more designed for multiple servers?
Good question that I also would like to hear a good answer to.
For me it began with a need for port mirroring to a sniffer interface. Turning vmbr0 into a hub by setting bridge_fd to 0 and bridge_ageing to 0 sort works but who wants a dumb hub when you can have a switch? Another option I tried was using iptables TEE but I couldn't make it play nice with my shorewall generated router/firewall rules.
Right now I have Open vSwitch installed with port mirroring to my sniffer interface, so mission accomplished. Checking out the rest of the features will have to wait until I'm done setting up my virtual environment.
Im struggling with openvswitch under Proxmox. I compiled and buildt it, though could not get any data to flow through the device, may been a faulty build.
Wondering if anyone has put this into production?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
