Get access to immediate incident response assistance.
Eliminate active threats with 24/7 threat detection, investigation, and response.
Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.
Advance your cybersecurity program and get expert guidance where you need it most.
Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.
Prevent unauthorized access and exceed compliance requirements.
Stop email threats others miss and secure your organization against the #1 ransomware attack vector.
Prepare for the inevitable with 24/7 global breach response in-region and available on-site.
Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.
This problem occurs because in 2.2, the kernel forces the default gateway to route through eth0 - previous versions routed through eth1 instead. As such, the filter will likely be set to associate its listening/receiving interface with the default gateway.
(1)Modify /etc/sysconfig/network to remove the GATEWAY entry. (2)Add the same GATEWAY entry to the file /etc/sysconfig/network-scripts/ifcfg-eth1. (3)Run ifdown eth1;ifup eth1 (4)Run ifdown eth0;ifup eth0 (5)Run /usr/local/shadow/bin/route_table and compare the route table with before the change to make sure no entries are missing. (6)Notify the customer not to make GUI changes or click on the save button in network settings, as this will overwrite the fixes.
To contact Trustwave about this article or to request support: