inn2: IPv6 quirks

[Klaus Alexander Seistrup]

Package: inn2
Version: 2.4.2-1
Severity: normal


Lets say we have an IPv6-enabled news server, news6.example.com, and an IPv4-
only news server, news4.example.com, and let's assume that news6 has both A
and AAAA DNS records for its hostname (news4 is IPv4-only, and has only an A
record).

Now if news6 and news4 tries to do peering, then the news flow will only
succeed in one direction, namely from news6 to news4.  Why?  Because when
news4's inn2 sees an AAAA record for news6, then it will never try the IPv4
address, even if it gets "network unreachable" or "no route to host" by
trying the IPv6 address (news4 has no IPv6 interface, remember?).

IMHO, inn2 should fall back to using IPv4 if IPv6 fails (for whatever reason).

Cheers,

  // Klaus

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.10-4-k7
Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1)

Versions of packages inn2 depends on:
ii  cron                3.0pl1-86ubuntu1     management of regular background p
ii  debconf [debconf-2. 1.4.42ubuntu4        Debian configuration management sy
ii  inn2-inews          2.4.2-1              NNTP client news injector, from In
ii  libc6               2.3.2.ds1-20ubuntu13 GNU C Library: Shared libraries an
ii  libdb4.2            4.2.52-17ubuntu1     Berkeley v4.2 Database Libraries [
ii  libperl5.8          5.8.4-6ubuntu1       Shared Perl library
ii  perl                5.8.4-6ubuntu1       Larry Wall's Practical Extraction 
ii  perl-base [perlapi- 5.8.4-6ubuntu1       The Pathologically Eclectic Rubbis
ii  postfix [mail-trans 2.1.5-9ubuntu3       A high-performance mail transport 
ii  procps              1:3.2.4-1ubuntu1     The /proc file system utilities
ii  time                1.7-19               The GNU time program for measuring

-- debconf information:
  inn2/postinst-cannot-start:
  inn2/preinst-upgrade-largefiles: false
  inn2/preinst-upgrade1: false