Won't we need to make sure the socket options SO_SNDBUF and SO_RCVBUF fit
MTU? Doing a UDP sendto, for example can cause an EMSGSIZE if the message
is longer than SO_SNDBUF.
--Nick
On Wed, Aug 4, 2010 at 10:07 PM, Varun Chandramohan <
var...@linux.vnet.ibm.com> wrote:
> Hi Richard,
>
> As per
Hi Nick,
On 08/12/2010 12:42 AM, Nick Wagner wrote:
> I agree that it's not ideal for the multicast-bound socket to be used
> for unicast. For one thing, on some platforms the binding address
> affects the source address, which can be confusing for someone trying
> to respond (or sniff).
But s
I had meant the source IP address, not the source port.
Anyway, I've added the patch which does a search for the unicast socket.
I've made this change a Darwin-only change for two reasons: 1) things work
correctly the way they are now on Linux. 2) Linux is more selective about
data sent to a so
Correction. More multi-nic testing on OSX showed a similar problem with the
list. One of those days, I guess. :)
So the darwin version now calls socket() and closes it after the sendto.
While this is more portable, I kept it in the Darwin #ifdef, because I
wasn't sure if we wanted to create ext
Hi Nick,
I think you are right. May be we should have a check for that. Iam
adding the author of the patch to this mail. He is not subscribed to this ML,
so please do reply all
so that he is kept in loop. In our labs we have had major issues to get this
working. If you have suggest
