hotfix(panel): bind inbounds to stack wildcard instead of registered public address

Inbounds were pinned to the server's registered public address
(ipv4: PublicAddress, ipv6: PublicAddressV6), so addresses not
registered as 'the' public address - intranet NICs used for relay
landings, additional v6 addresses - had nothing listening and
intranet relays were unreachable (field-verified: ss showed the
landing port bound to the public IP only). 3x-ui/xray bind the
wildcard and serve these paths fine.

- listenAddress: explicit bindAddress still wins; ipv4 -> 0.0.0.0,
  ipv6 -> ::, dual -> :: (ipv6 wildcard per user decision
  2026-10-21: multi-v6 machines must serve all their v6 addresses).
- ResolveBindAddress: no longer resolves the registered address
  into a bind pin (that resolution was the production path of the
  pinning via resourceForNode/resourceForNodeExit); returns
  ("", nil) for all stacks, as it already did for dual/absent.
- serverAddress (client connection address / subscription host)
  is unchanged.
- Golden fixtures updated for the three listen fields that
  intentionally change; new listen_hotfix_test.go covers the
  listenAddress cases and the resourceForNode/exit deploy chains.
This commit is contained in:
aaaamoooo
2026-10-21 07:16:38 +00:00
parent 79639ac338
commit aa2ee62d32
3 changed files with 183 additions and 62 deletions
+3 -3
View File
@@ -12,7 +12,7 @@
{
"type": "vless",
"tag": "ng-nodrf-in",
"listen": "203.0.113.10",
"listen": "0.0.0.0",
"listen_port": 23456,
"users": [
{
@@ -76,7 +76,7 @@
{
"type": "shadowsocks",
"tag": "ng-nodrf-exit-in",
"listen": "203.0.113.20",
"listen": "0.0.0.0",
"listen_port": 23457,
"method": "2022-blake3-aes-256-gcm",
"password": "AwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISI="
@@ -111,7 +111,7 @@
{
"type": "shadowsocks",
"tag": "ng-nodss-in",
"listen": "203.0.113.11",
"listen": "0.0.0.0",
"listen_port": 23458,
"method": "2022-blake3-aes-128-gcm",
"password": "CwwNDg8QERITFBUWFxgZGg==",