bind() udp behavior 2.6.8.1

[Adam Denenberg]

Hello,

 I am not subscribed to this list so please CC me personally in
response. 

 I am noticing some odd behavior with linux 2.6.8.1 on a redhat 8 box
when making udp requests.  It seems subsequent udp calls are all
allocating the same source ephemeral udp port.  I believe the kernel
should be randomizing these (or incrementing) these ports for subsequent
requests.  We ran a test C program that just put a gethostbyname_r call
in a for loop of 40 calls and all 40 requests used the same UDP source
port (32789).  This is causing our firewall to drop some packets since
it thinks it already closed that connection due to too many transactions
using same udp source/dest port passing thru in too short a time frame.

Is this a bug in how the linux kernel handles allocating udp source
ports? Freebsd seems to not do this, so i dont think this is a standard
methodology of how UDP/IP should function.

Any help would be appreciated..

thanks
adam


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/