Skip to content

Restore logic on when to open an address specific socket #502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

dougnazar
Copy link
Contributor

850f93b changed the logic while moving things around. Restore the original logic so we open a socket even if the address is the same, so long as it's the first time.

Fixes: #501

850f93b changed the logic while moving things around. Restore
the original logic so we open a socket even if the address is the
same, so long as it's the first time.
@rsmarples rsmarples merged commit 67af1db into NetworkConfiguration:master Apr 25, 2025
16 checks passed
@dougnazar dougnazar deleted the fix_address_socket_logic branch April 25, 2025 22:33
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request May 16, 2025
* Restore logic on when to open an address specific socket by @dougnazar in NetworkConfiguration/dhcpcd#502
* [Fix] DHCP Failure on WAN Interface Rename (Fixes #504) by @ngxquanganh in NetworkConfiguration/dhcpcd#505
* BSD: routes via P2P interfaces now find their out-going interface
* -b --background fixed
* resolv: Fix processing more DNSSL options than RDNSS]
* dhcpcd: Remove option rapid_commit from dhcpcd.conf
* privsep: Fix valgrind and hardened-malloc on Linux with SECCOMP
* route: Don't spam route changes for lifetime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dhcpcd fails to open address specific socket after binding
2 participants