Bug 1957 – UdpSocketImpl is stuck after a Close()

Bug 1957 - UdpSocketImpl is stuck after a Close()


Summary:	UdpSocketImpl is stuck after a Close()

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	internet
Version:	ns-3-dev
Hardware:	All All

Importance:	P5 minor
Assigned To:	George Riley

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-07-29 17:04 EDT by Tommaso Pecorella
Modified:	2014-10-12 10:04 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
patch (527 bytes, patch) 2014-07-30 14:09 EDT, Tommaso Pecorella	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tommaso Pecorella 2014-07-29 17:04:35 EDT

After a Close() a UdpSOcket has both m_shutdownRecv and m_shutdownSend set to true.

Re-opening the socket (e.g., by using Bind() or Connect()) will not clear them, so the socket is stuck in non-sending, non-receiving state.

The obvious solution is to clear them in
int UdpSocketImpl::FinishBind (void)

Comment 1 Tommaso Pecorella 2014-07-30 14:09:41 EDT

Created attachment 1859 [details]
patch

Comment 2 Tom Henderson 2014-10-02 13:44:10 EDT

Suggest to commit if no further comments.

Comment 3 Tommaso Pecorella 2014-10-12 10:04:38 EDT

changeset 11011:68da08e92ffa