{"id":515,"date":"2017-06-05T22:22:07","date_gmt":"2017-06-05T21:22:07","guid":{"rendered":"http:\/\/darkandscary.co.uk\/?p=515"},"modified":"2017-06-05T22:22:07","modified_gmt":"2017-06-05T21:22:07","slug":"creating-virtual-networks-in-kvm","status":"publish","type":"post","link":"https:\/\/darkandscary.co.uk\/?p=515","title":{"rendered":"Creating virtual networks in KVM"},"content":{"rendered":"

In earlier posts I installed the KVM hypervisor on an openSUSE Leap system and added a bridged network connection. That will allow virtual machines to use IP addresses on my house network. However, what if I want to use ‘private’ networks for the experiments I wish to run? That is easily done so let’s see\u00a0how to\u00a0create networks and address ranges as follows:<\/p>\n

'management'<\/div>
192.168.99.0\/24<\/div>\r\n
'site1'<\/div>
192.168.100.0\/24<\/div>\r\n
'site2vlan1'<\/div>
192.168.101.0\/24<\/div>\r\n
'site2vlan2'<\/div>
192.168.102.0\/24<\/div><\/pre>\n
Bring up the ‘details’ pane for the hypervisor and select the ‘Virtual Networks’ tab as follows:<\/p>\n
\"\"<\/a>
The list of virtual networks, currently empty<\/figcaption><\/figure>\n
Clicking on the small blue cross opens the dialog for adding a new network. Let’s define the ‘management’ LAN as follows:<\/p>\n
\"\"<\/a>
Setting the name of the management LAN<\/figcaption><\/figure>\n
Next, define the IP address and subnet mask (192.168.99.0\/24) and untick the ‘Enable DHCPv4’ option. DHCP will be provided by the virtual Mikrotek router.<\/p>\n
\"\"<\/a>
Setting the IP address range and disabling DHCP<\/figcaption><\/figure>\n
On the next pane, disable IPv6 for the time being.<\/p>\n
\"\"<\/a>
Disable IPv6 for this network<\/figcaption><\/figure>\n
Finally, select the option to create an isolated network and keep the DNS Domain Name as shown.<\/p>\n
\"\"<\/a>
Creating an isolated network called ‘management’<\/figcaption><\/figure>\n
Repeating the process for the other networks produces a network list as follows:<\/p>\n
\"\"<\/a>
The completed list of virtual networks<\/figcaption><\/figure>\n
As a final check to see that everything is working as expected, bring up a console as the root user and type the following commands:<\/p>\n
virsh net-list<\/code><\/p>\n
virsh net-list\r\n Name                 State      Autostart     Persistent\r\n----------------------------------------------------------\r\n management           active     yes           yes\r\n site1                active     yes           yes\r\n site2vlan1           active     yes           yes\r\n site2vlan2           active     yes           yes\r\n<\/pre>\n
ip addr<\/code><\/p>\n
ip addr\r\n1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1\r\n    link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\r\n    inet 127.0.0.1\/8 scope host lo\r\n       valid_lft forever preferred_lft forever\r\n    inet6 ::1\/128 scope host \r\n       valid_lft forever preferred_lft forever\r\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000\r\n    link\/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff\r\n3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000\r\n    link\/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.1.101\/24 brd 192.168.1.255 scope global br0\r\n       valid_lft forever preferred_lft forever\r\n    inet6 fd00::1:8ca0:7c31:ae16:2e0e\/64 scope global temporary dynamic \r\n       valid_lft 6233sec preferred_lft 6233sec\r\n    inet6 fd00::1:12bf:48ff:fe88:f355\/64 scope global mngtmpaddr dynamic \r\n       valid_lft 6233sec preferred_lft 6233sec\r\n    inet6 fe80::12bf:48ff:fe88:f355\/64 scope link \r\n       valid_lft forever preferred_lft forever\r\n4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:c4:63:38 brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.99.1\/24 brd 192.168.99.255 scope global virbr0\r\n       valid_lft forever preferred_lft forever\r\n5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:c4:63:38 brd ff:ff:ff:ff:ff:ff\r\n6: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:53:8a:0c brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.100.1\/24 brd 192.168.100.255 scope global virbr1\r\n       valid_lft forever preferred_lft forever\r\n7: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:53:8a:0c brd ff:ff:ff:ff:ff:ff\r\n8: virbr2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:cf:6f:e2 brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.101.1\/24 brd 192.168.101.255 scope global virbr2\r\n       valid_lft forever preferred_lft forever\r\n9: virbr2-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr2 state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:cf:6f:e2 brd ff:ff:ff:ff:ff:ff\r\n10: virbr3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:26:84:24 brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.102.1\/24 brd 192.168.102.255 scope global virbr3\r\n       valid_lft forever preferred_lft forever\r\n11: virbr3-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr3 state DOWN group default qlen 1000\r\n    link\/ether 52:54:00:26:84:24 brd ff:ff:ff:ff:ff:ff\r\n<\/pre>\n
The results\u00a0show the four virtual networks (virbr0 to virbr3)<\/code>, but they\u00a0also show that four virtual network adapters (virbr0-nic to virbr3-nic)<\/code> have been created that connect each of these new networks to the host machine itself.<\/p>\n
In another post, the virtual Mikrotek router will be installed and a basic configuration applied to allow it to route between the four virtual networks.<\/p>\n","protected":false},"excerpt":{"rendered":"
In earlier posts I installed the KVM hypervisor on an openSUSE Leap system and added a bridged network connection. That will allow virtual machines to use IP addresses on my house network. However, what if I want to use ‘private’ networks for the experiments I wish to run? That is easily done so let’s see\u00a0how … Continue reading Creating virtual networks in KVM<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,21],"tags":[],"class_list":["post-515","post","type-post","status-publish","format-standard","hentry","category-linux","category-virtualisation"],"_links":{"self":[{"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/515","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=515"}],"version-history":[{"count":16,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/515\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/515\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=515"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=515"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/darkandscary.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}