Request for comments: static routing configuration

[adrienthebo]

One of the features that has been asked for frequently is support for static network routes. This is a feature I hope to add, but I would like feedback on how the type should be implemented - that is, what are the types of information needed in the type. For example:

network_route { 'default':
  family  => 'inet',
  type    => 'network',
  netmask => '0/0',
  device  => 'eth0',
  gateway => '1.2.3.4',
  metric  => '0',
}

This is one suggested interface for the network_route type. What I need are example types like this and the expected output, so I can get an idea of what attributes need to be handled and how.

[vjanelle]

Looks about right.. The RHEL init scripts have the format:

any net ...

and passes that as

/sbin/route add -<entry from static-routes s/^any //>

If that makes sense.

[adrienthebo]

#23 adds in an implementation of network_route for Debian; if people could take a look at that and give opinions on that it would be great. I think it's a good implementation but there are a few edge cases around multiple routes with the same destination on multiple interfaces that could use some thought.

[codec]

The bad thing about #23 is that it isn't possible to implement support for multiple interfaces with the same route / metrics as the if-up.d script doesn't support any kind of options passing. The lines are passed almost as-is to netstat (:shit:).

Maybe implementing an iproute2 provider might be more flexible across multiple distro? That would involve coming up with a solution to persist across reboots (i.e. write a if-up style helper) though.

[adrienthebo]

Since we have Redhat and Debian route implementations I'm going to consider this solved. Thanks all!