2023-11-09 17:04:08 +08:00
|
|
|
|
---
|
|
|
|
|
icon: material/delete-alert
|
|
|
|
|
---
|
|
|
|
|
|
2023-09-08 11:52:15 +08:00
|
|
|
|
# Deprecated Feature List
|
|
|
|
|
|
2024-11-06 19:02:55 +08:00
|
|
|
|
## 1.11.0
|
|
|
|
|
|
|
|
|
|
#### Legacy special outbounds
|
|
|
|
|
|
|
|
|
|
Legacy special outbounds (`block` / `dns`) are deprecated
|
|
|
|
|
and can be replaced by rule actions,
|
|
|
|
|
check [Migration](../migration/#migrate-legacy-special-outbounds-to-rule-actions).
|
|
|
|
|
|
|
|
|
|
Old fields will be removed in sing-box 1.13.0.
|
|
|
|
|
|
|
|
|
|
#### Legacy inbound fields
|
|
|
|
|
|
|
|
|
|
Legacy inbound fields (`inbound.<sniff/domain_strategy/...>` are deprecated
|
|
|
|
|
and can be replaced by rule actions,
|
|
|
|
|
check [Migration](../migration/#migrate-legacy-inbound-fields-to-rule-actions).
|
|
|
|
|
|
|
|
|
|
Old fields will be removed in sing-box 1.13.0.
|
|
|
|
|
|
2024-11-15 13:33:35 +08:00
|
|
|
|
#### Destination override fields in direct outbound
|
|
|
|
|
|
|
|
|
|
Destination override fields (`override_address` / `override_port`) in direct outbound are deprecated
|
|
|
|
|
and can be replaced by rule actions,
|
|
|
|
|
check [Migration](../migration/#migrate-destination-override-fields-to-route-options).
|
|
|
|
|
|
2024-06-07 16:08:07 +08:00
|
|
|
|
## 1.10.0
|
|
|
|
|
|
2024-06-07 15:55:21 +08:00
|
|
|
|
#### TUN address fields are merged
|
|
|
|
|
|
|
|
|
|
`inet4_address` and `inet6_address` are merged into `address`,
|
|
|
|
|
`inet4_route_address` and `inet6_route_address` are merged into `route_address`,
|
|
|
|
|
`inet4_route_exclude_address` and `inet6_route_exclude_address` are merged into `route_exclude_address`.
|
|
|
|
|
|
2024-11-06 19:02:55 +08:00
|
|
|
|
Old fields will be removed in sing-box 1.12.0.
|
2024-06-07 15:55:21 +08:00
|
|
|
|
|
2024-10-13 13:20:49 +08:00
|
|
|
|
#### Match source rule items are renamed
|
|
|
|
|
|
|
|
|
|
`rule_set_ipcidr_match_source` route and DNS rule items are renamed to
|
|
|
|
|
`rule_set_ip_cidr_match_source` and will be remove in sing-box 1.11.0.
|
|
|
|
|
|
2024-06-07 16:08:07 +08:00
|
|
|
|
#### Drop support for go1.18 and go1.19
|
|
|
|
|
|
|
|
|
|
Due to maintenance difficulties, sing-box 1.10.0 requires at least Go 1.20 to compile.
|
|
|
|
|
|
2023-12-03 14:53:22 +08:00
|
|
|
|
## 1.8.0
|
|
|
|
|
|
|
|
|
|
#### Cache file and related features in Clash API
|
|
|
|
|
|
|
|
|
|
`cache_file` and related features in Clash API is migrated to independent `cache_file` options,
|
|
|
|
|
check [Migration](/migration/#migrate-cache-file-from-clash-api-to-independent-options).
|
|
|
|
|
|
|
|
|
|
#### GeoIP
|
|
|
|
|
|
2024-11-06 19:02:55 +08:00
|
|
|
|
GeoIP is deprecated and will be removed in sing-box 1.12.0.
|
2023-12-03 14:53:22 +08:00
|
|
|
|
|
|
|
|
|
The maxmind GeoIP National Database, as an IP classification database,
|
|
|
|
|
is not entirely suitable for traffic bypassing,
|
|
|
|
|
and all existing implementations suffer from high memory usage and difficult management.
|
|
|
|
|
|
2024-06-26 00:45:10 +08:00
|
|
|
|
sing-box 1.8.0 introduces [rule-set](/configuration/rule-set/), which can completely replace GeoIP,
|
2023-12-03 14:53:22 +08:00
|
|
|
|
check [Migration](/migration/#migrate-geoip-to-rule-sets).
|
|
|
|
|
|
|
|
|
|
#### Geosite
|
|
|
|
|
|
2024-11-06 19:10:26 +08:00
|
|
|
|
Geosite is deprecated and will be removed in sing-box 1.12.0.
|
2023-12-03 14:53:22 +08:00
|
|
|
|
|
|
|
|
|
Geosite, the `domain-list-community` project maintained by V2Ray as an early traffic bypassing solution,
|
|
|
|
|
suffers from a number of problems, including lack of maintenance, inaccurate rules, and difficult management.
|
|
|
|
|
|
2024-06-26 00:45:10 +08:00
|
|
|
|
sing-box 1.8.0 introduces [rule-set](/configuration/rule-set/), which can completely replace Geosite,
|
2023-12-03 14:53:22 +08:00
|
|
|
|
check [Migration](/migration/#migrate-geosite-to-rule-sets).
|
|
|
|
|
|
|
|
|
|
## 1.6.0
|
2023-11-09 17:04:08 +08:00
|
|
|
|
|
2023-09-08 11:52:15 +08:00
|
|
|
|
The following features will be marked deprecated in 1.5.0 and removed entirely in 1.6.0.
|
|
|
|
|
|
|
|
|
|
#### ShadowsocksR
|
|
|
|
|
|
|
|
|
|
ShadowsocksR support has never been enabled by default, since the most commonly used proxy sales panel in the
|
|
|
|
|
illegal industry stopped using this protocol, it does not make sense to continue to maintain it.
|
|
|
|
|
|
|
|
|
|
#### Proxy Protocol
|
|
|
|
|
|
|
|
|
|
Proxy Protocol is added by Pull Request, has problems, is only used by the backend of HTTP multiplexers such as nginx,
|
|
|
|
|
is intrusive, and is meaningless for proxy purposes.
|