- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Hello all,
we are facing the problem, that after upgrading a Cluster to R80.10, log accounting does not work any more. (worked with R77.30) So
- just the FW blade is used (no App Control etc.)
- accounting is enabled for the rule
- nevertheless, the accounting fields are empty in the log
We have waited quite a while to make sure the fields are filled up.
Case is open, but TAC told us that the App Control blade is necessary for accouting which i don´t think is true
(at least in my lab it works with the fw blade only)
I did not find any usefull SK/information for analysing this problem.
Does anyone had the same situation?
Thanks a lot
Matthias
Hi PhoneBoy,
SecureXL is enabled
GW-1> fwaccel stat Accelerator Features : Accounting, NAT, Cryptography, Routing, |
As we are using the FW blade only, (no IPS/AppControl), the traffic should be accelerated.
Here is part of the "fwaccel stats" output:
General |
btw., at the customer (R80.10) and in my lab environment (R80.20) we have the same strange situation:
Accounting is enabled for the rule which allows (admin) traffic to the firewall. After doing a ssh/Web Session to the master and the backup member , the backup member is generating accounting data, the master is not.
In my lab, switching acceleration on/off did not make any difference.
Switching VRRP, so the Backup is becoming the master, did make a difference.
After that, a login to the former master caused him to generate accounting data
(we have not done this at the customer yet)
What i further did:
fwd debug enabled (fw debug fwd on TDERROR_ALL_ALL=5)
If accounting is working, then a lot of "PackLogData" entries are generated in the fwd.elg:
[FWD 10503 3825499024]@FW1-1[18 Jul 14:27:48] CBinObjCommon::PackLogData: packing new field: index: 11 Field Offset: 0x0, (index + Field Offset) % Fields Num: 11, field type: eFtDword [FWD 10503 3825499024]@FW1-1[18 Jul 14:27:48] CBinObjCommon::PackLogData: Field number:11, Data offset:26, field Value:32 [FWD 10503 3825499024]@FW1-1[18 Jul 14:27:48] CBinObjCommon::PackLogData: fieldName is: client_outbound_bytes |
Looks like the accouting fields (here client_outbound_bytes) are updated.
Matthias
it´s a bug. Fix available. See sk159432 for further details.
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY