# Google SoC lwIP Report Week 10

DevFeed: [Google SoC lwIP Report Week 10](<https://devfeed.tech/articles/google-soc-lwip-report-week-10-32785.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/google-soc-lwip-report-week-10/>)

Published: 2016-08-01T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [lwIP](<https://devfeed.tech/topics/lwip.md>), [SOC](<https://devfeed.tech/topics/soc.md>), [Google](<https://devfeed.tech/topics/google.md>), [Network](<https://devfeed.tech/topics/network.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [bugs](<https://devfeed.tech/tags/bugs.md>), [code](<https://devfeed.tech/tags/code.md>), [free](<https://devfeed.tech/tags/free.md>), [google](<https://devfeed.tech/tags/google.md>), [lwip](<https://devfeed.tech/tags/lwip.md>), [network](<https://devfeed.tech/tags/network.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [soc](<https://devfeed.tech/tags/soc.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

A Google Summer of Code progress report on rewriting lwIP driver functions and addressing bugs in TDI_LISTEN handling. It explains how TCP_CONTEXT and ADDRESS_FILE structures map to sockets, connections, local addresses, and listener behavior across lwIP and AFD/TDI.

## Source excerpt

Having rewritten all of the functions that I implemented and modified some of the functions that already existed before I started on this project at the end of last week, I now had to start flushing all of the bugs that invariably exist after a rewrite. The major issue I dealt with this past week revolved around properly handling a TDI_LISTEN. Part of the purpose for the rewrite was to reorganize my data so each TCP_CONTEXT struct represented a user socket or connection endpoint, and each ADDRESS_FILE struct only represented a local network address.