[root@host] $ virsh list
Id Name State
----------------------------------------------------
[root@host] $ virsh list --all
Id Name State
----------------------------------------------------
- centos-test shut off
[root@host] $
[root@host] $ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.b8599f1ef79e no eth2
virbr0 8000.5254004de69f yes virbr0-nic
[root@host] $
[root@host] $ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.16.211.1 0.0.0.0 UG 0 0 0 br0
169.254.0.0 0.0.0.0 255.255.0.0 U 1007 0 0 br0
172.16.211.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
Some applications only working in same broadcast, so vpn feature is must have when access personal resource (e.g: NAS) from Internet. The artical only cover Wireguard, but not include theory.
Different platoform have diff version, e.g Virtual TestCenter have ESXi platform or QEMU platform, different platform have diff License, if use incorrect platform or License, will have alarm, e.g:
So I summarized hwo to deploy STC VM by QEMU in the article.
I summaried the hands-on at 2019.7, public on my blog now. So you will find the version is old (652/661), new version(721/731) include more inovation features in SR solution.
Introduction
I summarized SR/SRTE hands-on-deck that includes our highlight features and show information in the same topology, content includes the following topic, now revised version is v3:
