Bind succeeds for a used port

Hi

We are seeing that a socket which is already ESTABLISHED and the
local addressort and remote address: port are the same.

i) How is this possible ?
ii)Another process tried to listen on the same port on which
connection was
already Established , and seems to be successful

Linux Kernel version is :: 2.2.14-6.1.1

Below please find the netstat -a on port 4419


tcp 0 0 0.0.0.0:4419 0.0.0.0:*
LISTEN
tcp 0 0 10.202.112.9:4419 10.202.112.9:4419
ESTABLISHED


Can anyone please explain this?

Thanks
Prasad

On 15 Apr 2004 02:44:38 -0700, prasad <(E-Mail Removed)> wrote:
> Hi
>
> We are seeing that a socket which is already ESTABLISHED and the
> local addressort and remote address: port are the same.
>
> i) How is this possible ?
> ii)Another process tried to listen on the same port on which
> connection was
> already Established , and seems to be successful
>
> Linux Kernel version is :: 2.2.14-6.1.1
>
> Below please find the netstat -a on port 4419
>
>
> tcp 0 0 0.0.0.0:4419 0.0.0.0:*
> LISTEN
> tcp 0 0 10.202.112.9:4419 10.202.112.9:4419
> ESTABLISHED
>
>
> Can anyone please explain this?

I don't understand your questions. You show what appears to be ONE daemon
[or (x)inetd] bound to (listening on) a port. And you show one connection
established to that port. The "Foreign" port usually has nothing to do
with the "Local" port, even if on the same machine.

So what you have here is one thing bound to port 4419 listening for any
connection. And you have one client connected to that port (possibly
with a forked copy of whatever is listening for new connections). The
port you are connecting to that listening port is a non-issue. Show us
the second connection that can listen in on, or conflict with the
established connection (same Local and Foreign IPs and ports).

--
David Efflandt - All spam ignored http://www.de-srv.com/

prasad wrote:
> Hi
>
> We are seeing that a socket which is already ESTABLISHED and the
> local addressort and remote address: port are the same.
>
> i) How is this possible ?
> ii)Another process tried to listen on the same port on which
> connection was
> already Established , and seems to be successful
>
> Linux Kernel version is :: 2.2.14-6.1.1
>
> Below please find the netstat -a on port 4419
>
>
> tcp 0 0 0.0.0.0:4419 0.0.0.0:*
> LISTEN
> tcp 0 0 10.202.112.9:4419 10.202.112.9:4419
> ESTABLISHED
>
>
> Can anyone please explain this?

Take a look at the output from "netstat -tupan" and see what it
tells you.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.26 SMP i686 (GCC) 3.3.3
Uptime: 1 day, 1:04, 1 user, load average: 0.09, 0.06, 0.10