Carl Johnson on 9 Oct 2017 08:28:15 -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'm not sure what that interface was used for before. This server was a hand me down. It was put onto my desk, and I was told "Here, use this". :-)

You're close with the watchdog/outside management idea though. After a few hours of head scratching and hair pulling and looking for cron scripts and things like that, the light bulb went on for me. I thought... "Ahhh...right... this box has Centos 7 on it. Centos 7 uses systemd".

So then I just watched journalctl for a few mins after doing a "ip addr del 192.168.179.102/30 dev eth1". In addition to the standard /etc/sysconfig/network-scripts/ifcfg-ethx conf files, you can also put conf files (albeit in a slightly different format, kinda' like a windoze .ini file) into /etc/systemd/network.

(Sigh) Strike another line on the board for someone bitten by one of the those cursed systemd nuances.....
Anyhow, thanks for your and Rachel's input. Now I'm off to figure out MariaDB on this thing....




On Mon, Oct 9, 2017 at 10:18 AM, Keith C. Perry <kperry@daotechnologies.com> wrote:
What was the 192.168.179.102 previously used for?  Perhaps there is a service that is watching for that and is automatically adding it either locally on that system or remotely from another management service.


~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Keith C. Perry, MS E.E.
Managing Member, DAO Technologies LLC
www.daotechnologies.com


From: "Carl Johnson" <cjohnson19791979@gmail.com>
To: "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>, "rachelneko" <rachelneko@gmail.com>
Sent: Thursday, October 5, 2017 7:13:08 PM
Subject: Re: [PLUG] Two IP's on an interface. One won't go away.

Nope. This is on an Intel S2600 board actually.



On October 5, 2017 4:59:59 PM MDT, Rachel plays Linux <rachelneko@gmail.com> wrote:
Do you have a vm or single-board computer set up with network sharing? I know the beaglebone black defaults to a /30 address.





On Oct 5, 2017 6:34 PM, "Carl Johnson" <cjohnson19791979@gmail.com> wrote:
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 this
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 forever

If 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 forever

The 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 forever

See? 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 files


What 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

___________________________________________________________________________
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