Rachel plays Linux on 5 Oct 2017 16:00:06 -0700 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: [PLUG] Two IP's on an interface. One won't go away. |
I've got an interesting issue with a CentOS Linux release 7.4.1708 (Core) box. This server has two NIC's. One of those NIC's has had a single static IP set on it for a while now. No issues there. However, for some reason I'm having some issues bringing up the second interface.
"ip a" looks like this1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether a4:bb:01:02:43:5c brd ff:ff:ff:ff:ff:ff
inet 192.168.2.141/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether aa:bb:01:02:43:6d brd ff:ff:ff:ff:ff:ff
inet 192.168.1.50/26 brd 192.168.1.63 scope global eth1
valid_lft forever preferred_lft forever
inet 192.168.179.102/30 brd 192.168.179.103 scope global eth1
valid_lft forever preferred_lft foreverIf I "systemctl restart network"... then "ip a" again....1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether a4:bb:01:02:43:5c brd ff:ff:ff:ff:ff:ff
inet 192.168.2.141/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether aa:bb:01:02:43:6d brd ff:ff:ff:ff:ff:ff
inet 192.168.1.50/26 brd 192.168.1.63 scope global eth1
valid_lft forever preferred_lft foreverThe 192.168.1.50 is the only address I want on that interface. Now a few mins later.....1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether a4:bb:01:02:43:5c brd ff:ff:ff:ff:ff:ff
inet 192.168.2.141/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether aa:bb:01:02:43:6d brd ff:ff:ff:ff:ff:ff
inet 192.168.1.50/26 brd 192.168.1.63 scope global eth1
valid_lft forever preferred_lft forever
inet 192.168.179.102/30 brd 192.168.179.103 scope global eth1
valid_lft forever preferred_lft foreverSee? 192.168.179.102 is back again. This same behavior persists even if I "ip addr del 192.168.179.102/30 dev eth1". Wait a few minutes later and 179.102 is back once again.
NetworkManager is not installed or running.
I've got BOOTPROTO="static" set in both ifcfg-ethX filesWhat am I missing here? What keeps putting that additional, and unwanted 192.168.179.102 address back on there?
____________________________________________________________ _______________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug