similar to: KVM-Docker-Networking using TAP and MACVLAN

On Tue, Mar 12, 2019 at 11:10:40PM +0100, Lars Lindstrom wrote: >Hi everyone! > >I have the following requirement: I need to connect a set of Docker >containers to a KVM. The containers shall be isolated in a way that they >cannot communicate to each other without going through the KVM, which >will act as router/firewall. For this, I thought about the following >simple setup

On 3/14/19 4:06 PM, Martin Kletzander wrote: > I cannot try this right now, but I would try something like this: > > ip link add dev veth-vm type veth peer name veth-cont > > and then put veth-vm in the VM (type='direct' would work, but I can > imagine > type='ethernet' might be even faster) and start the containers with > macvtap > using veth-cont. I

On 3/13/19 2:26 PM, Martin Kletzander wrote: > IIUC, you are using the tap0 device, but it is not plugged anywhere. > By that I > mean there is one end that you created and passed through into the VM, > but there > is no other end of that.  I can think of some complicated ways how to > do what > you are trying to, but hopefully the above explanation will move you > forward

On Wed, Mar 13, 2019 at 11:40:51PM +0100, Lars Lindstrom wrote: > >On 3/13/19 2:26 PM, Martin Kletzander wrote: >> IIUC, you are using the tap0 device, but it is not plugged anywhere. >> By that I >> mean there is one end that you created and passed through into the VM, >> but there >> is no other end of that.  I can think of some complicated ways how to

Hi all. I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 My container has bridged network: # virsh dumpxml test1 <domain type='lxc'> <name>test1</name> <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0b1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory>

Hello list, Please don''t shoot me. I know I''m doing something with bonding that bonding wasn''t made for. I just want to give it a try. I want a simple mechanism to have a failover on a 24Mbit line to a 2Mbit line in case the 24Mbit line goes down. Between A and B there are two lines: a 24Mbit and a 2Mbit. I use two OpenVPN tunnels with tap devices: +-- tap0 (A)---

Hello, I successfully set up a tunnel with tinc using the tun interface. however I need a tap device, because I need to run the OLSR routing protocol on the tunnel and if I use the tun mode OLSR will just skip the interface. (It is a well known thing, I had this issue before also when using OpenVPN in the past). The problem is that I cannot make tinc use a tap device. I created the tap0

Hello! I've a problem with tinc-up on Debian Woody (tinc 1.0pre7): router:/etc/tinc/vpn# /etc/init.d/tinc start Starting tinc daemons: vpn. router:/etc/tinc/vpn# tail /var/log/syslog Aug 23 03:25:26 router tinc.vpn[503]: /dev/tap0 is a Linux ethertap device Aug 23 03:25:26 router modprobe: modprobe: Can't locate module tap0 Aug 23 03:25:27 router last message repeated 4 times Aug 23

I read tinc documentation part: " For Branch A BranchA would be configured like this: In /etc/tinc/company/tinc-up: # Real interface of internal network: # ifconfig eth0 10.1.54.1 netmask 255.255.0.0 ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0 ... Note that the IP addresses of eth0 and tap0 are the same. This is quite possible, if you make sure that the netmasks of the

I have a Debian 8 64-bit machine set up as a server and apt-got the tinc package. I configured tinc as a bridge and everything seems normal except that the tunnel does not forward multicast traffic. I used tcpdump to examine the br0, eth0 and tap interfaces. I could see multicast packets on both br0 and eth0, but there is no such packet present on the tap interface. I don't quite know why

inquiry about differences between the tap and the vnet in the virt-manager Greetings! I encounter a problem about the network when using virt-manager to create and run a VM. when I want to establish a network bridge for the guest OS, I generally use two kinds of ways described as fellow : First method : create a bridge with the help of linux commad: brctl, or Second method : using

Hello, I am trying to run a virtual machine with qemu-kvm and libvirt as a user. In order to start the virtual machine I setup a tap device manually, add it to the bridge and activate it via ifconfig. But I cannot tell libvirt to not try to add the definded tap device to the bridge by itself. It always fails telling me it cannot add tap0 to br0. Thats the xml snippet for defining the network:

Hello, On KubeVirt, we are trying to pre-create a tap device, then instruct libvirt to consume it (via the type=ethernet , managed='no' attributes). It works as expected, **unless** when we create a multi-queue tap device. The difference when creating the tap device is that we set the multi-queue flag; libvirt throws the following error when consuming it: ``` LibvirtError(Code=38,

Hi all. I have an OpenVPN server: 2.2.1-1 x86_64 Server config: port 11223 dev tap proto udp tls-server ca keys/ca.crt cert keys/server.crt key keys/server.key dh keys/dh1024.pem server 1.2.3.3 255.255.255.0 push "route 192.168.0.0 255.255.255.0 1.2.3.4" keepalive 10 60 client-to-client duplicate-cn inactive 600 log /var/log/openvpn.log syslog status /var/log/openvpn-status.log user

On Wed, Sep 23, 2020 at 05:44:28PM +0100, Daniel P. Berrangé wrote: > On Tue, Sep 22, 2020 at 01:48:08PM +0200, Miguel Duarte de Mora Barroso wrote: > > Hello, > > > > On KubeVirt, we are trying to pre-create a tap device, then instruct > > libvirt to consume it (via the type=ethernet , managed='no' > > attributes). > > > > It works as

> And all was fine, before I accidentally upgraded Centos to 7.1.1503 > After upgrade LXC can't start with diagnostic: > [root@node14 ~]# virsh start test1 > error: Failed to start domain test1 > error: internal error: guest failed to start: internal error: Child > process (ip link set macvlan0 netns 25263) unexpected exit status 2: > RTNETLINK answers: Invalid argument

> On Tue, Jun 30, 2020 at 04:02:05PM +0100, Daniel P. Berrangé wrote: > > On Tue, Jun 30, 2020 at 12:59:03PM +0200, Miguel Duarte de Mora Barroso wrote: > > > On Mon, Apr 6, 2020 at 4:03 PM Laine Stump <lstump redhat com> wrote: > > > > > > > > On 4/6/20 9:54 AM, Daniel P. Berrangé wrote: > > > > > On Mon, Apr 06, 2020 at 03:47:01PM

Sorry if this off-topic but I have a qemu related question I was going to send to the qemu users mailing list but that list appears to have vanished. I thought this community might have some insight. I am interested in controlling VM access to different tap devices so I want to have different qemu processes bound to different tun devices. I've created new tun devices (eg. /dev/net/tun_low)

Hello there, I was hoping that maybe one of you guys could help me out with a problem I'm experiencing with tinc1.0pre7. First, I'll start with my configuration, after that I'll explain my problem. Background ---------- This is a simple, client-server situation on a private network. Both machines run the same Debian Woody 3.0 testing installation and both have identical packages

Hi, Host A has two interfaces: eth0, tap0. I want that all locally generated traffic from user 1004 goes through tap0. This is what I did: iptables -A OUTPUT -t mangle -m owner --uid-owner 1004 -j MARK --set-mark 2 echo 202 bigmac.out >> /etc/iproute2/rt_tables ip rule add fwmark 2 table bigmac.out ip route add default via 10.0.0.1 dev tap0 table bigmac.out ip route flush cache