Definitely still a bug
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1223730
Title:
mDNS failure with openvswitch 1.10
To manage notifications about this bug go to:
[Expired for openvswitch (Ubuntu) because there has been no activity for
60 days.]
** Changed in: openvswitch (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
I've now updated to Saucy and I still have the same problem on multiple
machines with openswitch.
I have a KVM test machine that has a ubuntu VM running on it plugged
into a vswitch that is in turn plugged in via the quad port bond you can
see here.
Iron is the KVM host, the host shows no mDNS
Ah sorry, I had updated to the latest OVS version from saucy by enabling
the saucy repos and just updating relevant libvirt and OVS packages.
The show command I included was run on 1.9 after I downgraded again to
get printing working (printers found via mDNS)
I've looked at the packets on the
Hi NightShade
I'm a little confused as to which versions of openvswitch you are
running on which version of Ubuntu; the release version of OpenvSwitch
for raring was 1.9.0.
Please can you confirm. It would also be helpful to see if you have the
same issues with 3.11/1.10.2 on saucy.
** Changed
openvswitch setup
root@tim-6460b:~# ovs-vsctl show
ccdda6ff-e90d-41f5-9f87-5e68f562b73c
Bridge private
Port private
Interface private
type: internal
Bridge internal
Port internal
Interface internal
type: internal
