There is: Code Listing 13: Manually setting IP information for eth0 config_eth0=( "192.168.0.2 netmask 255.255.255.0" ) routes_eth0=( "default gw 192.168.0.1" ) There should be: Code Listing 13: Manually setting IP information for eth0 config_eth0=( "192.168.0.2 netmask 255.255.255.0" ) routes_eth0=( "default via 192.168.0.1" ) Reproducible: Always Steps to Reproduce:
example looks fine to me
gw - is used by the route command from net-tools via - is used by the ip route command from iproute2 Both should work equally well with baselayout-1.11.13 and better. baselayout-1.11 and earlier prefer net-tools baselayout-1.12 prefers iproute2
But it didn't work. I was setting up Gentoo box remotely. It failed while initialising network. I had to send there a guy, who changed it from gw to via and then everything worked fine. sys-apps/baselayout-1.11.13 sys-apps/iproute2-2.6.11.20050310-r1 sys-apps/net-tools-1.60-r11
Attach the non working /etc/conf.d/net please - there must be something else that's wrong
Not working net.eth0: config_eth0=( "80.55.147.109 netmask 255.255.255.248" ) routes_eth0=( "default gw 80.55.147.105" ) Working one: config_eth0=( "80.55.147.109/29" ) routes_eth0=( "default via 80.55.147.105" ) So two things has changed, but it only worked after changing routes_eth0
Mike, Roy? Any pointers on this?
All of his examples given correctly setup the interface. Personally, I have no issue with the example being changed, but if it is changed then please use iproute2 format instead of ifconfig, fex config_eth0=( "192.168.0.2/24" ) routes_eth0=( "default via 192.168.0.1" )
(In reply to comment #7) > Personally, I have no issue with the example being changed, but if it is changed > then please use iproute2 format instead of ifconfig, fex We wouldn't want to change the example *unless* the current one fails or doesn't work at all. Atleast that's what I feel about it. If this can't be reproduced or is a one off case, is a change warranted?
updating the example to be 'future-proof' isn't useless, but should only happen is the proposed change works for all architectures, all users. Think about networkless installs as well, btw. Are net-tools and iproute2 always available?
The current example works just fine with current and future baselayouts, regardless of using iproute2 or net-tools. baselayout transparently maps settings so that net-tools variant works on iprout2 and vice versa. net-tools is part of the system profile iproute2 is not, but should be a 100% drop in replacement for most users right now
yes, net-tools/iproute2 are available on all arches
(In reply to comment #10) > The current example works just fine with current and future baselayouts, Indeed.
