[Netkit.users] TAP problems in lab creation

[Massimo Rimondini]

Dear Silvia,

this can be traced back to a bug in the currently published Netkit release, which pops up every time you start a virtual machine with at least two network interfaces and at least one tap.
The problem has already been reported on the mailing list, and an entry is also present in our bug tracking system: http://bugs.netkit.org/show_bug.cgi?id=2.

In order to fix it, you need to apply the patch available at http://list.dia.uniroma3.it/pipermail/netkit.users/attachments/20080202/f21faaa6/tap-not-first.obj.

Sorry for the inconvenience.

Regards,
Massimo.



From: netkit.users-bounces a list.dia.uniroma3.it [mailto:netkit.users-bounces a list.dia.uniroma3.it] On Behalf Of silvia filippi
Sent: Wednesday, August 26, 2009 12:45 PM
To: netkit.users a list.dia.uniroma3.it
Subject: [Netkit.users] TAP problems in lab creation

Hello to everybody.
I'm in trouble trying to setup a tap interface inside  a  netkit-lab. 
I can successfully start a single virtual machine giving this instruction:
vstart pc1 --eth0=tap,10.0.0.1,10.0.0.2
and tap interfaces (host and vm) are created and I can ping an internet address.

If I try to start an easy lab with only two virtual machine (where pc1 should be connected to internet and to pc2, and pc2 only to pc1), with this instructions inside lab.conf:
pc1[1]="A"
pc1[0]=tap,10.0.0.1,10.0.0.2
pc2[0]="A"

I receive this msg at pc1 vm starting: "daemon_open : control connect failed, errno=2" and no tap interface is created.

Could someone help me in resolving this problem?

Thank you,
Silvia Filippi