Re: [lwip-users] DHCP callback was removed - Correct way to obtain new address?

2014-09-03 Thread Sergio R. Caprile
According to the wiki, the correct way to initialize a DHCP interface is to call dhcp_start() and not netif_set_up(). So, summarizing: you can poll for netif.dhcp-state == DHCP_BOUND you can define LWIP_NETIF_STATUS_CALLBACK, and call void netif_set_status_callback(struct netif *netif,

[lwip-users] DHCP callback was removed - Correct way to obtain new address?

2014-08-29 Thread Chris Maier
Hi all, I am just porting my application from version 1.3.2 to the latest 1.4.2. and I was wondering why my application does not get called back from the stack when the DHCP As I found out the callback was removed. My application has to know the address for displaying purposes, so do I have

Re: [lwip-users] DHCP callback was removed - Correct way to obtain new address?

2014-08-29 Thread Paul Webber
was removed - Correct way to obtain new address? Hi all, I am just porting my application from version 1.3.2 to the latest 1.4.2. and I was wondering why my application does not get called back from the stack when the DHCP As I found out the callback was removed. My application has to know

Re: [lwip-users] DHCP callback was removed - Correct way to obtain new address?

2014-08-29 Thread Sergio R. Caprile
When I did it, I basically polled for netif.dhcp-state == DHCP_BOUND and read ipaddr = netif.ip_addr; netmask = netif.netmask; gw = netif.gw; but now I realize the dhcp code calls netif_set_up() when it reaches that state, which also calls NETIF_STATUS_CALLBACK if