Skip to content
This repository has been archived by the owner on Nov 11, 2021. It is now read-only.

ip rule management for RedHat completely different structure and approach #227

Open
igarny opened this issue Apr 4, 2018 · 2 comments
Open

Comments

@igarny
Copy link
Contributor

igarny commented Apr 4, 2018

Expected Behavior

similar approach as with Debian ip rule management #226

Actual Behavior

https://github.com/example42/puppet-network/blob/master/templates/rule-RedHat.erb

Steps to Reproduce the Problem

Specifications

Please add this info:

  1. Output of facter -p on the failing node (at least the OS related facts)
  2. Version of Puppet and of the module
  3. The relevant Puppet code and eventually Hiera data
@alvagante
Copy link
Member

@igarny not sure on what you miss here, the ipv6 family support on RedHat based on the family parameter (and not eventually with ipv6 directly specified in the rule entry?)

@igarny
Copy link
Contributor Author

igarny commented May 8, 2018

All I'm stating is that both approaches for Debian and RedHat on ip rule management differ a lot, where it shouldn't. After all the implementation of the ip stack is very close in both flavors of Linux and the ip commands are the same.
Also there is a risk to continue to diverge, them by having people adding specifics for Debian in the respective templates.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants