lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-users] parameter for netif_add in UDP


From: Ben Bobbitt
Subject: RE: [lwip-users] parameter for netif_add in UDP
Date: Wed, 13 Feb 2008 18:53:23 -0600

Thanks for the quick response.  I'm a little confused by the driver comment,
though.  What should I have to do in that regard?  

The symptom that I am seeing (using wireshark to view the packets ) is that
my system is sending out an ICMP reject (port unreachable) when the UDP
packets reach him. This would seem to indicate some problem with the setup
in regard to the UDP service.  

Here's what I am doing to set up the interface...
My addresses at this point are all 0 because of using DHCP

sys_init();
  mem_init();
  memp_init();
  pbuf_init();
  netif_init();
  ip_init();  
  udp_init();  
  tcpip_init( prvEthernetConfigureInterface, NULL );

where in prvEthernetConfigureInterface:

netif_add(&MACB_if, &xIpAddr, &xNetMask, &xGateway, NULL, ethernetif_init,
tcpip_input);
netif_set_default(&MACB_if);
dhcp_start(&MACB_if);

in my UDP task, I'm waiting while MACB_if.dhcp->state != DHCP_BOUND before
calling netconn_new().   

Of course, I've checked all of the UDP related config options that I can
find in the lwipopts.h   

Ben

 

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Jonathan Larmour
Sent: Wednesday, February 13, 2008 6:16 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] parameter for netif_add in UDP

Ben Bobbitt wrote:
> 
> 
> Just curious if I’ve missed something in the documentation,  but my 
> application only needs to use UDP, so what parameter do I pass to the 
> netif_add() function for the input() callback when setting up the 
> interface?
[snip]
> Any advice would be appreciated.    I am using the atmel avr32 and the 
> IAR compiler.   This is under FreeRTOS with the 1.2.0 version of lwIP.   

For lwIP 1.2.0, you should use tcpip_input. That way it gets sent to 
lwip's tcpip handling thread, which means that the packet is passed in to 
the stack in the correct context.

Note that for ethernet interfaces, your driver will also have had to 
interface with the etharp code to pass packets in.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine


_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.4/1276 - Release Date: 2/13/2008
9:41 AM
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.4/1276 - Release Date: 2/13/2008
9:41 AM
 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]