Skip to content
This repository was archived by the owner on Nov 11, 2021. It is now read-only.
This repository was 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

Description

@igarny

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

Activity

  1. alvagante commented on May 7, 2018

    @alvagante
    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?)

  2. igarny commented on May 8, 2018

    @igarny
    ContributorAuthor

    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 join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions