Skip to content

Conversation

@intelfx
Copy link

@intelfx intelfx commented Jan 27, 2025

Accept a new variable $IFB_PATTERN which is used as a printf(1)
pattern to generate the IFB interface name from the primary interface
name. The default is ifb4%s which corresponds to the pre-existing
behavior.

Signed-off-by: Ivan Shapovalov [email protected]

Accept a new variable `$IFB_PATTERN` which is used as a printf(1)
pattern to generate the IFB interface name from the primary interface
name. The default is `ifb4%s` which corresponds to the pre-existing
behavior.

Signed-off-by: Ivan Shapovalov <[email protected]>
@moeller0
Copy link
Collaborator

Out of curiosity, what is the motivation for this?

@intelfx
Copy link
Author

intelfx commented Jan 27, 2025

Out of curiosity, what is the motivation for this?

Some less-than-configurable monitoring software that uses hardcoded patterns of ignored interface names. There is a pattern for ifb interfaces, but it does not match ifb4*.

@moeller0
Copy link
Collaborator

Fair, may I ask to maybe add this to the commit description (maybe even reveal that monitoring software's name)? So far the fixed naming for sqm created IFBs has helped in the past to detect cases where users accidentally tried multiple traffic shaping solutions in parallel...

@tohojo
Copy link
Owner

tohojo commented Jan 27, 2025

Yes, please document the reason for the change in the commit message :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants