On Thu, Jun 23, 2011 at 2:35 PM, fooler mail <[email protected]> wrote: > On Thu, Jun 23, 2011 at 1:32 PM, Anonymous `M` <[email protected]> wrote: >> hi fooler, >> thanks for the informative response. >> i wonder what is your "elegant" solution to that. =) does the bug still >> exists even today after recent kernel release? >> thanks! > > hi anonymous, > > the bug that i discovered in linux was in 2008... linux properly > recieved the RST segment coming from loadbalancer as seen from tcpdump > inside linux server... by the time loadbalancer tried to reuse that > socket pair to reconnect again to linux (initiate to complete 3-way > handshake).. linux send invalid response...
This is a gem in the rough here. I think I've seen this behavior before, in some client's web app where its front-end balancers would sometimes get invalid responses from the app server because the front-ends were aggressively reusing socket pairs... > im not sure if that bug is still in there but i guess it is still in > there as i havent check it lately.. it requires for me to make raw > socket programming to simulate that kind of connectivity (which is not > my priority right now) to show here in plug... the reason why i didn't > bother to report this bug aside from it takes time to fix the bug.. > the source port from loadbalancer is going to exhaust eventually as > more and more users are using that service as time pass by... source > ip is the load balancer ip, destination IPs are linux servers and > destination port is port 80... since port is 16 bit... maximum is > 64k... 64k is not enough at extremly high loads.. It is probably still there. -- Zak B. Elep || zakame.net 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
