Please see the answers embedded.
On Feb 25, 2016, at 11:42 PM, Patrik Flykt
On Wed, 2016-02-24 at 11:32 -0800, Feng Wang wrote:
> But in some cases, the socket is closed after the DHCP ACK is
What are these cases on ConnMan side where the socket is closed after
the ACK is received? Or what code path does the code take in that case?
Isn't it easier to identify that code path or special case and figure
out if there is an easier solution fixing it?
For ConnMan side, the code path is no difference. The difference is when trying
to close the socket in the ConnMan, the socket was NOT closed immediately because the
close function can be rescheduled or there are some packets just rxed, the close will
happen later. And the main point is why using two sockets(one is for transmitting and
one is for receiving) instead of one socket both for tx and rx?