Red Hat Bugzilla – Bug 921476
Please document rule6-* files inside the initscripts documentation
Last modified: 2016-11-25 08:07:18 EST
Description of problem: I've just configured policy routing for IPv6 and I've looked for rule-* equivalent for IPv6. I decide to look inside the documentation file "/usr/share/doc/initscripts-9.03.38/sysconfig.txt" but I realized that rule6-* information is missing besides the fact, that I can use it according this information: http://rhn.redhat.com/errata/RHBA-2012-0355.html So please document rule6-* avaliability inside sysconfig.txt documentation file. Version-Release number of selected component (if applicable): initscripts-9.03.38-1.el6 Actual results: documentation about rule6-* is missing Expected results: rule6-* possibility should be documented thank you
/etc/sysconfig/network-scripts/rule-<interface-name> +/etc/sysconfig/network-scripts/rule6-<interface-name> Contains lines that specify additional routing rules that should be added when the associated interface is brought up. - Each non-comment line is used directly as an argument to "/sbin/ip rule add". + Each non-comment line is used directly as an argument to "/sbin/ip rule add" + or "/sbin/ip -6 rule add" for rule6 files. Is such change sufficient?
yes, this is fine, it makes rule6-* documented. But I personally prefer to differentiate between different configuration files like for other config files in following way: - keep original rule-* configuration documentation unchanged - just append at the end of file something like this: <snip> /etc/sysconfig/network-scripts/rule6-<interface-name> Contains lines that specify additional IPv6 routing rules that should be added when the associated interface is brought up. Each non-comment line is used directly as an argument to "/sbin/ip -6 rule add". </snip> but in real it does not matter. I just wanted to have rule6-* in documentation. Its your choice :) And thank you for taking this report over.
Upstream commit bd80c85bc077753f7bef74c38d85cab30c8831b0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1679.html