Well, you probably have noticed that somewhere in your code you call
netif_set_up()... if you browse src/core/netif.c you'll see that there
is a netif_set_down()... but if you are just starting out of DHCP on
someone else's code you overlooked that.
http://lwip.wikia.com/wiki/Network_interfaces_management
What is the API you are using ? NO_SYS=?
If you use the raw API you control your hardware and your timing, so you
can just not call the stack and leave your hardware alone.
If you use NO_SYS=1, "the timers" is that fancy call in your main loop
that looks like this:
sys_check_timeouts();
If you use an RTOS, ask the one who set the framework, the RTOS provides
a timer and you call lwIP time function on that.
http://lwip.wikia.com/wiki/LwIP_with_or_without_an_operating_system
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
