|
| From: | Bill Auerbach |
| Subject: | RE: [lwip-users] OT: Binding UDP in WinXP |
| Date: | Wed, 15 Jul 2009 17:14:37 -0400 |
|
Yes, I think so. I think the idea is to have one socket on
the PC receive all data from all IP addresses on the port and dispatch who gets
the data at the application level. I hoped that the stack would do this
and each WinXP UDP socket would tell me when there is incoming data from the
one IP address. One MS help file mentioned binding a UDP socket to a
fixed address is “frowned upon”. I don’t understand the
rationale or reasoning behind this. I’ll have to switch to using
one socket on the PC and handle multiple devices myself unless someone knows of
a way to bind UDP to a remote address. Thanks for your reply. Bill From:
address@hidden
[mailto:address@hidden On Behalf
Of Marek Hi, not sure if I understood
you correctly, but isn't that udp packets (unlike tcp), are transmitted over
the network without creating any connection before ? 2009/7/15 Bill Auerbach <address@hidden> After half a day at this
problem that I can’t solve, I figure someone here might say the
answer is, “You
can’t” and I’ll know I have a big problem. J I can send UDP data from WinXP to lwIP using SentTo no
problem. I can receive from lwIP if I use the port and IP_ADDRANY.
I realized with 2 of my devices connected I have a problem so I tried to bind
the UDP socket in WinXP to the IP address and port of the lwIP device (I know
it from a prior UDP “here
I am” broadcast). WinXP refuses to bind (or connect) to a specific
IP address. I know I’m missing something and spent half the day not
finding it. How do you bind a WinXP SOCK_DGRAM socket to a remote IP
address and port? Thank you, Bill
|
| [Prev in Thread] | Current Thread | [Next in Thread] |