This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Very slow WLAN using SD-RED20 + wifi module (802.11 AC 2x2 wifi module (for 125w / 135w rev3)

Hi!

I'm having problem using new RED20 device + WiFi module.

With ethernet speed is just fine, but when connected to wifi connection speed is horrible.

RED's operation mode is Standard/unified.

Tested with various devices. Laptop connects to REDs AP at 300Mbps.

Most of the time Ping is well over 100. At worst over 3000ms.

What could be done to fix this? Firewall we're using is XG 210 running SFOS 17.5.11 MR-11.

Patterns are up to date.

 

Here's some pics:  

 

This is the speed with laptop connected to RED's wifi: 

 

This is the result when connected with ethernet through RED:

This is the Wifi speed when same device connected to APX320 to clarify it's not the client device issue (Not connected to RED):



This thread was automatically locked due to age.
Parents
  • Hi Jarno Hynynen,

    Please run command : iwlist scan from wireless client and provide the result if possible.

    Also provide name of SSID you have configured on RED.

    Regards,

    Kaushal

  • Just got the new device from Sophos.

    Guess what...

    It does NOT work either. It's just the same.

  • From my sources I just had a message:

    "This problem has raised multiple tickets so far. And R&D is trying to fix it with severity level "Very High" 

     

     

    So please Sophos "official" support, could you please comment this. Where are we now with this?

    What is the estimate when we can expect to have this fix?

  • We are actively investigating unusually slow wireless performance on a small number of SD-RED devices. The problem has been reproduced and Engineering are currently trying to root cause the issue. The tracking ID for this issue is NRF-341.

    This is indeed getting very high priority and I hope to have an answer very soon, but clearly I cannot make a commitment to a possible fix time. I will keep the Community updated when I know more

     

    Stuart Hatto | XG Product Management

  • Just wanted to keep everyone aware of the current progress.

    We have now reproduced and root caused the slow performance of SD-RED WiFi. This does not affect every device but we will be releasing a pattern update for XG connected devices around the 19th June, and an update for UTM somewhere around the 23rd June.

    I'm sorry that we can't bring these dates in any closer, but the build, packaging, QA and legal requirements all take time.

     

    Once again the dates above are estimates not promises, and I will keep the Community updated if there are any changes to timescale.

     

    Thank you for your patience,

    Stuart

  • Stuart, is this issue tied to certain lots of the REDs and/or WiFi modules shipped, or is it about specific configurations that trigger the issue?  If it's the latter, it'd be nice to know what configurations trigger the issue so we can work around it.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • Stuart, is this issue tied to certain lots of the REDs and/or WiFi modules shipped, or is it about specific configurations that trigger the issue?  If it's the latter, it'd be nice to know what configurations trigger the issue so we can work around it.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
  • It's not configuration related, and there is no workaround*. At this point there are only 2 cases reported to Sophos Support but there are many hundreds of devices with the WiFi module running without reported issues.

    *Well, there is a workaround and that would be to add an APX to a wired port.

  • Hi everyone,

    There is an update for the performance issue. The fix will be released in a Pattern update on 18th June for SFOS 18 MR, 23rd June for SFOS 17.5 MR12 and in RPM on 23rd June for UTM 9.7 MR3.

    For more information, please refer to this article.

    Regards,

    Jasmin
    Community Support Engineer | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

  • There it is:

    On your appliance : Backup & Firmware - pattern updates. 

    __________________________________________________________________________________________________________________

  • Nope!

    Only version 3.0.0 available.

  • Can you verify your u2d.log on Shell, that your XG is getting this packet or not? 

    __________________________________________________________________________________________________________________

  • XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    Mon Jun 22 11:08:30 2020 Starting download for file savi_1.00_1.0.15725_immdiff.tar.gz.gpg
    Mon Jun 22 11:09:30 2020 Download completed for file atp_threatdata_1.00_1.0.0305.tar.gz.gpg
    Mon Jun 22 11:09:30 2020 We are primary machine in HA. Syncing download for module atp to auxiliary machine
    gpg: Signature made Mon Jun 22 09:37:58 2020 EEST using RSA key ID 6A20EB0B
    gpg: NOTE: trustdb not writable
    gpg: Good signature from "Sophos Up2Date Server <updates@sophos.com>"
    Mon Jun 22 11:10:32 2020 Download for file atp_threatdata_1.00_1.0.0305.tar.gz.gpg passed integrity and gpg checks
    Mon Jun 22 11:10:33 2020 Either FILE or MSID received in U2DVERSION is blank, atp_1.00_1.0.0305.tar.gz,
    Mon Jun 22 11:10:33 2020 Current atp patterns are at /content/atp_1.00/1.0.0304
    Mon Jun 22 11:10:33 2020 New updated patterns are now at /content/atp_1.00/1.0.0305
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    DEBUG Jun 22 11:11:58 [4090]: Response length : 428
    DEBUG Jun 22 11:11:58 [4090]: Received name : savi_1.00_1.0.15725_immdiff.tar.gz.gpg
    DEBUG Jun 22 11:11:58 [4090]: Received location : d30ncyzaneb4q0.cloudfront.net/savi_1.00_1.0.15725_immdiff.tar.gz.gpg
    DEBUG Jun 22 11:11:58 [4090]: Received version : 1.0.15725
    DEBUG Jun 22 11:11:58 [4090]: Received size : 11405
    DEBUG Jun 22 11:11:58 [4090]: Received md5sum : d4aa0e5a52510c08fef30d03c8ee7260
    DEBUG Jun 22 11:11:58 [4090]: Received module : savi
    DEBUG Jun 22 11:11:58 [4090]: Received cv : 1.00
    DEBUG Jun 22 11:11:58 [4090]: Received type : immdiff
    WARNING Jun 22 11:11:58 [4090]: A new update is available for savi but we are ignoring it as download for a previous update is in progress.
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    DEBUG Jun 22 11:13:15 [5505]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:13:15 [5505]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:13:15 [5505]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:13:15 [5505]: Final query string is :
    ?&serialkey=C230763FYBHY975&deviceid=795a96f34d7456aed692ed2521f97ab7464f&fwversion=17.5.12.664&productcode=CN&appmodel=XG210&appvendor=WP03&useragent=SF&oem=Sophos&pkg_ips_version=9.17.19&pkg_ips_cv=14.0&pkg_atp_version=1.0.0305&pkg_atp_cv=1.00&pkg_savi_version=1.0.15725&pkg_savi_patch=2&pkg_savi_cv=1.00&pkg_avira_version=1.0.408551&pkg_avira_patch=2&pkg_avira_cv=4.00&pkg_clientauth_version=1.0.0019&pkg_clientauth_cv=2.00&pkg_apfw_version=11.0.012&pkg_apfw_cv=1.00&pkg_redfw_version=3.0.000&pkg_redfw_cv=2.00&pkg_waf_version=1.0.0006&pkg_waf_cv=1.00&pkg_sslvpn_version=1.0.007&pkg_sslvpn_cv=1.00&pkg_ipsec_version=1.4.001&pkg_ipsec_cv=1.00&central_mgmt=1.0
    DEBUG Jun 22 11:13:15 [5505]: Response code : 200
    DEBUG Jun 22 11:13:15 [5505]: Response body :
    <Up2Date/>

    DEBUG Jun 22 11:13:15 [5505]: Response length : 11
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Final query string is :
    ?&serialkey=C230763FYBHY975&deviceid=795a96f34d7456aed692ed2521f97ab7464f&fwversion=17.5.12.664&productcode=CN&appmodel=XG210&appvendor=WP03&useragent=SF&oem=Sophos&pkg_ips_version=9.17.19&pkg_ips_cv=14.0&pkg_atp_version=1.0.0305&pkg_atp_cv=1.00&pkg_savi_version=1.0.15725&pkg_savi_patch=2&pkg_savi_cv=1.00&pkg_avira_version=1.0.408551&pkg_avira_patch=2&pkg_avira_cv=4.00&pkg_clientauth_version=1.0.0019&pkg_clientauth_cv=2.00&pkg_apfw_version=11.0.012&pkg_apfw_cv=1.00&pkg_redfw_version=3.0.000&pkg_redfw_cv=2.00&pkg_waf_version=1.0.0006&pkg_waf_cv=1.00&pkg_sslvpn_version=1.0.007&pkg_sslvpn_cv=1.00&pkg_ipsec_version=1.4.001&pkg_ipsec_cv=1.00&central_mgmt=1.0
    DEBUG Jun 22 11:14:47 [7409]: Response code : 200
    DEBUG Jun 22 11:14:47 [7409]: Response body :
    <Up2Date/>

    DEBUG Jun 22 11:14:47 [7409]: Response length : 11
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Final query string is :
    ?&serialkey=C230763FYBHY975&deviceid=795a96f34d7456aed692ed2521f97ab7464f&fwversion=17.5.12.664&productcode=CN&appmodel=XG210&appvendor=WP03&useragent=SF&oem=Sophos&pkg_ips_version=9.17.19&pkg_ips_cv=14.0&pkg_atp_version=1.0.0305&pkg_atp_cv=1.00&pkg_savi_version=1.0.15725&pkg_savi_patch=2&pkg_savi_cv=1.00&pkg_avira_version=1.0.408551&pkg_avira_patch=2&pkg_avira_cv=4.00&pkg_clientauth_version=1.0.0019&pkg_clientauth_cv=2.00&pkg_apfw_version=11.0.012&pkg_apfw_cv=1.00&pkg_redfw_version=3.0.000&pkg_redfw_cv=2.00&pkg_waf_version=1.0.0006&pkg_waf_cv=1.00&pkg_sslvpn_version=1.0.007&pkg_sslvpn_cv=1.00&pkg_ipsec_version=1.4.001&pkg_ipsec_cv=1.00&central_mgmt=1.0
    DEBUG Jun 22 11:14:47 [7409]: Response code : 200
    DEBUG Jun 22 11:14:47 [7409]: Response body :
    <Up2Date/>

    DEBUG Jun 22 11:14:47 [7409]: Response length : 11
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1# tail u2d.log
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG Jun 22 11:14:47 [7409]: Final query string is :
    ?&serialkey=C230763FYBHY975&deviceid=795a96f34d7456aed692ed2521f97ab7464f&fwversion=17.5.12.664&productcode=CN&appmodel=XG210&appvendor=WP03&useragent=SF&oem=Sophos&pkg_ips_version=9.17.19&pkg_ips_cv=14.0&pkg_atp_version=1.0.0305&pkg_atp_cv=1.00&pkg_savi_version=1.0.15725&pkg_savi_patch=2&pkg_savi_cv=1.00&pkg_avira_version=1.0.408551&pkg_avira_patch=2&pkg_avira_cv=4.00&pkg_clientauth_version=1.0.0019&pkg_clientauth_cv=2.00&pkg_apfw_version=11.0.012&pkg_apfw_cv=1.00&pkg_redfw_version=3.0.000&pkg_redfw_cv=2.00&pkg_waf_version=1.0.0006&pkg_waf_cv=1.00&pkg_sslvpn_version=1.0.007&pkg_sslvpn_cv=1.00&pkg_ipsec_version=1.4.001&pkg_ipsec_cv=1.00&central_mgmt=1.0
    DEBUG Jun 22 11:14:47 [7409]: Response code : 200
    DEBUG Jun 22 11:14:47 [7409]: Response body :
    <Up2Date/>

    DEBUG Jun 22 11:14:47 [7409]: Response length : 11
    XG210_WP03_SFOS 17.5.12 MR-12.HF062020.1#

  • Apologies for the confusion - the pattern update is currently for v18 MR1 only. 17.5 pattern update will be released this week, hopefully tomorrow.

     

    Stuart