You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest Shellshocker patch triggers this bug. In short, "/etc/sysconfig/network-scripts/network-functions" does not work under bash 4.x - which is applied as part of the Shellshocker patch. The result is network interfaces come up/start, but fail to apply their gateway information.
Fixes:
1.) Manually define a gateway on a nominated interface via "route add" after restarting the system or restarting network services - example:
service network restart
route add default gw n.n.n.n eth0
2.) Go to line 78 in "/etc/sysconfig/network-scripts/network-functions" and change:
. $CONFIG
to:
. ./$CONFIG
(Note the spaces between the '.')
Note: On Redhat systems, the bug documentation cited above infers this change is required on line 80, not 78.
The text was updated successfully, but these errors were encountered:
For your reference:
http://bugs.centos.org/view.php?id=4582
https://bugzilla.redhat.com/show_bug.cgi?id=482826
The latest Shellshocker patch triggers this bug. In short, "/etc/sysconfig/network-scripts/network-functions" does not work under bash 4.x - which is applied as part of the Shellshocker patch. The result is network interfaces come up/start, but fail to apply their gateway information.
Fixes:
1.) Manually define a gateway on a nominated interface via "route add" after restarting the system or restarting network services - example:
service network restart
route add default gw n.n.n.n eth0
2.) Go to line 78 in "/etc/sysconfig/network-scripts/network-functions" and change:
. $CONFIG
to:
. ./$CONFIG
(Note the spaces between the '.')
Note: On Redhat systems, the bug documentation cited above infers this change is required on line 80, not 78.
The text was updated successfully, but these errors were encountered: