|
From: | Kai Parow-Souchon |
Subject: | Re: [lwip-users] UDP-server not working! |
Date: | Mon, 01 Aug 2011 14:29:08 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 |
Hey! first, let me thank you all for your help :)And yes, Kieran is right, my "server" should be able to receive commands or requests and should answer with anything appriopriate to that. In my understanding this would make it a server ;)
@Marcos: doesn't work, but this values are definitively written in udp_bind...
@Kieran: tracking a packet through debug-outputs is kind of difficult, as my debug outputs are crashing the ARM from time to time (when setting IP_DEBUG). Setting only UDP_DEBUG i just get a lot of confusing logs which doesn't seem to be related to the event me sending a debug-packet to the ARM.
I once got a "UDP: not for us" message, but that was just once.The outputs for bind are completely chaotic, number encoding doesn't seem to like me at the moment.
I'll have a look on that soon... Thanks all, Kai Am 01.08.2011 14:19, schrieb Kieran Mansley:
On Mon, 2011-08-01 at 09:46 +0100, Chris Williams wrote:You talk about a server? A server sends data to something else. Looking at the code you seem to be trying to receive UDP data ie client!The distinction between server and client is always a difficult one, as both involve sending and receiving, but a server will typically first receive a request, then send its response, with a client the other way round. I think their server is trying to receive the request and failing. Kieran _______________________________________________ lwip-users mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/lwip-users
[Prev in Thread] | Current Thread | [Next in Thread] |