-
Notifications
You must be signed in to change notification settings - Fork 232
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 IPV6_TCLASS and IPV6_RECVTCLASS #364
Conversation
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.
Can you switch the ordering of the functions, first the getter than the setter.
f300a30
to
8e2e04d
Compare
Done Should I remove |
Sure 👍 |
8e2e04d
to
130a517
Compare
@duskmoon314 can you fix the failing CI for Windows? See https://github.com/rust-lang/socket2/actions/runs/3740167945/jobs/6348219101 |
Sure. I am looking for MS documentation on this setting |
It seems that Microsoft doesn't allow modifying the traffic class of IPv6 win-socket as in Unix-like OS. For IPv4, using
And for IPv6, no I am considering adding |
Yes, that's the way to go I think. However if it's not available on Windows it need to be behind the Lines 1048 to 1076 in fa67e04
|
Sure. I will modify the code ASAP. |
d9cdd0f
to
085c9e1
Compare
I'll squash the commit I've added. |
A simple implementation of the IPV6_TCLASS and IPV6_RECVTCLASS modeled after the existing IP_TOS and IP_RECVTOS implementations. Remove useless bool to i32 conversion in `set_recv_tos` close rust-lang#363
62e2b02
to
bada246
Compare
Thanks @duskmoon314! |
A simple implementation of the IPV6_TCLASS and IPV6_RECVTCLASS modeled after the existing IP_TOS and IP_RECVTOS implementations.
close #363