[GH-ISSUE #955] 连接前检测地址是否可用功能,可以在纯 IPV6 域名或双栈模式下测试 #1737

Closed
opened 2026-02-28 12:06:21 +03:00 by kerem · 3 comments
Owner

Originally created by @zhangzuwei on GitHub (Jul 10, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/955

Originally assigned to: @VShawn on GitHub.

Is your enhancement related to a problem? Please describe.
远程连接 IPV6 的 RDP主机时,如果不关闭“连接前检测地址是否可用”,直接连接右下角提示连接检查不通过,但实际是可以正常通过 IPV6 解析地址连接的。

Describe the solution you'd like
针对连接属性里的 “连接前检测地址是否可用” 这个选项能够同时支持纯 IPV6 以及 IPV4 和 IPV6 双栈域名解析和测试

Describe alternatives you've considered
针对这种纯 IPV6 DDNS 域名,关闭“连接前检测地址是否可用”选项直接连接即可

Additional context
贴心的一个小功能,希望能完善一下 IPV6 的测试场景,谢谢。

Image
Originally created by @zhangzuwei on GitHub (Jul 10, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/955 Originally assigned to: @VShawn on GitHub. **Is your enhancement related to a problem? Please describe.** 远程连接 IPV6 的 RDP主机时,如果不关闭“连接前检测地址是否可用”,直接连接右下角提示连接检查不通过,但实际是可以正常通过 IPV6 解析地址连接的。 **Describe the solution you'd like** 针对连接属性里的 “连接前检测地址是否可用” 这个选项能够同时支持纯 IPV6 以及 IPV4 和 IPV6 双栈域名解析和测试 **Describe alternatives you've considered** 针对这种纯 IPV6 DDNS 域名,关闭“连接前检测地址是否可用”选项直接连接即可 **Additional context** 贴心的一个小功能,希望能完善一下 IPV6 的测试场景,谢谢。 <img width="1174" height="1333" alt="Image" src="https://github.com/user-attachments/assets/4f22cf28-d78d-43f7-97ca-e9b2c08222e9" />
kerem 2026-02-28 12:06:21 +03:00
Author
Owner

@VShawn commented on GitHub (Jul 12, 2025):

希望能给有人能帮完善这个功能,我没有能完善它的唯一原因是,我自己没有IPV6环境,无法测试这个功能的好坏。

<!-- gh-comment-id:3064777309 --> @VShawn commented on GitHub (Jul 12, 2025): 希望能给有人能帮完善这个功能,我没有能完善它的唯一原因是,我自己没有IPV6环境,无法测试这个功能的好坏。
Author
Owner

@github-actions[bot] commented on GitHub (Aug 12, 2025):

This issue is stale because it has been open for 30 days with no activity.

<!-- gh-comment-id:3177459909 --> @github-actions[bot] commented on GitHub (Aug 12, 2025): This issue is stale because it has been open for 30 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Aug 27, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

<!-- gh-comment-id:3226495383 --> @github-actions[bot] commented on GitHub (Aug 27, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/1Remote#1737
No description provided.