From: Gerrit Hoetzel (gt_at_hzhome.mine.nu)
Date: Thu 26 Dec 2002 - 21:00:11 GMT
Hi,
I noticed a strange behaviour already mentioned by Jesper FA (who got no
replies) in August.
When running a "netcat -l 0.0.0.0" (do NOT give a specific port !)
netcat will listen to some port bound on 0.0.0.0.
Every vserver on the system may now connect to this port (although
netstat doesn't list this port within other vservers).
Well, at lest to some extend: netcat exits with an "invalid connection"
error.
When running "netcat -l 0.0.0.0 -p 7777" everything is fine.
Running "netcat -l 1234" or some other bogus IP netcat will bind to
0.0.0.0, too.
I am using a 2.4.19ctx-15 kernel.
Do I miss something here? Of course the vservers is running chbind'd
to one specific IP (not being 0.0.0.0).
Any ideas ?