[X] I have read the documentation and understand the meaning of all the configuration items I have written, rather than just piling up seemingly useful options or default values.
[X] I have carefully reviewed the documentation and have not resolved the issue.
[X] I have searched the Issue Tracker for the issue I want to raise and did not find it.
[ ] I am a non-Chinese user.
[X] I have tested with the latest Alpha branch version, and the issue still persists.
[X] I have provided the server and client configuration files and processes that can reproduce the issue locally, rather than a sanitized complex client configuration file.
[X] I provided the simplest configuration that can be used to reproduce the errors in my report, rather than relying on remote servers or piling on a lot of unnecessary configurations for reproduction.
[X] I have provided complete logs, rather than just the parts I think are useful out of confidence in my own intelligence.
[X] I have directly reproduced the error using the Mihomo command-line program, rather than using other tools or scripts.
Operating System
Linux
System Version
6.10.10-aosc-main
Mihomo Version
Mihomo Meta alpha-de19f92 linux amd64 with go1.23.2 Thu Nov 14 02:09:03 UTC 2024
Use tags: with_gvisor
Verify steps
Operating System
Linux
System Version
6.10.10-aosc-main
Mihomo Version
Mihomo Meta alpha-de19f92 linux amd64 with go1.23.2 Thu Nov 14 02:09:03 UTC 2024 Use tags: with_gvisor
Configuration File
Description
the core's proxy listener ports can not be connected via IPv6 Link-Local address, even firewall disabled.
however, it works well with this use-case if use the core version 1.18.8.
Reproduction Steps
curl -x socks5://[fe80::xxxx:xxxx:xxxx:xxxx%eno1]:9999 1.1.1.1/cdn-cgi/trace
Connection reset by peer
error outputs. the core have no any error log outputs.Logs