Re: [Xen-users] Internal network Configuration

[Jason Long <hack3rcon@xxxxxxxxx>]

Physical port? Is you mean Virtual Adapter? 

# ifconfig

br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::211:3bff:fe15:48be  prefixlen 64  scopeid 0x20<link>

        ether 00:11:3b:15:48:be  txqueuelen 0  (Ethernet)

        RX packets 2029  bytes 392913 (383.7 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 14  bytes 2700 (2.6 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp4s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        ether 00:11:3b:15:48:be  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 0  (Local Loopback)

        RX packets 10  bytes 1004 (1004.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 10  bytes 1004 (1004.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif2.0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif2.1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif2.0-emu: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::fcff:ffff:feff:ffff  prefixlen 64  scopeid 0x20<link>

        ether fe:ff:ff:ff:ff:ff  txqueuelen 500  (Ethernet)

        RX packets 6628  bytes 744203 (726.7 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 110104  bytes 9402053 (8.9 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif2.1-emu: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::fcff:ffff:feff:ffff  prefixlen 64  scopeid 0x20<link>

        ether fe:ff:ff:ff:ff:ff  txqueuelen 500  (Ethernet)

        RX packets 2029  bytes 421319 (411.4 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 22  bytes 3348 (3.2 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255

        ether 52:54:00:8b:c5:55  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I guess "virbr0" is a good option. Can I use "virbr0" for more than one VM?

On Saturday, July 9, 2016 5:39 PM, Simon Hobson <linux@xxxxxxxxxxxxxxxx> wrote:

Jason Long <hack3rcon@xxxxxxxxx> wrote:

> How can I create an internal network in Xen that just my VMs can see it and other part of network can't see it.

Create a new bridge, but don't connect any physical ports to it.
In Debian type systems you specify (IIRC) "bridge_ports none" in the network setup.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users