From: Dinesh Mistry (dmistry_at_yourhostdirect.com)
Date: Sun 13 Apr 2003 - 18:22:00 BST
I have mentioned having this problem with BIND 8 too, it appears that even
when using the listenon directive bind still only binds to the first IP of
the vserver.. I also thought I had seem this working before not sure where
it broken though.
--------------------------------------------
Dinesh Mistry
YourHostDirect
1-800-210-6757
Better, Faster and more Reliable Hosting
http://www.yourhostdirect.com
--------------------------------------------
-----Original Message-----
From: Gerrit Hotzel [mailto:gt_at_hzhome.mine.nu]
Sent: Sunday, April 13, 2003 9:19 AM
To: vserver_at_solucorp.qc.ca
Subject: Re: [vserver] Re: status on vserver services binding to 0.0.0.0
On Sun, Apr 13, 2003 at 01:19:24PM +0200, klavs klavsen wrote:
> On Sun, 2003-04-13 at 13:13, klavs klavsen wrote:
> > Hi guys,
> >
> > As far as I can tell, a service which is set up pr. default to listen to
> > 0.0.0.0 - does not get rewritten to listen to IPROOT. I tried this with
> > v0.22 of the utils and ctx17.
> >
> > Shouldn't this be automatically rewritten by the kernel? I believe it
> > once was (but I can remember wrong ofcourse :)
> >
>
> The weird thing is that this rewrite of 0.0.0.0 seems to work fine for
> proftpd - but not for postfix or sshd. Any ideas why?
>
May this be related to what Jesper FA pointed out about programs running
create socket, listen instead of the usual create socket, bind, listen?
The posts were around the end of the last year.
Jesper FA wrote a patch to ctx16 attached to its mail. It adds an
additional check to the listen-syscall to limit IPs.
It worked fine for me, though I never understood why this patch never
made it into the offical ctx.
-- Gerrit