Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 26 subscribers
  • Views 6045 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

[Bug] Web Filter & CrashPlan

Joffer

Just want to raise a bug I've found. Not sure how much an older question is monitored, but there has to be a bug in the Web Filter engine.

Setting WebFilter to 'Allow All" doesn't work with CrashPlan. It has to be set to 'None'. Otherwise the cloud backup software won't log in and/or connect/sync/back up.

https://community.sophos.com/products/xg-firewall/f/125/p/32111/286462#286462

Feel free to close/delete this post if regarded as duplicate.

OT - Where do we report bugs? General discussion?



This thread was automatically locked due to age.
  • 0

    Hi Joffer,

    Greetings.

    As per you previous post, where CrashPlan worked when Firewall Rule you created had "None" Filters applied. This is because, when you configure a Firewall Rule in XG with None Filter it will not forward the traffic through it's proxy but simply bypass it completely.

    Configuring "Allow all", I request you to take a TCPDUMP, and check at what MTU-MSS value does the packet from CrashPlan server respond to, tweaking the MTU-MSS value may resolve this! To change the MTU-MSS value in Sophos XG, you have to take console access to Firewall and go to option 4. Device console. 

    console> set network mtu-mss Port2 mtu default mss value (1412 or 1380)

    Such issue can be resolved but need deep inspection which can be done in Live environment, if you have a subscribed support, i request you to raise a support case here: support@sophos.com.

    Let us know if tweaking the MTU-MSS value helps :)

    Thanks

    Sachin Gurung

  • 0 in reply to sachingurung

    Sorry for not getting back to you.. It was solved earlier (1), just to have a new problem kick in with v16.x, which is solved temporarily (2) and acknowledged by Sophos (3). Just posting for completeness :)

     

    1. community.sophos.com/.../314571

    2. community.sophos.com/.../310556

    3. community.sophos.com/.../125458