1.11.0-alpha.16

📝 Release Notes

• Add cache_capacity DNS option 1
• Add override_address and override_port route options 2
• Fixes and improvements

1:

See DNS.

2:

See Rule Action and Migrate destination override fields to route options.

1.11.0-alpha.15

📝 Release Notes

• Improve multi network dialing 1
• Fixes and improvements

1:

New options allow you to configure the network strategy flexibly.

See Dial Fields, Rule Action and Route.

https://github.com/SagerNet/sing-box/releases/tag/v1.11.0-alpha.15

1.11.0-alpha.14

📝 Release Notes

• Add multi network dialing 1
• Fixes and improvements

1:

Similar to Surge's strategy.

New options allow you to connect using multiple network interfaces,
prefer or only use one type of interface,
and configure a timeout to fallback to other interfaces.

See Dial Fields, Rule Action and Route.

1.11.0-alpha.13

📝 Release Notes

• Fixes and improvements

1.11.0-alpha.12

📝 Release Notes

• Merge route options to route actions 1
• Add network_type, network_is_expensive and network_is_constrainted rule items 2
• Fixes and improvements

1:

Route options in DNS route actions will no longer be considered deprecated, see DNS Route Action.

Also, now udp_disable_domain_unmapping and udp_connect can also be configured in route action, see Route Action.

2:

When using in graphical clients, new routing rule items allow you to match on network type (WIFI, cellular, etc.), whether the network is expensive, and whether Low Data Mode is enabled.

See Route Rule, DNS Route Rule and Headless Rule.

1.11.0-alpha.11

📝 Release Notes

• Fixes and improvements

1.11.0-alpha.10

📝 Release Notes

• Fixes and improvements

1.11.0-alpha.9

📝 Release Notes

• Improve tun compatibility 1
• Fixes and improvements

1:

When gvisor tun stack is enabled, even if the request passes routing, if the outbound connection establishment fails, the connection still does not need to be established and a TCP RST is replied.

1.11.0-alpha.8

📝 Release Notes

• Fixes and improvements

1.11.0-alpha.7

📝 Release Notes

• Introducing rule actions 1

1:

New rule actions replace legacy inbound fields and special outbound fields, and can be used for pre-matching 2.

See Rule, Rule Action, DNS Rule and DNS Rule Action.

For migration, see Migrate legacy special outbounds to rule actions, Migrate legacy inbound fields to rule actions and Migrate legacy DNS route options to rule actions.

2:

Similar to Surge's pre-matching.

Specifically, the new rule actions allow you to reject connections with TCP RST (for TCP connections) and ICMP port unreachable (for UDP packets) before connection established to improve tun's compatibility.

See Rule Action.