rms/win-split-tunnel
1
0
Fork 0
mirror of https://github.com/amnezia-vpn/win-split-tunnel.git synced 2026-05-17 08:16:00 +03:00
Code Issues Packages Projects Releases Wiki Activity

Extend readme with section on multicast

Browse Source
This commit is contained in:
Odd Stranne
2021-05-07 12:42:02 +02:00
parent 83d01961ce
commit 68ebaf276d
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -127,6 +127,14 @@ This means that, for excluded apps, if a socket isn't explicitly bound to `127.0
Because explicitly bound client sockets are rare, it can be expected that most excluded apps are affected. No generally applicable mitigations are available.
## Multicast reception
When configuring a network socket for multicast packet reception, it's common to both bind `inaddr_any` and join a multicast group on that same address. This is problematic on multi-homed machines such as a machine with an active VPN connection, because the "wrong" interface may be selected behind the scenes.
If we add split tunneling into the mix things become even more complicated. With split tunneling engaged, the socket bind will be redirected to the LAN interface but the group join will still be on `inaddr_any`. This will typically not result in any API errors but the net effect is that incoming traffic can't be properly matched, and will instead be discarded.
No generally applicable mitigations are available.
# License
Copyright (C) 2021 Mullvad VPN AB