- When sosreport is run, some kernel modules are loaded as a side effect; the loading of unwanted kernel modules consumes memory and may cause other issues
- The output of
sysctl -achanges after a run of sosreport due to the bridge kernel module being loaded
- The bridge module's sysctls are initialized to their defaults, instead of being properly initialized via
- Despite not having any bridge interfaces configured, you find you have these set in
net.bridge.bridge-nf-call-arptables = 1 net.bridge.bridge-nf-call-iptables = 1 net.bridge.bridge-nf-call-ip6tables = 1
- Red Hat Enterprise Linux 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.