Pomeroy, Marty wrote: > > That syntax is going to call dhcp_start() from your application thread, > and pass the return value to tcpip_callback: not what you want. > > Try netifapi_netif_common( &netif_default, NULL, dhcp_start); > > Not sure if you have tried this: don't use the static IP address at all > (use 0.0.0.0), and see if DHCP works right. > Like i said it works fine only when i start dhcp_start from my application thread while locking the scheduler, without tcpip_callback.
Due to time pressure we have decided to stay on LWIP 1.1.1 so i dont have this function. Can't LWIP 1.1.1 manage this problem? -- View this message in context: http://old.nabble.com/Start-DHCP-from-application-thread-not-tcpip-thread-tp34004026p34009943.html Sent from the lwip-users mailing list archive at Nabble.com. _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
