# best approach to lwip **URL:** \ **Category:** Kernel\ **Created:** [March 12, 2009, 5:04pm UTC](https://forums.freertos.org/t/best-approach-to-lwip/3496 "2009-03-12T17:04:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [March 12, 2009, 5:04pm UTC](https://forums.freertos.org/t/best-approach-to-lwip/3496/1 "2009-03-12T17:04:49Z")
**[sergiosider](https://sourceforge.net/u/sergiosider/)** wrote on [Thursday, March 12, 2009](https://sourceforge.net/p/freertos/discussion/382005/thread/999c0a0b/#aa32): HI all, I need an opinion: I am used to lwip raw interface, and like it´s simplicity and callback approach. For years, I was using in my embedded programs, a simple cooperative "multitasking" interface, where I call all tasks sequentially in the main loop, using a simple ticker. I am now starting to try FreeRTOS… What´s the best way to use lwip ?  Continue to use raw api (I suppose I have to do it inside one single task)? or start using netcon to take  advantage of the multitasking? I know the answer might depend on the complexity of my design, but is one approach way better than the other so I just should not think about it ? Thanks for any advice! Sergio P. Sider ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [March 12, 2009, 9:03pm UTC](https://forums.freertos.org/t/best-approach-to-lwip/3496/2 "2009-03-12T21:03:18Z")
**[edwards3](https://sourceforge.net/u/edwards3/)** wrote on [Thursday, March 12, 2009](https://sourceforge.net/p/freertos/discussion/382005/thread/999c0a0b/#aa32/f10a): I would suggest getting yourself over to the lwIP mailing list. They are a very friendly and helpful bunch and expert on this.