- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- SecureXL is messed up in AWS when R77.30 JHFA is i...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SecureXL is messed up in AWS when R77.30 JHFA is installed
Good day,
Heads up for all of you that are installing new vSEC instances in AWS with Jumbo take 216, 282 or 292
This is only true for the new AMI R77.30-041.168. Previous version of the AMI works fine with JHFA.
JHFA will install "just fine", but you will notice that traffic is not passing the gateway.
fwaccel off and traffic starts flowing again
Another thing that will show the issue is that running fwaccel stats -s command will only provide 1 single row output for Accelerated packets (instead of normally 4-5 rows or whatever it is).
I have a case with TAC and R&D have identified the issue (race condition of some sort) and are currenly working on specific hotfix for us for specific JHFA take.
According to TAC there is only one other reported íssue about this. So probably it won't find its way as permanent fix in coming JHFA. I have a hard time beleiving this since issue is so easy to reproduce with clean install, but thats the info I have.
Anyway, point of the post was that it might save time for someone.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 |
Thu 09 May 2024 @ 05:00 PM (CEST)
Under the Hood: Automate Azure Virtual WAN security deployments with Terraform