Enhanced Connection Control In Clash Nyanpasu: A Feature Request

by Henrik Larsen 65 views

Hey guys! Today, we're diving deep into a feature request for Clash Nyanpasu that's all about giving you more control over how connections are interrupted. This is a super important topic because, let's be honest, nobody likes it when their connection drops unexpectedly. This proposal aims to make those drops less frequent and more predictable.

需求 / Requirement

The current implementation of connection interruption in Clash Nyanpasu is triggered mainly when switching Profiles or Modes. While that's helpful, it doesn't quite cover all the bases. Think about it: most of the time, when you're switching between proxies within a proxy group, you'd also want to sever those old connections tied to the previous proxy. This ensures a clean break and prevents potential issues arising from lingering connections.

The main keyword here is connection interruption. Currently, Clash Nyanpasu only interrupts connections when switching profiles or modes. This feature request proposes extending this functionality to include proxy switching within proxy groups. This is important for maintaining a clean and reliable connection experience. The user experience is significantly impacted by how smoothly these transitions occur. Imagine you're streaming a video, and the connection suddenly drops because you switched proxies. That's frustrating, right? By implementing more granular control over connection interruption, we can minimize these disruptions and keep your online experience smooth and seamless.

打断连接的时机和影响

To really understand the impact, let's break down why interrupting connections is crucial. When you switch proxies, the old connection might still be trying to send or receive data through the previous proxy server. This can lead to various problems, including:

  • Slowdowns: Data might be routed inefficiently, leading to slower speeds.
  • Errors: Incomplete data transfers can cause errors and application instability.
  • Security risks: Leftover connections might expose you to security vulnerabilities.

Therefore, a well-managed connection interruption mechanism is vital for performance, stability, and security. By intelligently cutting off old connections, we ensure that your traffic flows exclusively through the new proxy, preventing any interference from the past.

切换场景下的连接问题

Think of different scenarios where proxy switching occurs. You might be using a proxy group with automatic failover, where Clash Nyanpasu switches to a different proxy if the current one becomes unavailable. Or, you might be manually selecting a different proxy based on your needs. In both cases, ensuring a clean connection switch is crucial.

When a proxy is switched due to failover, you definitely don't want the old connection to linger and cause issues. The goal is to seamlessly transition to the new proxy without any hiccups. Similarly, when you manually switch proxies, you expect the change to take effect immediately, without any remnants of the old connection interfering.

  • Automation: The system should automatically handle connection interruptions when proxies are switched, reducing manual intervention.
  • User control: Users should have the option to customize the interruption behavior to suit their specific needs.
  • Transparency: The system should provide clear feedback about when and why connections are being interrupted.

建议实现 / Suggested implements

The user suggests implementing more fine-grained control over connection interruption, drawing inspiration from CFW (Clash for Windows). Here's a breakdown of the suggested features:

Break When Proxy Change

This is the core of the feature request, guys. It's all about controlling what happens when you switch proxies within a proxy group. The suggested options are:

  • None: (Default) No connection interruption occurs.
  • Chain: Interrupts connections that include the specific proxy group in their chain. This is a smart approach because it targets only the relevant connections, minimizing disruption.
  • All: Interrupts all connections. This is the most aggressive option and should be used with caution, but it can be helpful in certain situations where a complete reset is necessary.

The key suggestion here is to implement different levels of connection interruption when switching proxies. The "Chain" option is particularly interesting as it offers a targeted approach, only interrupting connections that are actually using the proxy group in question. This targeted approach is crucial for minimizing disruption. Imagine you're downloading a large file through one proxy while browsing the web through another. If you switch proxies in your main browsing proxy group, you wouldn't want your download to be interrupted. The "Chain" option allows for this level of granularity.

优化连接中断方案

The user's suggestion to implement different levels of connection interruption is a game-changer. The "Chain" option, specifically, is a brilliant idea. By only interrupting connections that are using the proxy group you're switching within, you can avoid unnecessary disruptions to other connections.

Think about it: you might be using one proxy for streaming videos, another for general browsing, and yet another for downloading files. If you switch proxies for your general browsing, you wouldn't want your video stream or your file download to be interrupted. The "Chain" option makes this possible.

  • Flexibility: Different levels of interruption provide flexibility for different use cases.
  • Efficiency: Targeted interruption minimizes unnecessary disruption.
  • User control: Users can choose the level of interruption that best suits their needs.

Break When Profile Change

  • 开 (On): Interrupts all connections before switching profiles. This ensures a clean slate and prevents conflicts between different profile configurations.
  • 关 (Off): No interruption occurs. This might be useful if you want to maintain existing connections across profile switches, but it's generally recommended to enable this option for stability.

Break When Mode Change

  • 开 (On): Interrupts all connections when switching proxy modes (e.g., Global, Rule, Direct). Similar to profile switching, this ensures a clean transition and prevents routing inconsistencies.
  • 关 (Off): No interruption occurs. Again, this is generally not recommended as it can lead to unexpected behavior.

参考 CFW 实现

The user points to the CFW (Clash for Windows) documentation as a valuable reference. The linked document (https://web.archive.org/web/20230319100701/https://docs.cfw.lbyczf.com/contents/breakconn.html) provides a detailed explanation of CFW's connection interruption features, which can serve as a solid foundation for implementing similar functionality in Clash Nyanpasu.

The user specifically suggests referencing the CFW implementation of connection interruption. This is a great suggestion as CFW has a well-established and effective system for managing connections. CFW's approach provides a proven model for how to handle different levels of interruption and how to integrate these settings into the user interface. By drawing inspiration from CFW, Clash Nyanpasu can leverage existing best practices and avoid reinventing the wheel.

CFW 连接中断的优势

CFW's implementation of connection interruption is known for its reliability and flexibility. It offers a range of options that allow users to fine-tune the behavior of the system to their specific needs. This includes:

  • Granular control: Users can choose when and how connections are interrupted.
  • Stability: The system is designed to minimize disruptions and ensure a smooth user experience.
  • Integration: The settings are well-integrated into the CFW interface, making them easy to access and configure.

By adopting a similar approach, Clash Nyanpasu can benefit from these advantages and provide its users with a more robust and user-friendly experience.

备注 / Addition details

No response

Clash Nyanpasu 版本号 / Clash Nyanpasu

v2.0.0

是否为 Pre-release / Is pre-release version

ba2c767

自查步骤 / Verify steps

  • [ ] 如果您有足够的时间和能力，并愿意为此提交 PR，请勾上此复选框 / Pull request is welcome. Check this if you want to start a pull request
  • [x] 您已仔细查看并知情 Q&A 中的内容 / You have checked Q&A carefully
  • [x] 您已搜索过 Issue Tracker，没有找到类似内容 / I have searched on Issue Tracker, No duplicate or related open issue has been found
  • [x] 您确保这个 Issue 只提及一个功能。如果您有多个功能请求，烦请发起多个 Issue / Ensure there is only one feature request in this issue. Please make multiply issue for multiply feature request
  • [x] 您确保已使用最新 Pre-release 版本测试，并且该功能在最新 Pre-release 版本中并未实现 / This feature have not implemented in latest Pre-release version