default network example does not work on RHEL about puppet-network HOT 11 CLOSED

I had to, manually, remove GATEWAY setting in /etc/sysconfig/network-scripts/ifcfg-ethX - and then the default network_route works as expected.
Setting the ip for eth0 interface with network_config - didn't even remove the GATEWAY setting.

Oddly enough, the other routes now works as well:

192.168.63.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
192.168.0.0     192.168.63.1    255.255.0.0     UG    0      0        0 eth0
10.0.0.0        192.168.63.1    255.0.0.0       UG    0      0        0 eth0
0.0.0.0         192.168.63.50   0.0.0.0         UG    0      0        0 eth0

(I rebooted once more).

from puppet-network.

Thanks for reporting this!

Looking at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-static-routes.html , it seems like the format for the routes should be valid; if I'm understanding you correctly then the routes did start working?

The documentation also says that you can add a default route of the format default via X.X.X.X dev interface; is the problem that GATEWAY was added to the file and then not removed later? Were you managing the interface file with the network_config type?

With respect to not applying the configuration immediately, I've left that up to users to handle. Restarting networking is something that you can't get wrong - if Puppet was restarting the network each time a route was updated it's entirely possible that the machine could get knocked offline. Since it's a bit risky, I've opted to not manage that and let end users do what best suits them. Does that make sense?

from puppet-network.

Hi,
The format is not valid, when using IP commands arguments format, the netmask should be specified using CIDR notation:

10.8.0.0/24 via 172.20.8.1 dev eth1

Instead of

10.8.0.0/255.255.255.0 via 172.20.8.1 dev eth1

If not the network init script returns an error:

Bringing up interface eth1:  Error: an inet prefix is expected rather than "10.8.0.0/255.255.255.0".
Error: an inet prefix is expected rather than "10.8.1.0/255.255.255.0".

And the module is always removing the CIDR notation from the route, even when setting netmask to 24.

from puppet-network.

Hi,
I managed to get this working using the changes mentionned in #58.

from puppet-network.

I can confirm it's working well...
It's been one year and half and nobody merge this

from puppet-network.

@confiq if the pull request worked for you, could you update the pull request with tests and rebase it so that it can be merged?

from puppet-network.

@adrienthebo: are we talking about PR #62 ?
It's not mine PR so I can't rebase it but if needed I can make new PR.
About tests, It passes all tests so I don't see a problem merging it. Unless you want to write tests for new check new CIDR notations

CC @gwarf

from puppet-network.

A new PR would be fine; I'm fine with merging code to fix this issue but the existing PR has merge conflicts. Since there is a behavior change, it does need tests before it gets merged.

from puppet-network.

And if @gwarf is willing to continue working it then superb, but if that doesn't work out I'm happy to accept PRs from other locations.

from puppet-network.

Ok,
I've been using HEAD version and it's working fine.
I can't confirm this bug anymore.

from puppet-network.

okay, thank you @confiq!

from puppet-network.