On 2/13/06, KOVACS Krisztian <hidden@xxxxxxxxxx> wrote: > > > Unfortunately not, at least not without modifying the source code :) The > behaviour of the NAT code changed when Rusty's NAT simplifications were > merged in 2.6.11. I personally think this new behaviour is better than > the old one, as it provides increased performance and better cooperation > with load balancing solutions and other NAT-sensitive equipment. > > Why exactly do you want to achieve the round-robin behaviour for one > internal IP? > > -- > KOVACS Krisztian > Hi, Thanks for your response. I would like to simulate thousands of clients with the following setup in order to stress test our in-house product: Client ---> SNAT box ---> In-house Gateway --> Server Before 2.6.11 kernel, the SNAT box was mapping every new socket from the Client to a new source IP address. With this, I was able to simulate several thousands "virtual" clients. Now with the new behaviour, every socket from the Client to the Server is mapped to the same random but fixed source IP address. I am sure the new NAT implementation is better and cleaner than the old one, but it also takes away a nice round-robin feature per socket. Is there any way I can achieve the previous behaviour without modifying the kernel source code :-( or downgrading to a pre-2.6.11 kernel? (I am writing some ip_conntrack/ip_nat modules based on the new 2.6.11+ API, so downgrading the kernel is going to be painful) Thanks, Khoa
