Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

net: Wrong localPort on using the same socket object for multiple connect/destroy #25621

Closed
phanikumars opened this issue Jul 3, 2015 · 3 comments
Closed

net: Wrong localPort on using the same socket object for multiple connect/destroy #25621

phanikumars opened this issue Jul 3, 2015 · 3 comments

Comments

@phanikumars
Copy link

When the same socket object is used for multiple .connect(), the socket.localPort is not refreshing with new localPort used by the OS.

See the discussion on mailing list:
https://groups.google.com/d/topic/nodejs/eT3xanyP83U/discussion
@cjihrig
Copy link

cjihrig commented Jul 3, 2015

Related io.js PR - nodejs/node#2095

@rmg
Copy link

rmg commented Jul 3, 2015

AFAICT, this bug is present in 0.10, 0.12, and iojs. I didn't bother looking back any further, but I suspect it has been around for a little while.

This was referenced Jul 22, 2015
Closed
Closed
@rmg
Copy link

rmg commented Jul 22, 2015

I've also opened PR #25753 in this repo in case it is more convenient.

@Trott Trott closed this as completed Apr 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rmg @Trott @cjihrig @phanikumars