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
There may be some issues for bindToDevice but I did no further investigation.
According to Microsoft documents and other proxy software, interface index should be a DWORD (uint32) in network byte order for IP_UNICAST_IF, and in host byte order for IPV6_UNICAST_IF.
returnnewError("failed to set IPV6_UNICAST_IF", err)
}
}
On Darwin and Windows, it tries to set bothIP_(UNICAST|BOUND)_IF and IPV6_(UNICAST|BOUND)_IF for a single socket without ignoring expected errors. Normally only one of them should be set.
On Windows, only applyOutboundSocketOptions calls bindToDevice. But on Darwin and Linux both applyOutboundSocketOptions and applyInboundSocketOptions call bindToDevice.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There may be some issues for
bindToDevice
but I did no further investigation.DWORD
(uint32) in network byte order forIP_UNICAST_IF
, and in host byte order forIPV6_UNICAST_IF
.v2ray-core/transport/internet/sockopt_windows.go
Lines 42 to 53 in 458db39
IP_(UNICAST|BOUND)_IF
andIPV6_(UNICAST|BOUND)_IF
for a single socket without ignoring expected errors. Normally only one of them should be set.applyOutboundSocketOptions
callsbindToDevice
. But on Darwin and Linux bothapplyOutboundSocketOptions
andapplyInboundSocketOptions
callbindToDevice
.Beta Was this translation helpful? Give feedback.
All reactions