If you get the "netlink_lookup: write failed: Connection
refused" message, please read the following lines.

Please refer to http://bugs.debian.org/305926 and
                http://bugs.debian.org/339317

Costas Tavernarakis <taver@cs.ntua.gr>

  pident always fails on 2.6.11.7 with "netlink_lookup:
  write failed: Connection refused". Have not tried many
  kernel versions, it works on debian kernels and 2.6.8.1.

And Daniel Kraft <da_kraft@web.de>

  I had the same problem with pidentd and found that it
  apparently tries to use a NETLINK-socket with "protocol"
  NETLINK_TCPDIAG, probably to inquire about the "owners"
  of tcp connections. For this to work, the kernel needs
  to have CONFIG_IP_TCPDIAG, called "IP: TCP socket
  monitoring interface" in the networking options section
  of the kernel configuration. I had configured that as a
  module, not knowing what it was needed for; obviously it
  does not load automatically on demand, but after loading
  it manually, the error with pidentd is gone.

Olivier Berger <olivier.berger@int-evry.fr>

  Refering to bug 305926 and the additions in README.Debian,
  I think it would be interesting to explicitly mention the
  module name (tcp_diag) in the README.

Roland Stigge <stigge@antcom.de>

  The kernel option is called CONFIG_INET_TCP_DIAG, or
  CONFIG_INET_DIAG, in 2.6.15. The module is called tcp_diag,
  as Oliver mentioned. But it's not loaded by default, at
  least not with the current Debian default setting and stock
  kernel.

vj <vinjacob@gmail.com>

  netlink_lookup: write failed: Connection refused still
  occurs, the module tcp_diag needs to be loaded. It is a
  module in the default 2.6.16 .config, CONFIG_INET_DIAG.
  Loading it solves the error.
