R2S启用OpenClash 后无法使用

R2S，固件使用https://github.com/DHDAXCW/NanoPi-R2S-2021 表现为，如果不开OpenClash，则使用非常正常，运行很久也不会出问题。但一旦开启了OpenClash 后，一段时间（大概几个小时），R2S ####[直接挂掉，DHCP无法获取地址，即使重启后也只能一闪而过进入后台，然后继续死机。是否是其他帖子所说连接数耗尽，没有注意。

之前使用是正常的，大概是在更新了0.43.2或者0.43.3左右出现的问题，之前一直非常稳定。

配置文件如下：

# Port of HTTP(S) proxy server on the local end
# port: 7890

# Port of SOCKS5 proxy server on the local end
# socks-port: 7891

# Transparent proxy server port for Linux and macOS (Redirect TCP and TProxy UDP)
# redir-port: 7892

# Transparent proxy server port for Linux (TProxy TCP and TProxy UDP)
# tproxy-port: 7893

# HTTP(S) and SOCKS5 server on the same port

mixed-port: 1081

# authentication of local SOCKS5/HTTP(S) server
# authentication:
#  - "user1:pass1"
#  - "user2:pass2"

# Set to true to allow connections to the local-end server from
# other LAN IP addresses
allow-lan: false

# This is only applicable when `allow-lan` is `true`
# '*': bind all IP addresses
# 192.168.122.11: bind a single IPv4 address
# "[aaaa::a8aa:ff:fe09:57d8]": bind a single IPv6 address
bind-address: '*'

# Clash router working mode
# rule: rule-based packet routing
# global: all packets will be forwarded to a single endpoint
# direct: directly forward the packets to the Internet
mode: rule

# Clash by default prints logs to STDOUT
# info / warning / error / debug / silent
log-level: info

# When set to false, resolver won't translate hostnames to IPv6 addresses
ipv6: false

# RESTful web API listening address
external-controller: 127.0.0.1:9090

# A relative path to the configuration directory or an absolute path to a
# directory in which you put some static web resource. Clash core will then
# serve it at `http://{{external-controller}}/ui`.
# external-ui: folder

# Secret for the RESTful API (optional)
# Authenticate by spedifying HTTP header `Authorization: Bearer ${secret}`
# ALWAYS set a secret if RESTful API is listening on 0.0.0.0
# secret: ""

# Outbound interface name
#interface-name: en0

# Static hosts for DNS server and connection establishment (like /etc/hosts)
#
# Wildcard hostnames are supported (e.g. *.clash.dev, *.foo.*.example.com)
# Non-wildcard domain names have a higher priority than wildcard domain names
# e.g. foo.example.com > *.example.com > .example.com
# P.S. +.foo.com equals to .foo.com and foo.com
hosts:
  # '*.clash.dev': 127.0.0.1
  # '.dev': 127.0.0.1
  # 'alpha.clash.dev': '::1'

# DNS server settings
# This section is optional. When not present, the DNS server will be disabled.
dns:
#  enable: false
#  listen: 0.0.0.0:53
#  # ipv6: false # when the false, response to AAAA questions will be empty

  # These nameservers are used to resolve the DNS nameserver hostnames below.
  # Specify IP addresses only
  default-nameserver:
    - 119.29.29.29
    - 114.114.114.114
    - 8.8.8.8
  # enhanced-mode: redir-host # or fake-ip
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16 # Fake IP addresses pool CIDR
  # use-hosts: true # lookup hosts and return IP record

  # Hostnames in this list will not be resolved with fake IPs
  # i.e. questions to these domain names will always be answered with their
  # real IP addresses
  # fake-ip-filter:
    # - '*.lan'
    # - localhost.ptlogin2.qq.com

  # Supports UDP, TCP, DoT, DoH. You can specify the port to connect to.
  # All DNS questions are sent directly to the nameserver, without proxies
  # involved. Clash answers the DNS question with the first result gathered.
  nameserver:
    - 114.114.114.114 # default value
    - 8.8.8.8 # default value
    - tls://dns.rubyfish.cn:853 # DNS over TLS
    - https://1.1.1.1/dns-query # DNS over HTTPS

  # When `fallback` is present, the DNS server will send concurrent requests
  # to the servers in this section along with servers in `nameservers`.
  # The answers from fallback servers are used when the GEOIP country
  # is not `CN`.
  # fallback:
  #   - tcp://1.1.1.1

  # If IP addresses resolved with servers in `nameservers` are in the specified
  # subnets below, they are considered invalid and results from `fallback`
  # servers are used instead.
  #
  # IP address resolved with servers in `nameserver` is used when
  # `fallback-filter.geoip` is true and when GEOIP of the IP address is `CN`.
  #
  # If `fallback-filter.geoip` is false, results from `nameserver` nameservers
  # are always used if not match `fallback-filter.ipcidr`.
  #
  # This is a countermeasure against DNS pollution attacks.
  fallback-filter:
    geoip: true
    ipcidr:
      - 240.0.0.0/4
    # domain:
    #   - '+.google.com'
    #   - '+.facebook.com'
    #   - '+.youtube.com'
proxies:
  - name: aaaaa
  - name: bbbbb

proxy-providers:
  Potato_Full:
  Potato_JKTS:
  Potato_HK:
  Potato_US:
  Potato_5x:
  Potato_stream:

proxy-groups:
  - name: FastProxy
  - name: HappyProxy
  - name: MySELF
  - name: FastFinal
  - name: Apple
  - name: Google

rules:
  - DOMAIN-SUFFIX, v2ex.com, REJECT ## 实在受不了这个傻逼网站了
  - RULE-SET, must-go-by-self-proxy, MySELF
  - RULE-SET, reject, REJECT
  - RULE-SET, anti-ad, REJECT
  - RULE-SET, direct, DIRECT
  - RULE-SET, lancidr, DIRECT
  - RULE-SET, private, DIRECT
  - RULE-SET, cncidr, DIRECT
  - RULE-SET, icloud, Apple
  - RULE-SET, apple, Apple
  - RULE-SET, google, Google
  - RULE-SET,gfw,FastProxy
  - RULE-SET,greatfire,FastProxy
  - RULE-SET,proxy,FastProxy
  - RULE-SET,telegramcidr,FastProxy
  - RULE-SET,tld-not-cn,FastProxy
  - GEOIP, CN, DIRECT, no-resolve
  - MATCH, MySELF
rule-providers:
  must-go-by-self-proxy:
  youtube:
  twitter:
  instagram:
  anti-ad:
  reject:
  icloud:
  apple:
  google:
  proxy:
  direct:
  private:
  gfw:
  greatfire:
  tld-not-cn:
  telegramcidr:
  cncidr:
  lancidr:

vernesong / OpenClash

R2S启用OpenClash 后无法使用 #1614