Skip to content
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

wireguard mode: binding to both IPv4 and IPv6 by default does not work as expected #6671

Open
decathorpe opened this issue Feb 18, 2024 · 1 comment
Labels
area/core help wanted kind/ux User experience improvements

Comments

@decathorpe
Copy link
Member

This issue was previously reported here:
decathorpe/mitmproxy_wireguard#23

The same potentially problematic code is still present in mitmproxy_rs:
https://github.com/mitmproxy/mitmproxy_rs/blob/main/src/packet_sources/wireguard.rs#L88-L96

I'm opening a ticket here since mitmproxy_rs does not seem to have an open issue tracker.

@decathorpe decathorpe added the kind/triage Unclassified issues label Feb 18, 2024
@mhils
Copy link
Member

mhils commented Feb 18, 2024

For UDP mode, we have fixed this as follows: https://github.com/mitmproxy/mitmproxy/blob/10.2.2/mitmproxy/proxy/mode_servers.py#L294-L310

We should probably do the same for WireGuard :)

@mhils mhils added help wanted area/core kind/ux User experience improvements and removed kind/triage Unclassified issues labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core help wanted kind/ux User experience improvements
Projects
None yet
Development

No branches or pull requests

2 participants