- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Announcing Quantum R82.10!
Learn MoreOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
You can most certainly reset interface counters via the steps in sk61500. Just be aware that reloading a NIC device driver will cause an outage on *all* individual interfaces utilizing that particular driver, including no doubt (in true Murphy's Law fashion) the interface you are currently using for your SSH control connection into the firewall itself. Careful!
Kind of like copy/pasting ACL updates on a Cisco and your SSH session freezes up permanently, sparking a panicked sprint to the console...oops.
--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com
The easiest way is to reboot if that is an option. Otherwise check this SK How to reset interface counters
Reboot not required! | sk61500 |
You'll have to reload the driver on this NIC
You can most certainly reset interface counters via the steps in sk61500. Just be aware that reloading a NIC device driver will cause an outage on *all* individual interfaces utilizing that particular driver, including no doubt (in true Murphy's Law fashion) the interface you are currently using for your SSH control connection into the firewall itself. Careful!
Kind of like copy/pasting ACL updates on a Cisco and your SSH session freezes up permanently, sparking a panicked sprint to the console...oops.
--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com
I am not able to see that sk sk61500. Do you have any idea why it is so?
Either they removed it or its internal sk now.
Just tested these expert mode commands on eth1 interface using vmxnet3 driver, and it worked to reset the counters for that interface:
ifconfig eth1 down;ifconfig eth1 up
This should also work:
ifdown eth1;ifup eth1
Can't vouch for whether the above commands will work with igb/ixgbe/mlx* drivers, if they don't try these WHICH WILL CAUSE AN OUTAGE ON ALL INTERFACES USING THE IGB DRIVER in this example, use at your own risk:
modprobe -r igb; modprobe igb
Then you will need to manually re-up all relevant igb-based interfaces like this to get them working again:
ifup eth0
ifup eth1
ifup eth2
etc....
sk61500 is no longer available for two reasons:
However, @Timothy_Hall describes the procedure in that SK.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 22 | |
| 15 | |
| 11 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY