Re: [lwip-users] bug #2240 - UDP pcb connect behaviour

[Ed Sutter]

Leon,
Yes, I beleive that's correct.  My change to udp.c for this
assumes connectionless behaviour, so now I'm going to
advertise my stupidity... Isn't that the way UDP should work?

Assuming there are cases where accept() and connect() are
used with UDP, then maybe a real fix would be to have some
kind of flag field in the pcb that allows udp_input() to
determine if it is a connection or connectionless bind.
Then udp_input() can decide based on the PCB that matches
the incoming portnumber whether or not to pass the packet
up the stack.
Does that make sense? 
Thanks!
Ed


Leon Woestenberg wrote:
> 
> Ed Suller submitted this bug report. (Thanks Ed.)
> 
> >A UDP server appears to "lock on" to the IP address of
> >he first client that communicates with it. After the first
> >client transaction, no other client (different IP) can
> >communcate with that server. Assuming that it is agreed
> >by all that this is a bug, I have what I think is a
> >fix for this and will submit a patch.
> 
> This behaviour corresponds with accept() or connect(), where the socket
> connects with the
> remote IP address and remote UDP port address. Ed's fix probably implements
> recvfrom() behaviour,
> where the socket stays unconnected to a remote address.
> 
> None of both is wrong, but we should make both available and especially well
> documented.
> 
> Regards, Leon.
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/lwip-users

els.vcf
Description: Card for Ed Sutter