On Mon, Jun 27, 2016 at 12:44 PM, Rick Stevens ricks@alldigital.com wrote:
On 06/26/2016 06:44 PM, Ed Greshko wrote:
On 06/27/16 08:51, Sam Varshavchik wrote:
For the longest time I had /etc/sysconfig/network-scripts/eno2 specify:
IPADDR1=216.254.115.102 PREFIX1=24 IPADDR2=216.27.136.223 PREFIX2=24 IPADDR=216.254.115.190 PREFIX=24
Maybe try reordering what is in your /etc/sysconfig/network-scripts/eno2 file?
Currently IPADDR=216.254.115.190 is last. Maybe move it, and associated parameters, above IPADDR1?
Just a shot in the dark....
I tend to agree. If you look at the output of the "ip addr" output, you'll notice that the .190 address is listed as "global secondary", so it is now the secondary IP address for the NIC in that subnet, and that's probably because it came after the .102 specification. I believe the script just looks for "IPADDR.+" in the config file. It doesn't reorder things based on the ordinal (or lack thereof), it just uses them as they're seen.
I'd missed the output of "ip a" and the "global secondary".
ifup-eth has
for idx in {0..256} ; do ... if ! ip addr add ${ipaddr[$idx]}/${prefix[$idx]} \ brd ${broadcast[$idx]:-+} dev ${REALDEVICE} ${SCOPE} label ${DEVICE}; then net_log $"Error adding address ${ipaddr[$idx]} for ${DEVICE}." fi ...
so you could try
IPADDR0=216.254.115.190 PREFIX0=24 IPADDR1=216.254.115.102 PREFIX1=24 IPADDR2=216.27.136.223 PREFIX2=24
(or #1/#2/#3) even though network-functions has
for idx in '' {0..255} ; do ipaddr[$i]=$(eval echo '$'IPADDR$idx) ...
so this shouldn't be necessary.