Public bug reported:
I have two machines: a Ubuntu 7.10 machine called "astromech", and a
Debian 4.0 machine called "debian".
debian is a Xen machine with two virtual machines: "openbravo" and
"infraestructura", both running Debian 4.0. This virtual machines are
connected to an ethernet bridge via it's virtual network interfaces. The
real machine's Ethernet port and wireless adapter are also connected to
this bridge. The wireless card works in master mode, because this
machine is a wireless access point for my network. I'm running hostapd
for WPA encryption over the wireless link. On the Ethernet port I have
my WiMAX modem giving my network DHCP with a private address range.
Basically debian has two virtual machines, a WiMAX connection, a
wireless interface and an ethernet port all bound to bridge, and is
working as a secure wireless access point.
astromech is a Ubuntu 7.10 laptop connected through the wireless link.
debian and it's virtual machines all resolve correctly through Multicast
DNS on the local domain. Every virtual machine can resolve every other
virtual machine and debian, they all use DHCP for it's network
configuration.
But, there's a problem when debian or the VMs try to locate astromech.
At startup they are unable to resolve it, but if I run "avahi-resolve -n
astromech.local" from within astromech twice, then the other machines
can resolve astromech.local for awhile. The first time I run "avahi-
resolve -n astromech.local" from astromech it always resolve a link-
local IPv6 address instead of the IPv4 address of the machine.
At startup, astromech can locate the other machines, but after some time
it is unable to do so, and it doesn't matter if I restart avahi-daemon
on astromech and the other machines, it just doesn't work anymore.
Note that there are no problems with the machines that are inside
debian, but only with astromech, which is connected through the wireless
link.
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
--
MDNS not working properly
https://bugs.launchpad.net/bugs/162084
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
