Package: psi
Version: 0.13-1
Severity: important

We seem to be unable to use Psi in our local network. The DNS domain
is used also by Windows domain controllers and somehow Psi seems to
think that it can use a zeroconf-style DNS request to find the server.
This is what I found while sniffing the network interface:

  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query SRV 
_xmpp-client._tcp.jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question
  10.66.1.71 -> 224.0.0.251  MDNS Standard query A jabber.intranet.local, "QM" 
question
fe80::222:15ff:fe85:ccdc -> ff02::fb     MDNS Standard query A 
jabber.intranet.local, "QM" question

Apparently Psi tries to resolve the server "jabber.intranet.local"
through a multicast DNS request but there is no such server in our
local network answering such requests.

Other Jabber clients sometimes also try multicast DNS requests but
quickly fallback to regular (UDP 53) DNS requests. Psi doesn't.

I don't have any avahi or zeroconf services running on my system
and the /etc/nsswitch.conf reads:

    hosts:          files dns
    networks:       files

I have removed all traces of "mdns4" here because that has caused
incorrect caching of DNS entries in the past.

Psi is currently unusable in our local domain. Still it can connect
to other Jabber servers.
-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages psi depends on:
ii  libaspell15            0.60.6-2          GNU Aspell spell-checker runtime l
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libgcc1                1:4.4.2-3         GCC support library
ii  libqca2                2.0.2-1           libraries for the Qt Cryptographic
ii  libqca2-plugin-ossl    0.1~20070904-4    QCA OSSL plugin for libqca2
ii  libqt4-dbus            4:4.5.3-4         Qt 4 D-Bus module
ii  libqt4-network         4:4.5.3-4         Qt 4 network module
ii  libqt4-qt3support      4:4.5.3-4         Qt 3 compatibility library for Qt 
ii  libqt4-xml             4:4.5.3-4         Qt 4 XML module
ii  libqtcore4             4:4.5.3-4         Qt 4 core module
ii  libqtgui4              4:4.5.3-4         Qt 4 GUI module
ii  libstdc++6             4.4.2-3           The GNU Standard C++ Library v3
ii  libx11-6               2:1.2.2-1         X11 client-side library
ii  libxss1                1:1.1.3-1         X11 Screen Saver extension library
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages psi recommends:
ii  sox                           14.3.0-1.1 Swiss army knife of sound processi

Versions of packages psi suggests:
ii  libqca2-plugin-gnupg       2.0.0~beta3-1 QCA gnupg plugin for libqca2
ii  psi-translations           1.9           Translations for psi
ii  xdg-utils                  1.0.2-6.1     desktop integration utilities from

-- no debconf information



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

Reply via email to