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

WAF issues after upgrading to 9.602-3

Hi,

after upgrading from 9.601-5 to 9.602-3 we experienced issues ( intermittently lost packets and rejected connections) at some Apps (Kerio Connect), all HTTPS only.

Rollback to 9.601-5 fixed the problems. Found no useful messages in the WAF/FW logs. We have 13 Apps in the WAS config defined, maybe a number with a bad Karma.

Thanks

Henri

This thread was automatically locked due to age.

BrucekConvergent over 4 years ago in reply to Jesse Wulf

9.603 does not include the fix we are all waiting for, only corrects an AWS licensing issue.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Sophos Platinum Partner

--------------------------------------

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.
Cancel
Vote Up 0 Vote Down

Cancel
FloSupport over 4 years ago in reply to BrucekConvergent

Hi All,

The issue NUTM-10952 is still being actively investigated by our team with critical priority. Please stay tuned as more information regarding a fix version will be announced as it becomes available.

Regards,

Florentino
Director, Global Community & Digital Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the 'Verify Answer' button.

The Award-winning Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
Claudio Schnell da Silva over 4 years ago in reply to FloSupport

Hi FloSupport,

the issue NUTM-10952 doesn´t seem to match the issue described by the OP (WAF issues).

My Sophos UTM support company is asking me constantly for occurrences of WAF failures and screenshots from our monitrings and even web check locations.

Thanks,

Claudio
Cancel
Vote Up 0 Vote Down

Cancel
FloSupport over 4 years ago in reply to Claudio Schnell da Silva

Hi Claudio Schnell da Silva

My apologies, I was replying back to the ID that BrucekConvergent mentioned.

Henri04 I would advise that you raise a case so that our support team can follow up and further investigate your appliance. Please PM me with your case details as well.

Florentino
Director, Global Community & Digital Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the 'Verify Answer' button.

The Award-winning Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
Henri04 over 4 years ago in reply to FloSupport

Hi,

I found in another topic that the Webfilter issues are solved by changing the SPX port.

Have here also SPX and the SPX traffic ist redirected to the public IP of the UTM appliance with port 443, with is the WAF.

I have a WAF rule to redirect the SPX traffic to a internal IP where SPX is listing.

The reason for that, have in case of a ISP failure a backup with only one IP and have to use port 443, otherwise I'am blocked by customers FWs.

Could this configuration ends in bad ipfilter rules, after a firmware upgrade?

Thanks

Henri

Henri
Cancel
Vote Up 0 Vote Down

Cancel
Henri04 over 4 years ago in reply to Henri04

Any other port than 443 causes an invalid link in the SPX mail.

So how to setup this one after applying the update?

Thanks

Henri
Cancel
Vote Up 0 Vote Down

Cancel