bug in IPv6 patch with linux 2.4.x? [WAS Re: Consolidation of CRC newsfeeds for IPv6]

[William F. Maton]

Pardon the break in doldrums, but I thought I'd address this to the list
in case the authors of the "North" IPv6 patch were lurking.

On Wed, 6 Feb 2002, Bernhard Schmidt wrote:

> On Wed, Feb 06, 2002 at 01:37:59PM -0500, William F. Maton wrote:
>
> > Feb  6 13:01:56 crc-news innd: SERVER cant listen RCreader Address already
> > in use
>
> If you have lsof on your box you could try to execute 'lsof -i' for an
> overview about used ports. Usually it is just an forgotten inetd-entry
> or something else.

Definately not inetd.  BUT, I decided to do a test:

-news.crc.ca is running 2.4.17  (glibc 2.2.5)
-mcast.dgim.crc.ca was running 2.2.20 (glibc 2.2.4)

mcast has the "North" IPv6 patch for inn 2.3.2 applied.  In order to
reduce my overhead in running two separate news servers, I wanted to have
news.crc.ca handle both IPv4 and IPv6 newsfeeds.  So I applied the "North"
patch as well to crc-news.crc.ca INN 2.3.2 code, and recompiled and
installed.

In migrating, I found the message quoted above in news.crit.
Hmmmm...setting listenonipv6 to "no", allowed me to start INN.

So I decided to test a hunch.  I decided to compile and install linux
kernel 2.4.17 on mcast as well, and reboot.  Now on mcast, I get:

Feb  6 14:25:38 mcast innd: SERVER cant listen RCreader Address already in use

OK, so I re-installed 2.2.20 on mcast, rebooted, and voila, INN is running
again.

There's something in that patch that the Linux 2.4.x series kernel just
doesn't grok that well.

Ideas, anyone?

> > On Wed, 6 Feb 2002, William F. Maton wrote:
>
> Funny enough I did not receive this message. Anyone else did?

My fault.  I think I missed a letter in a copy and paste while composing
the first message.

>
> --
>    bye bye
>      Bernhard
>



wfms