-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Add support for IP_MULTICAST_LOOP socket option #87167
Conversation
Hello @Abd002, and thank you very much for your first pull request to the Zephyr project! |
Thanks for the PR! Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. |
@Abd002 you need to rebase your commits to squash them into a single one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Carles suggested, please read the contribution guidelines. I'd expect only 2 commits:
- Introduction of the
IP_MULTICAST_LOOP
definition - Implementation for
net_context
820abe6
to
f5fc7fe
Compare
f5fc7fe
to
e027ad4
Compare
e027ad4
to
72ab5fe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favor of explicit typing.
4455dfc
to
506479b
Compare
506479b
to
eee0603
Compare
eee0603
to
64ee08c
Compare
It looks like #87338 got in first, will need to rebase this and merge ipv4 with ipv6. |
Also please rebase the PR and squash the merge commit |
shouldn't i merge that to solve this conflict or what ? |
Pull the current zephyr main branch to your fork. |
64ee08c
to
03d9c9f
Compare
564582c
to
f8e2961
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, few more nits
Add support for the IP_MULTICAST_LOOP socket option to control multicast packet loopback. Signed-off-by: AbdElRahman Khalifa <abdelrahman.5alifa@gmail.com>
f8e2961
to
93cd641
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks very nice now.
Hi @Abd002! To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge. Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁 |
net: sockets: Add support for IP_MULTICAST_LOOP socket option
This PR adds support for the IP_MULTICAST_LOOP socket option,
which controls whether multicast packets are looped back to the
sending host.
Fixes: #86977
Signed-off-by: AbdElRahman Khalifa abdelrahman.5alifa@gmail.com