You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So by default CoAPClient::new() binds to 0.0.0.0:0 for Ipv4 and :::0 for Ipv6.
I have the need to use Ipv6's scope_id when binding, so I can specify which interface I want the packet to go out on. SocketAddrV6::new() lets me specify the scope_id I want to use, but the current CoAPClient assumes I want :::0. Allowing the user to pass in another ToSocketAddrs for the bind address would alleviate this issue.
I have forked the repo and made the change so I can continue working, but it'd be cool if the main repo had support for it. Change is here: robbym@4fa038d
To prevent API breakage, maybe a different function that takes both the bind address and destination address?
The text was updated successfully, but these errors were encountered:
So by default
CoAPClient::new()
binds to0.0.0.0:0
for Ipv4 and:::0
for Ipv6.I have the need to use Ipv6's
scope_id
when binding, so I can specify which interface I want the packet to go out on.SocketAddrV6::new()
lets me specify thescope_id
I want to use, but the current CoAPClient assumes I want:::0
. Allowing the user to pass in anotherToSocketAddrs
for the bind address would alleviate this issue.I have forked the repo and made the change so I can continue working, but it'd be cool if the main repo had support for it. Change is here: robbym@4fa038d
To prevent API breakage, maybe a different function that takes both the bind address and destination address?
The text was updated successfully, but these errors were encountered: