Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 配置tunnels或relay的落地节点经常无法ping通 #98

Closed
stimw opened this issue Dec 11, 2023 · 3 comments
Closed

[BUG] 配置tunnels或relay的落地节点经常无法ping通 #98

stimw opened this issue Dec 11, 2023 · 3 comments

Comments

@stimw
Copy link

stimw commented Dec 11, 2023

Describe the bug

  • 配置tunnels或relay的落地节点经常无法ping通,见下面截图和配置文件
  • 虽然显示无法ping通但是可以正常使用,并且机场节点没有出现这个问题

以上问题在clash verge rev中,使用同一配置文件,没有复现。(已关闭clash过滤字段)

To Reproduce
可以尝试确认任意tunnels或relay配置能否总是正常ping通

Expected behavior
正常ping通

Screenshots
image

Information

  • OS: macOS
  • Clash Nyanpasu Version: 1.4.1
  • Clash Core: Clash Meta

Additional context

Simple Config:

port: 7890
socks-port: 7891
allow-lan: true
mode: Rule
log-level: info
external-controller: :9090
tunnels:
  - network: [tcp, udp]
    address: 127.0.0.1:7777
    target:  # 手动打码
    proxy: Kuromi
proxies:
  - name: 'singapore-ss'
    type: ss
    server: 127.0.0.1
    port: 7777
    cipher: # 手动打码
    password:  # 手动打码
proxy-providers:
  Jichang:
    type: http
    url:  # 手动打码
    path: ./Proxy/Jichang.yml
    interval: 86400
    health-check:
      enable: false
      interval: 600
      url: https://www.gstatic.com/generate_204
proxy-groups:
  - name: 🚀 节点选择
    type: select
    proxies:
      - singapore-ss
      - DIRECT
  - name: Kuromi
    type: select
    use:
      - Jichang

Information

  • OS: macOS
  • Clash Nyanpasu Version: 1.4.1
  • Clash Core: Clash Meta
@greenhat616
Copy link
Collaborator

能补充一下日记吗,在设置里面有个日记目录。我需要 nyanpasu 相关的日记。

@greenhat616
Copy link
Collaborator

zzzgydi/clash-verge@5a0fed9
zzzgydi/clash-verge@7e3a85e

可能这两个 commit 有助于解决这个问题

@4o3F
Copy link
Collaborator

4o3F commented Apr 9, 2024

Fixed in #172

@4o3F 4o3F closed this as completed Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants