23 Nov
2007
23 Nov
'07
6:53 a.m.
From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
Just want to mention that the problem is fixed by doing a bind after setsockopt(....IP_FREEBIND... ).
There are some minor changes in behavior as compared to tproxy2, but overall I would think that the tproxy4 behaviour might be considered more correct !
Sorry to contradict my ownself. It seems my testing was not quite conclusive. I will report again as soon as I have conclusion. Please ignore my previous posts. Regards.