[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #3168] Handling UDP/TCP PCBs upon netif address change

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #3168] Handling UDP/TCP PCBs upon netif address change.
Date: Mon, 14 May 2007 17:37:10 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

Follow-up Comment #15, bug #3168 (project lwip):

>After trying on Linux, even when the locally bound address goes away, recv()
will remain blocked and not report an error. Even if I do a non-blocking
recv(), still no error is returned, and netstat shows the listening socket
remains bound to the (now gone) address. 

Hearing that, I'll check in my change that udp_send() checks the local
address. That way we make sure we don't send packets from the old address.

On the receive side, the application has to work around that (like it has to
do on linux). We are already supplying the functions for that
(netif->callback, maybe we should call that on IP address change also?) or
the app must use a receive timeout (or not bind to a specific address ;-)

I think we would be done with that. Only out of interest: what happens on
linux with a tcp socket that is in a blocking recv call?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]