Trouver du contenu similaire

#Mac#Beta Version 6.4.1-9370 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9360 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9350 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9340 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9330 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9320 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.1-9310 - Improved the stability of the UDP Fast Path, preventing previous UDP connections from being affected by fast path fallback. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.0-9300 ### Surge Gateway VM UDP Fast Path - Currently, when using Surge in gateway mode to take over a device, if P2P applications (such as BT downloads, game installers, live streaming, etc.) are used on the device, it may result in a large number of connections appearing in the Dashboard, slowing down overall speed. If the number of connections is extremely high, it may even exhaust system resources and force Surge to restart. - The cause of this issue is that Surge operates as a layer 4 proxy, and for every UDP packet with a different quadruple, it needs to be handled as a new connection. For most applications, even if UDP is used, only a few logical connections are typically generated, so the overhead is completely acceptable. However, for P2P applications, nearly a thousand logical connections may be generated within a few seconds. - Therefore, this version introduces a UDP Fast Path defense mechanism. When a client initiates a large number of UDP connections in a short period of time (10 within 1 second or 30 within 10 seconds), UDP Fast Path will be enabled for that client, downgrading UDP packet processing to L3. In this mode, performance is extremely high, far exceeding the physical network card speed limit, so there is no longer a need to worry about resource consumption issues. Additionally: - Packets under UDP Fast Path will be forwarded directly and cannot go through the proxy. - For UDP packets with a destination port number less than 1024, they will always be forwarded using the normal processing mode to avoid affecting regular applications. ### Bug Fixes - Fix the issue where the HTTP engine might get stuck when handling consecutive requests. - Fixed the issue where using Snell v3 to carry UDP traffic could cause a crash. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.0-9280 ### Surge Gateway VM UDP Fast Path - Currently, when using Surge in gateway mode to take over a device, if P2P applications (such as BT downloads, game installers, live streaming, etc.) are used on the device, it may result in a large number of connections appearing in the Dashboard, slowing down overall speed. If the number of connections is extremely high, it may even exhaust system resources and force Surge to restart. - The cause of this issue is that Surge operates as a layer 4 proxy, and for every UDP packet with a different quadruple, it needs to be handled as a new connection. For most applications, even if UDP is used, only a few logical connections are typically generated, so the overhead is completely acceptable. However, for P2P applications, nearly a thousand logical connections may be generated within a few seconds. - Therefore, this version introduces a UDP Fast Path defense mechanism. When a client initiates a large number of UDP connections in a short period of time (10 within 1 second or 30 within 10 seconds), UDP Fast Path will be enabled for that client, downgrading UDP packet processing to L3. In this mode, performance is extremely high, far exceeding the physical network card speed limit, so there is no longer a need to worry about resource consumption issues. Additionally: - Packets under UDP Fast Path will be forwarded directly and cannot go through the proxy. - For UDP packets with a destination port number less than 1024, they will always be forwarded using the normal processing mode to avoid affecting regular applications. ### Bug Fixes - Fix the issue where the HTTP engine might get stuck when handling consecutive requests. - Fixed the issue where using Snell v3 to carry UDP traffic could cause a crash. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.0-9270 ### Surge Gateway VM UDP Fast Path - Currently, when using Surge in gateway mode to take over a device, if P2P applications (such as BT downloads, game installers, live streaming, etc.) are used on the device, it may result in a large number of connections appearing in the Dashboard, slowing down overall speed. If the number of connections is extremely high, it may even exhaust system resources and force Surge to restart. - The cause of this issue is that Surge operates as a layer 4 proxy, and for every UDP packet with a different quadruple, it needs to be handled as a new connection. For most applications, even if UDP is used, only a few logical connections are typically generated, so the overhead is completely acceptable. However, for P2P applications, nearly a thousand logical connections may be generated within a few seconds. - Therefore, this version introduces a UDP Fast Path defense mechanism. When a client initiates a large number of UDP connections in a short period of time (10 within 1 second or 30 within 10 seconds), UDP Fast Path will be enabled for that client, downgrading UDP packet processing to L3. In this mode, performance is extremely high, far exceeding the physical network card speed limit, so there is no longer a need to worry about resource consumption issues. Additionally: - Packets under UDP Fast Path will be forwarded directly and cannot go through the proxy. - For UDP packets with a destination port number less than 1024, they will always be forwarded using the normal processing mode to avoid affecting regular applications. ### Bug Fixes - Fix the issue where the HTTP engine might get stuck when handling consecutive requests. - Fixed the issue where using Snell v3 to carry UDP traffic could cause a crash. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.0-9260 ### Surge Gateway VM UDP Fast Path - Currently, when using Surge in gateway mode to take over a device, if P2P applications (such as BT downloads, game installers, live streaming, etc.) are used on the device, it may result in a large number of connections appearing in the Dashboard, slowing down overall speed. If the number of connections is extremely high, it may even exhaust system resources and force Surge to restart. - The cause of this issue is that Surge operates as a layer 4 proxy, and for every UDP packet with a different quadruple, it needs to be handled as a new connection. For most applications, even if UDP is used, only a few logical connections are typically generated, so the overhead is completely acceptable. However, for P2P applications, nearly a thousand logical connections may be generated within a few seconds. - Therefore, this version introduces a UDP Fast Path defense mechanism. When a client initiates a large number of UDP connections in a short period of time (10 within 1 second or 30 within 10 seconds), UDP Fast Path will be enabled for that client, downgrading UDP packet processing to L3. In this mode, performance is extremely high, far exceeding the physical network card speed limit, so there is no longer a need to worry about resource consumption issues. Additionally: - Packets under UDP Fast Path will be forwarded directly and cannot go through the proxy. - For UDP packets with a destination port number less than 1024, they will always be forwarded using the normal processing mode to avoid affecting regular applications. ### Bug Fixes - Fix the issue where the HTTP engine might get stuck when handling consecutive requests. - Fixed the issue where using Snell v3 to carry UDP traffic could cause a crash. Official Channel: @SurgeTestFlightFeed

#Mac#Beta Version 6.4.0-9250 ### Surge Gateway VM UDP Fast Path - Currently, when using Surge in gateway mode to take over a device, if P2P applications (such as BT downloads, game installers, live streaming, etc.) are used on the device, it may result in a large number of connections appearing in the Dashboard, slowing down overall speed. If the number of connections is extremely high, it may even exhaust system resources and force Surge to restart. - The cause of this issue is that Surge operates as a layer 4 proxy, and for every UDP packet with a different quadruple, it needs to be handled as a new connection. For most applications, even if UDP is used, only a few logical connections are typically generated, so the overhead is completely acceptable. However, for P2P applications, nearly a thousand logical connections may be generated within a few seconds. - Therefore, this version introduces a UDP Fast Path defense mechanism. When a client initiates a large number of UDP connections in a short period of time (10 within 1 second or 30 within 10 seconds), UDP Fast Path will be enabled for that client, downgrading UDP packet processing to L3. In this mode, performance is extremely high, far exceeding the physical network card speed limit, so there is no longer a need to worry about resource consumption issues. Additionally: - Packets under UDP Fast Path will be forwarded directly and cannot go through the proxy. - For UDP packets with a destination port number less than 1024, they will always be forwarded using the normal processing mode to avoid affecting regular applications. ### Bug Fixes - Fix the issue where the HTTP engine might get stuck when handling consecutive requests. - Fixed the issue where using Snell v3 to carry UDP traffic could cause a crash. Official Channel: @SurgeTestFlightFeed