[release/10.0] [OSX] ip_mreqn struct is not supported for IPv4 Multicast #119480
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…IFINDEX for interface index specification
karelz
approved these changes
Sep 11, 2025
|
@artl93 can you please merge it if you approve? This will make .NET 10 as LTS work better on macOS 26. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #119354 to release/10.0
/cc @liveans
Customer Impact
Running CI on latest macOS 26 showed a problem in IPv4 Multicast Interface. It is a regression against macOS 13.
Found internally via CI runs.
Regression
Technically yes -- due to different behavior of macOS Kernel -- since macOS 14 (see details above).
Testing
Failing CI tests now pass + manual testing of the Multicast Interface scenario (hard to automate).
Risk
Low, this was broken for a while since macOS 14.