Hello, Thank you for the response, It is really helpful and I really appreciated it. As seen from my post, networking, specifically SDN is not a specialty of mine. Thank you for the directions. From your reply, I understand that openvswitch does not handle routing or layer 3 switching in itself, I need some external tools/settings to handle it. I have several more questions, and I appreciate if you can provide your opinions about these. Please bare with me if they are really dumb questions because the information in the internet is overwhelming for me and I have difficulty to extract answers for these basic questions.
I always thought mininet is a isolated simulation environment for some academic or research work and not for real environments. I hear that routers, switches with different topologies can be created with mininet easily. Is it possible to use it daily for the requirements that I presented previously? Will there be performance penalty against a setting if the same topology is created with other tools you specified, openvswitch, iproute2 etc? I have seen some blogs/post using openwrt as a virtual router or just using a linux box in a virtual machine as a static router. What do you think about this? I may be wrong but if I understand correctly that with openflow it is possible to do the routing or l3 switching without actually needing a router. I will be needing an openflow controller I presume along with openflow enabled switches, and some flows need to be programmed. Openvswicth does openflow but misses controller part to the best of my understanding. Are these statements correct? If so which tools should I use to do layer 3 switching with openflow. You have not commented anything about open virtual networking (ovn). What do you think about it. It is not in proposed your set of solutions. I ask it even though it will be hard to use for me it since I have not encountered a package for arch linux. Which direction would you chose if you were me. mininet, openflow/openvswitch, openswitch/openwrt/linuxboxrouter etc. Thanks in advance.... On Sun, Feb 19, 2023 at 4:30 PM Raymond Burkholder via discuss < ovs-discuss@openvswitch.org> wrote: > > > On 2/18/23 09:22, Bilinmek Istemiyor via discuss wrote: > > Hello, > > I am looking for a solution to create several virtual switches connected > by a virtual router on a single linux pc. I would like to create a test, > development or similar environments which has its own ip address space > and use a single linux pc along with already available kvm/qemu/libvirt > capability for the virtual machines or containers. > > > look at lxc/lxd - a linux kernel native namespace/process management > solution > > I have understood that openvswitch can create virtual switches as the name > suggests, but I have not been able to find any instructions related to > creating a virtual router. I have seen some posts routing the these > switches' traffic with kernels network configuration, but I am more looking > for virtual switches/routers and their virtual interfaces without messing > my host routing settings often and manually. > > > you'll want to dive into the world of iproute2 - it is a series of tools > for managing namespaces, interfaces, addressing, routing, tunnels, .... > > I will connect my custom build kvm/qemu containers or virtual machines to > these enviroments. I have previously used vagrant, docker, proxmox but I do > not want to use those tools since they have their specific attachments. > > as mentioned earlier, iproute2 namespaces are dead simple, or use lxc/lxd > for something a bit more segregated > > My internet searches pointed me, open virtual networking (ovn) which > claims to do virtual switches, routers etc and seems to be using > openvswitch underneath. However ovn seems like it requires higher level of > tooling or services such as openstack provides etc. I have not seen a > proper package for that in arch linux as well which I am currently using. > > To make long story short: > > - > > Can I create several private network switches for such as *MailScanner > warning: numerical links are often malicious:* 192.168.100.0/24 > <http://192.168.100.0/24>, *MailScanner warning: numerical links are > often malicious:* 192.168.101.0/24 <http://192.168.101.0/24>, *MailScanner > warning: numerical links are often malicious:* 192.168.102.0/24 > <http://192.168.102.0/24> for host, test, development etc. and connect > them to a virtual router and make these machines accessible from my lan via > *openvswitch* in a reqular linux box. > - > > If not, which toolset I can use to achive that. I am only interested > in the networking stack, and I would like to be free of any other stack or > technology such as openstack, proxmox, vagrant or docker which came as > bundled with their services, image types etc. > > > Your overall tooling would be comprised of (in increasing order of > complexity and abstraction): > > > - iproute2 (ip ns, ip link, ip addr, ip route, ....) - native kernel > network management > - the trick is to use veth interfaces to link namespaced > environments via the ip ns command > - ifupdown or ifupdown2 - persisting network configurations across > sessions > - open vswitch and/or bridge - kernel switching solutions > - mininet - a python tool for quickly building virtual networks on > your pc (a high level tool using iproute2 functionality (ip ns, veth, etc)) > - frr - free range routing - actual routing protocols for advanced > routing development > > Hope this helps on your networking journey > > Raymond Burkholder > https://blog.raymond.burkholder.net/index.php?/categories/67-Networks > > > > > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
