
config homeproxy-pro 'infra'
	option __warning 'DO NOT EDIT THIS SECTION, OR YOU ARE ON YOUR OWN!'
	option common_port '22,53,80,143,443,465,587,853,873,993,995,5222,8080,8443,9418'
	option mixed_port '5330'
	option redirect_port '5331'
	option tproxy_port '5332'
	option dns_port '5333'
	option dns_redirect '1'
	option ntp_server 'nil'
	option udp_timeout ''
	option tun_name 'singtun0'
	option tun_addr4 '172.19.0.1/30'
	option tun_addr6 'fdfe:dcba:9876::1/126'
	option tun_mtu '9000'
	option table_mark '100'
	option self_mark '100'
	option tproxy_mark '101'
	option tun_mark '102'

config homeproxy-pro 'migration'
	option crontab '1'

config homeproxy-pro 'config'
	option main_node 'nil'
	option main_udp_node 'same'
	option dns_server '8.8.8.8'
	option china_dns_server '223.5.5.5'
	option routing_mode 'bypass_mainland_china'
	option routing_port 'common'
	option proxy_mode 'redirect_tproxy'
	option ipv6_support '1'
	option github_token ''
	option log_level 'warn'
	# Functional health probes (runtime/health.sh). They run after the
	# process/listener gate and only log by default: a probe can fail because
	# the uplink is down or a captive portal answers, and rolling a good
	# configuration back for that would be worse than the condition probed
	# for. Set health_probe_strict to 1 only if a failing probe must fail the
	# start (and therefore trigger the rollback).
	option health_probe_strict '0'
	option health_probe_name 'example.com'
	option cn_ip_fallback '1'
	option sniffer_advanced_mode '0'
	# Start the client even when a remote rule-set cannot be downloaded.
	#
	# Off by default, and the default has to stay off: the mechanism points a
	# remote rule-set at an EMPTY rule-set so that sing-box starts immediately
	# instead of fetching during initialization, before the inbounds bind.  An
	# empty rule-set matches nothing, so everything it would have split falls
	# through to `final` - that is a routing change, not just a robustness
	# tweak, and on bypass_mainland_china it means mainland destinations can be
	# proxied until the download succeeds.
	#
	# With it off, a cold cache on a fresh install waits for
	# raw.githubusercontent.com (through the selected node) before the instance
	# will listen at all, and a failure there fails the whole start.
	option tun_dns_mode ''
	option udp_mapping ''
	option udp_filtering ''
	option udp_nat_max ''

config homeproxy-pro 'control'
	option lan_proxy_mode 'disabled'
	list wan_proxy_ipv4_ips '91.105.192.0/23'
	list wan_proxy_ipv4_ips '91.108.4.0/22'
	list wan_proxy_ipv4_ips '91.108.8.0/22'
	list wan_proxy_ipv4_ips '91.108.16.0/22'
	list wan_proxy_ipv4_ips '91.108.12.0/22'
	list wan_proxy_ipv4_ips '91.108.20.0/22'
	list wan_proxy_ipv4_ips '91.108.56.0/22'
	list wan_proxy_ipv4_ips '149.154.160.0/20'
	list wan_proxy_ipv4_ips '185.76.151.0/24'
	list wan_proxy_ipv4_ips '203.208.50.66/32'
	list wan_proxy_ipv6_ips '2001:67c:4e8::/48'
	list wan_proxy_ipv6_ips '2001:b28:f23c::/48'
	list wan_proxy_ipv6_ips '2001:b28:f23d::/48'
	list wan_proxy_ipv6_ips '2001:b28:f23f::/48'
	list wan_proxy_ipv6_ips '2a0a:f280::/32'

config homeproxy-pro 'routing'
	option default_outbound 'direct-out'
	option default_outbound_dns 'default-dns'
	option find_neighbor '0'

config homeproxy-pro 'dns'
	option default_strategy 'prefer_ipv4'
	option default_server 'default-dns'
	option disable_cache '0'
	option disable_cache_expire '0'
	option optimistic_cache '0'
	option optimistic_timeout ''
	option dns_timeout ''
	option cache_file_store_dns '0'

config homeproxy-pro 'subscription'
	option auto_update '0'
	option allow_insecure '0'
	option packet_encoding 'xudp'
	option update_via_proxy '0'
	option filter_nodes 'blacklist'
	list filter_keywords '重置|到期|过期|剩余|套餐'
	list filter_keywords 'Expiration|Remaining'

config homeproxy-pro 'server'
	option enabled '0'
	option log_level 'warn'
