And also there is a bind bug..
If a program bind an ip address with an specific
port, then noone could use that port with any other ip address.
Example;
1.2.3.4 and 1.2.3.5 are two ip of my vserver
box.
and if my client binds 1.2.3.4:7000 then the
other client could not (or nobody could) bind 1.2.3.5:7000 port number. Please
check it. I have check it with an irc deamon program (you can find it on
www.unrealircd.com)
----- Original Message -----
From: "Jacques Gelinas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 09, 2002 9:48
PM
Subject: Re: [vserver] 2.4.19ctx-15 and vserver
0.22
> >
> > [burak@vserver:vs1 home]telnet -b 213.194.112.122 lantar.net
> > Trying 213.194.112.66...
> > telnet: connect to address 213.194.112.66: Operation not permitted
> > [burak@vserver:vs1 home]
> >
> > bind problem looks still occurs??
>
> Oops, had forgotten this case. I will release 2.4.20ctx-16 today with this fix.
>
> Sorry!
>
>
> ---------------------------------------------------------
> Jacques Gelinas <[EMAIL PROTECTED]>
> vserver: run general purpose virtual servers on one box, full speed!
> http://www.solucorp.qc.ca/miscprj/s_context.hc
