Thread Info
  • State Verified Answer
  • +6 person also asked this people also asked this
  • Locked Locked
  • Replies 63 replies
  • Answers 4 answers
  • Subscribers 34 subscribers
  • Views 166327 views
  • Users 0 members are here
Options
Suggested
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

Slow downloads on smartphones connected over AP

Jelle

Hi,

we have a WiFi running for our smartphones mainly to update Android and apps. WiFi is offered through an AP55. Only smartphones can connect based on their MAC address. There is an own firewall rule for these connections with the following options active: HTTP scanning, block Google QUIC, detect zero day malware with Sandstorm, Scan FTP.

Unfortunately downloads are very slow. App updates take a long time and Android updates are canceled at a certain point by the smartphone itself.

As all updates are done over secure socket layer protocol and HTTPS scanning is not active I wonder what could be the reason. I checked the IP addresses that are used during update and always got to https://r3---sn-h0jeened.gvt1.com/ and https://r4---sn-h0jeened.gvt1.com/ so I excluded gvt1.com from HTTPS scanning, malware scanning and sandstorm. But also this showed no improvement on download speed.

Currently I wonder if the throughput of the AP55 is that slow?

 

Does anybody have any suggestions? Thanks.



This thread was automatically locked due to age.
Parents
  • 0

    Perhaps we're experiencing the same issue. :-/

    Have you tried to turn off Scan HTTP and set Web Policy to None in your network rule?

    We're using this both components in several network rules. But if we use them in a Wifi network rule, the Wifi performance drops extremely. I've already opened a ticket and Sophos Support is currently investigating our problem.

  • 0 in reply to dja

    Turned off Scan HTTP and set web policy to None. No improvement...

  • 0 in reply to Jelle

    The MTU Size (1450) is written in der Database. 

    So can you explain the history of your current installation? Because we dont change such thing with a firmware update. Basically the appliance should create everything new with the correct value (1500). 

    But dja already explained, it is not. So i have to assume, that the appliance does not allow to create 1450 and 1500 on one access points (which is clearly correct, because this would cause a real mess). 

    So basically if you delete everything from the wireless protection and maybe disable and enable the wireless protection, the new created wireless network should work fine. 

    You could also go with the Sophos Support. I could be possible to change the MTU Size via database, but i would not do that. 

    tbh, recreating wireless protection is a 5-10 minute task. 

  • 0 in reply to LuCar Toni

    The appliance was first installed in february 2018 with SFOS 17 and was directly updated to 17.0.5-MR5. It has been updated to 17.1.1-MR1 about 5 weeks ago. WiFi with AP55 was set up about 3 weeks ago. So where comes MTU 1450 from when it was fixed in 16.05?

  • 0 in reply to Jelle

    I cannot tell you, how this can happen. 

    I already checked three appliances right now. All Wireless Networks are correct there. 

    And this is the first time since 2 years, where i could find such an issue. 

     

    Found some threads about this. 

    https://community.sophos.com/products/xg-firewall/f/sophos-xg-firewall-general-discussion/76768/unacceptable-guest-wifi-performance-regular-wifi-is-ok

     

    Also interesting is the initial firmware. You updated it "directly to MR5". From which version? 

  • 0 in reply to LuCar Toni

    manbearpig said:

    So i have to assume, that the appliance does not allow to create 1450 and 1500 on one access points (which is clearly correct, because this would cause a real mess). 

    Tested again and you're right. I've created a new Wireless Network, it has a MTU size of 1500. Then I assigned this new Wireless Network to an existing AP, now it has a MTU size of 1450.

    We've also would prefer to just change the values, instead of re-creating several Wifi networks...

    PS: We're coming from SFOS 15. It has been a loooong way. ;)

  • 0 in reply to dja

    I can confirm that. A new wireless network has MTU 1500 until assigned to the AP. Then it has MTU 1450. Unassigning it from the AP has no effect, MTU still is 1450. So I have to delete all wifi networks (3 active networks) and then do what? Delete the AP?

  • 0 in reply to Jelle

    Hi,

    Seems like the config of the MTU is attached to the AP. 

    So delete the AP and try to attach it again to the AP. Should stay with MTU1500 and this will most likely resolve all your issues. 

  • 0 in reply to LuCar Toni

    do you work with a testing system? Would it then be possible to test this? Our XG and WiFi are productive system so I wouldn't want to test it on them.

  • 0 in reply to LuCar Toni

    manbearpig said:

    So delete the AP and try to attach it again to the AP. Should stay with MTU1500 and this will most likely resolve all your issues.  

    I'm not quite sure. I've used a dedicated AP and a new Wireless Network for testing. Both of them never have seen SFOS 16.05.2 before. But now I know where to look, so I'll test it again.

    Jelle said:

    dja do you work with a testing system? Would it then be possible to test this?

    Not really, but I think tommorow I will have some time for testing. :)

  • 0 in reply to dja

    Also possible to contact the Sophos Support. But i am not quite sure, which way is most likely the fastes. I would recreate everything, because it take only couple of minutes. Delete the Network, delete the AP, disable the Wireless Protection. Enable it and add the AP plus create the wireless network. 

  • 0 in reply to LuCar Toni

    manbearpig said:

    I would recreate everything, because it take only couple of minutes. Delete the Network, delete the AP, disable the Wireless Protection. Enable it and add the AP plus create the wireless network. 

    Not so easy. We're using many hotspot vouchers and I'm not willing to risk that all vouchers are getting unusuable.

    SaschaParis said:

    Google Play and some other on Android often used services doesn't play well with AV scanning or MITM of the proxy.

    In our case it's not limited to Google services. We're experiencing general Guest Wifi performance problems. Even if I download a Debian image. If we disable Scan HTTP and Web Policy the throughput is getting normal. As said, we're also using this two components in several other Network Rules, there are no problems with them at all, only in Separate Zone Wifi.

     

    I've just deployed a new AP and configured a new Wireless Network for it. Inital the Wireless Network has a MTU of 1500. After I've assigned it to the AP, the MTU is now 1450 again. :(

Reply
  • 0 in reply to LuCar Toni

    manbearpig said:

    I would recreate everything, because it take only couple of minutes. Delete the Network, delete the AP, disable the Wireless Protection. Enable it and add the AP plus create the wireless network. 

    Not so easy. We're using many hotspot vouchers and I'm not willing to risk that all vouchers are getting unusuable.

    SaschaParis said:

    Google Play and some other on Android often used services doesn't play well with AV scanning or MITM of the proxy.

    In our case it's not limited to Google services. We're experiencing general Guest Wifi performance problems. Even if I download a Debian image. If we disable Scan HTTP and Web Policy the throughput is getting normal. As said, we're also using this two components in several other Network Rules, there are no problems with them at all, only in Separate Zone Wifi.

     

    I've just deployed a new AP and configured a new Wireless Network for it. Inital the Wireless Network has a MTU of 1500. After I've assigned it to the AP, the MTU is now 1450 again. :(

Children