[Bug] unable to use mihomo's proxy listener ports via IPv6 Link-Local address

[Fearyncess]

Verify steps

• 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.
• I have carefully reviewed the documentation and have not resolved the issue.
• I have searched the Issue Tracker for the issue I want to raise and did not find it.
• I am a non-Chinese user.
• I have tested with the latest Alpha branch version, and the issue still persists.
• 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.
• 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.
• I have provided complete logs, rather than just the parts I think are useful out of confidence in my own intelligence.
• 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

Configuration File

log-level: debug

mixed-port: 9998
allow-lan: true

mode: rule
ipv6: true

listeners:
  - name: socks-in
    type: socks
    port: 9999
    listen: "::"
    udp: true

rules:
  - 'MATCH,DIRECT'

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

• run the core with the config above
• use server's ipv6 link-local address to connect the proxy listener ports,
  eg. curl -x socks5://[fe80::xxxx:xxxx:xxxx:xxxx%eno1]:9999 1.1.1.1/cdn-cgi/trace
• the client will fail with Connection reset by peer error outputs. the core have no any error log outputs.

Logs

INFO[2024-11-17T17:01:10.169757405+08:00] Start initial configuration in progress
INFO[2024-11-17T17:01:10.169816407+08:00] Geodata Loader mode: memconservative
INFO[2024-11-17T17:01:10.169823528+08:00] Geosite Matcher implementation: succinct
INFO[2024-11-17T17:01:10.170025904+08:00] Initial configuration complete, total time: 0ms
INFO[2024-11-17T17:01:10.178119813+08:00] Sniffer is closed
INFO[2024-11-17T17:01:10.178252027+08:00] SOCKS[socks-in] proxy listening at: [::]:9999
INFO[2024-11-17T17:01:10.178288379+08:00] Mixed(http+socks) proxy listening at: [::]:9998
WARN[2024-11-17T17:01:11.137208602+08:00] [CacheFile] can't open cache file: timeout
INFO[2024-11-17T17:01:11.1380559+08:00] Start initial Compatible provider default

[Fearyncess]

i found that seems cd2d1c6 causes this bug (or regression?) after bisects.

[Fearyncess]

80e4eaa lgtm.