Package: avahi-daemon
Version: 0.6.30-5
Severity: normal

I have a Samsung Q45 laptop with the following wireless interface:

02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
        Subsystem: Intel Corporation PRO/Wireless 3945BG Network Connection
        Kernel driver in use: iwl3945

and a desktop with the following ethernet interface:

00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit 
Ethernet Controller (rev 13)
        Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet 
Controller (Asus)
        Kernel driver in use: skge

Both are amd64 systems running Linux 3.1.

Neither system can resolve the name of the other (tested with
avahi-resolve-host-name -4).

If I run tshark on the laptop, I can see the MDNS queries being
received, and the responses being transmitted; the desktop just ignores
the responses.

If I run tshark on the desktop, both machines start being able to
find each other, so it appears that putting the skge-using interface
into promiscuous mode prevents further diagnosis of the problem on the
desktop end.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages avahi-daemon depends on:
ii  adduser            3.113
ii  bind9-host [host]  1:9.7.3.dfsg-1+b1
ii  dbus               1.4.16-1
ii  libavahi-common3   0.6.30-5
ii  libavahi-core7     0.6.30-5
ii  libc6              2.13-23
ii  libcap2            1:2.22-1
ii  libdaemon0         0.14-2
ii  libdbus-1-3        1.4.16-1
ii  libexpat1          2.0.1-7.2
ii  lsb-base           3.2-28

Versions of packages avahi-daemon recommends:
pn  libnss-mdns  <none>

Versions of packages avahi-daemon suggests:
pn  avahi-autoipd  <none>

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to