Re: [lwip-users] UDP broadcast not working - Socket API

[Daniel Berenguer]

I finally solved the problem!

the author of the port suggested me to look into the dhcp code, that
seemed to work correctly. There I realized that the netif interface
was explicitly declared in each send/receive command. After switching
to udp_sendto_if instead of udp_sendto and using default_netif as the
interface everything worked as expected. I'm now able to send and
receive UDP broadcast messages from a separate thread.

Daniel.


2009/6/19 Daniel Berenguer <address@hidden>:
> Hi Kieran,
>
> I verified that unicast doesn't work either on my platform. Neither
> receiving nor sending. I've tried with both BSD and Raw API's.
>
> The author of the examples has sent me his lwipopts.h file and he
> doesn't remember having done nothing special for his AVR EVK1100
> board. Anyway, the new lwipopts.h changes nothing on the UDP side.
>
> I'm now going to ask the same question in the FreeRTOS forum, just in
> case that this issue has to do with the implementation of lwIP for my
> platform. I'll come back with the results.
>
> Thanks again,
>
> Daniel.
>
>
> 2009/6/19 Kieran Mansley <address@hidden>:
>> On Fri, 2009-06-19 at 15:50 +0200, Daniel Berenguer wrote:
>>> Thanks Kieran for your reply.
>>>
>>> I'm using lwIP 1.3.0 and I successfully built and ran the demo that
>>> came with FreeRTOS, a basic http server. I can now display a simple
>>> web page through lwIP.
>>
>> Would be interesting to see if a simple UDP unicast app worked.  i.e. Is
>> it UDP that isn't working, or broadcast that isn't working, or something
>> else...
>>
>>> this is my complete lwipopts.h code:
>>
>> Looks OK to me.
>>
>> There was a bug concerning UDP broadcast recently:
>>
>> [bug #26309] Implement SOF_BROADCAST
>> https://savannah.nongnu.org/bugs/?26309
>>
>> but I think that was to do with receiving UDP broadcast frames rather
>> than sending them.
>>
>> It might also be worth contacting the authors of the example you're
>> using to see if there is anything special that is required to get it to
>> work.
>>
>> Do you have any kind of debugging tools available on your lwIP device?
>> The quickest way to get a solution to your problem would be to trace
>> through the stack and see how far your packet gets.  Once we know where
>> it is dropped, the solution should be much easier.
>>
>> Kieran
>>
>>
>>
>>
>> _______________________________________________
>> lwip-users mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/lwip-users
>>
>
>
>