martin/IPv6-Lab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
theamma
2025-05-01 09:21:01 +02:00
committed by GitHub
parent 4518571091
commit a8e162db2e
1 changed files with 29 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
README.md
View File

@@ -43,9 +43,9 @@ Turn on the bridge
KVM is used as a hypervisor in this project. You may use virsh on the cli or virt-manager as a graphical tool. KVM is used as a hypervisor in this project. You may use virsh on the cli or virt-manager as a graphical tool.
### Create virtual network on hypervisor ### Create virtual networks on hypervisor
Here we create a new network to be used by the edge router torino by creating a new file named bridged-network.xml with the following content Here we create two networks on the hypervisor. The first is used by the edge router impala to connect to the host network, the second is needed by the hosts in the lab network. Create a file named bridged-network.xml with the following content
<network> <network>
<name>bridged-network</name> <name>bridged-network</name>
@@ -53,18 +53,40 @@ Here we create a new network to be used by the edge router torino by creating a
<bridge name="br0" /> <bridge name="br0" />
</network> </network>
To create the network on the hypervisor, run Then we need the network for the virtual switch served by openvswitch. Create a file named ovs-network.xml with this content
<network>
<name>vSwitch0</name>
<forward mode="bridge"/>
<bridge name="labbr1"/>
<virtualport type='openvswitch'/>
</network>
In case you use virsh, you need to run the following commands to create the network on the hypervisor:
$ virsh net-define bridged-network.xml $ virsh net-define bridged-network.xml
$ virsh net-define ovs-network.xml
Then start it Then start it
$ virsh net-start bridged-network $ virsh net-start bridged-network
$ virsh net-autostart bridged-network $ virsh net-start vSwitch0
$ virsh net-autostart bridged-network
$ virsh net-autostart vSwitch0
$ virsh net-list $ virsh net-list
Name Status Automatischer Start Bleibend Name Status Automatischer Start Bleibend
------------------------------------------------------------ ------------------------------------------------------------
bridged-network Aktiv ja ja## bridged-network Aktiv ja ja
vSwitch0 Aktiv ja ja
On the hosts torino, we need just one interface connected to vSwitch0.
<interface type="bridge">
<source network="vSwitch0" portid="672dad49-ab32-4369-81d3-4a1e7e69b0de" bridge="labbr1"/>
<virtualport type="openvswitch"/>
<model type="virtio"/>
</interface>
## Torino ## Torino
Torino is the WAN router of the lab. On the external interface torino acts as a DHCPv6 client in order to receive a Prefix Delegation from the DSL-Router (Fritz!Box in this case). On the internal interface torino will serve Router Advertisements which is necessary for SLAAC. The hosts in the lab environment connectetd to the vSwitch will receive a prefix via SLAAC this way. Torino is the WAN router of the lab. On the external interface torino acts as a DHCPv6 client in order to receive a Prefix Delegation from the DSL-Router (Fritz!Box in this case). On the internal interface torino will serve Router Advertisements which is necessary for SLAAC. The hosts in the lab environment connectetd to the vSwitch will receive a prefix via SLAAC this way.