It's normal for the kernel to hold onto a port for a while after it's been closed.

I believe it's so that you don't get another program grabbing the port number and receiving data that was meant for the first program. Partly that's good for security, and partly it stops the program getting data not meant for it which may confuse it.

-Steve


On 30 January 2011 17:37, Madovsky <infos@madovsky.org> wrote:
right, after hours I checked it again and yes, the kernel removed them.
 
Thanks Steve
----- Original Message -----
Sent: Sunday, January 30, 2011 6:06 AM
Subject: Re: [Freeswitch-users] clean UDP sockets

The kernel will clean them up in it's own good time. Don't worry about it.

Steve on iPhone

On 30 Jan 2011, at 04:28, "Madovsky" <infos@madovsky.org> wrote:

is there a way to clean inactive UDP sockets after
a timeout ?
when I do on my linux console
[bash] # netstat -tuvnap
I can see a lot of UDP sockets not removed after calls.
tried also to modify the kernel with nf_conntrack_udp_timeout without success.
 
Thanks

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org