You are right, its seems like linux bug I see a patch that fixes it to free bsd, I cant find one to linux too This limit the traffic to only 400mbits for each machine, it is a pity... -----Original Message----- From: KOVACS Krisztian [mailto:hidden@sch.bme.hu] Sent: Thursday, May 07, 2009 12:14 PM To: elyasaf Cc: 'KOVACS Krisztian'; tproxy@lists.balabit.hu Subject: Re: [tproxy] tproxy bind failed - limit of TPROXY bind Hi, On Wed, May 06, 2009 at 08:35:19PM +0300, elyasaf wrote:
Thank you for your response
I have more than 2Gbits (all tcp and udp via tproxy) on my networks, with more than 20k different active ips
I am not using the same ip twice (local_addr.sin_addr.s_addr++;) Than I expected tproxy don't mix the bind, and treat them like different interface And my sample code, I think approve it
Indeed, sorry. Have you tried removing the setsockopt(IP_TRANSPARENT) call from you program? I'm asking because tproxy should not make a difference in how bind() behaves (none of the tproxy patches changed that part of the kernel). -- KOVACS Krisztian