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 module is currently using the route-$interface file for setting up static routes (which is the correct place for them), but no option to setup a default route statement with other settings like the initcwnd/initrwnd.
This could be solved with using concat fragments, so the 1st fragment could be the default gateway and the 2nd be the static routes.
Or the network::route define could be changed to not take the $interface from $name, so one could have several network::route defines (the way it is now, with the file declared in the define, will break if you have multiple). This would still use concat but would allow for many concats.
Or something else entirely.
Either way it's quite a bit of change to the module and adds a dependency which may not be desired.
I'm happy to take a stab at any of the above and send a pull request, but would like to hear your opinion first.
Have a good day.
-Shawn
The text was updated successfully, but these errors were encountered:
Hello,
Currently the module won't support setting a initcwnd or initrwnd. In order to set these to be persistent, one needs to
*NOTE: initcwnd requires $rhel 6, initrwnd requires $rhel 6.4+
The module is currently using the route-$interface file for setting up static routes (which is the correct place for them), but no option to setup a default route statement with other settings like the initcwnd/initrwnd.
This could be solved with using concat fragments, so the 1st fragment could be the default gateway and the 2nd be the static routes.
Or the network::route define could be changed to not take the $interface from $name, so one could have several network::route defines (the way it is now, with the file declared in the define, will break if you have multiple). This would still use concat but would allow for many concats.
Or something else entirely.
Either way it's quite a bit of change to the module and adds a dependency which may not be desired.
I'm happy to take a stab at any of the above and send a pull request, but would like to hear your opinion first.
Have a good day.
-Shawn
The text was updated successfully, but these errors were encountered: