0

I am sending some data from Canoe in Windows to Linux host. I am able to receive to Linux host PC. Now I would like to route the data from Linux host to Qemu but I am not able to route it to qemu.

I have created bridge and connected to eth1 and tap0. I have set defined IP address which is in Qemu to tap0 and tap0 is connected to bridge.

I could see the problem is bridge is up but tap0 is not up. Could you please suggest me how to make it tap0 as up.

How to make it tap0 is up:

6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 66:46:27:c2:b8:ea brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6446:27ff:fec2:b8ea/64 scope link 
       valid_lft forever preferred_lft forever
7: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br0 state DOWN group default qlen 1000
    link/ether 66:46:27:c2:b8:ea brd ff:ff:ff:ff:ff:ff
2
  • I am facing the issue: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br0 state DOWN group default qlen 1000 link/ether 66:46:27:c2:b8:ea brd ff:ff:ff:ff:ff:ff
    – Ganesh
    Sep 6 at 13:50
  • " I have set defined IP address which i s in Qemu to tap0". No, tap0 on a bridge should not have an IP address. The other side of tap0, the VM, should have it. "NO-CARRIER" for a tap device means the VM didn't set its interface up (or QEMU wasn't configured properly to get the VM to detect the interface). It's probably a problem on the VM, but if the VM isn't runing Unix/Linux, then addressing this would be off-topic.
    – A.B
    Sep 7 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.