Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3258) is ready to test on iOS.
What to Test:
- 修正如果开启了始终开启功能，通过小组件开启时未能正确生效的问题
（该版本使用 iOS 17 SDK 编译，不支持控制中心插件）
5.11.3 RC1
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3258) is ready to test on iOS.
What to Test:
- 修正如果开启了始终开启功能，通过小组件开启时未能正确生效的问题
（该版本使用 iOS 17 SDK 编译，不支持控制中心插件）
5.11.3 RC1
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
⚠️版本回撤‼️
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
⚠️版本回撤‼️
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from 雪之下雪乃 (xzxxn)
#MengNiu #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本
蒙牛营养生活家每日签到
使用方法：进入微信小程序 蒙牛营养生活家-中间的每日签到 获取token
蒙牛生活家会员中心每日任务（签到用有赞通用脚本）
使用方法：进入微信小程序 蒙牛生活家会员中心 获取token
🤩 脚本作者：@xzxxn7
✅ 模块地址：点击链接
❗️只测试了surge，其他代理软件请使用Script Hub转换
👥 频道 💬 群聊
蒙牛营养生活家每日签到
使用方法：进入微信小程序 蒙牛营养生活家-中间的每日签到 获取token
蒙牛生活家会员中心每日任务（签到用有赞通用脚本）
使用方法：进入微信小程序 蒙牛生活家会员中心 获取token
❗️只测试了surge，其他代理软件请使用Script Hub转换
Please open Telegram to view this post
VIEW IN TELEGRAM
GitHub
Home
Advanced Script Converter for QX, Loon, Surge, Stash, Egern, LanceX and Shadowrocket - 重写 & 规则集转换 - Script-Hub-Org/Script-Hub
Forwarded from 雪之下雪乃 (xzxxn)
#HGDS #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本
哈根达斯会员中心每日签到
使用方法：进入微信小程序-哈根达斯会员中心 获取token
🤩 脚本作者：@xzxxn7
✅ 模块地址： 点击链接
❗️只测试了surge，其他代理软件请使用Script Hub转换
哈根达斯会员中心每日签到
使用方法：进入微信小程序-哈根达斯会员中心 获取token
❗️只测试了surge，其他代理软件请使用Script Hub转换
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from Surge's Changelog
#iOS #AppStore
Version 5.11.3
Release Date: 2024/6/15 01:53:14(UTC+08:00)
What’s New:
- Support turning off Surge via widgets/Shortcuts when the always-on switch is turned on.
- Support turning on Surge via widgets/Shortcuts when the Surge VPN Profile is not selected (or when other VPNs are running).
- Fix an issue where DOMAIN-SUFFIX rules may become invalid if duplicate DOMAIN and DOMAIN-SUFFIX rules are included in the rule set.
- Optimizations related to No Default Route mode, significantly improving usability.
- Other bug fixes.
Official Channel: @SurgeTestFlightFeed
Version 5.11.3
Release Date: 2024/6/15 01:53:14(UTC+08:00)
What’s New:
- Support turning off Surge via widgets/Shortcuts when the always-on switch is turned on.
- Support turning on Surge via widgets/Shortcuts when the Surge VPN Profile is not selected (or when other VPNs are running).
- Fix an issue where DOMAIN-SUFFIX rules may become invalid if duplicate DOMAIN and DOMAIN-SUFFIX rules are included in the rule set.
- Optimizations related to No Default Route mode, significantly improving usability.
- Other bug fixes.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2793
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2793
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
⚠️版本回撤‼️
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
⚠️版本回撤‼️
Version 5.7.4-2792
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2793
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2793
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2794
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2794
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#tvOS #TestFlight
Surge 5 5.100.0 (3262) is ready to test on tvOS.
What to Test:
- 同步 iOS 版本更新
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3262) is ready to test on tvOS.
What to Test:
- 同步 iOS 版本更新
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2795
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2795
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3263) is ready to test on iOS.
What to Test:
- 模块支持配置 client-source-address 参数
- 修正导出 HAR 时的一些问题
- 使用 iOS 18 SDK 编译，包含控制中心开关
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3263) is ready to test on iOS.
What to Test:
- 模块支持配置 client-source-address 参数
- 修正导出 HAR 时的一些问题
- 使用 iOS 18 SDK 编译，包含控制中心开关
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2796
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2796
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2799
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2799
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2800
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2800
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2801
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2801
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2802
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2802
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2803
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2803
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2804
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2804
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed