You are not logged in.

Pages: 1

#1 2015-06-14 16:53:29

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

[SOLVED] Multiple IP addresses accumulating

My system is accumulating IP addresses. Eventually, at about three, sometimes four, I get problems connecting to the internet because of this. I have to remove all the addresses and restart dhcpcd to get one IP. Then things work.

I can't say for sure, but it seems that this happens when I come out of a suspend. But I'm not sure what kind of hook might be a solution or if this is a bug ... or it's just something else I'm doing/not doing.

Right now, here's what my 

ip a

looks like:

2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d0:51:99:19:34:4e brd ff:ff:ff:ff:ff:ff
    inet 173.169.146.74/19 brd 255.255.255.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet 173.169.147.182/19 brd 173.169.159.255 scope global secondary dynamic enp5s0
       valid_lft 37321sec preferred_lft 37321sec

It works, but I know in a day or so I'll have three, then four IPs. When I get a new one, shouldn't the old one be automatically removed?

By default, dhcpcd.conf seems to have an option for "persistent".

     -p, --persistent
             dhcpcd normally de-configures the interface and configuration when it exits.  Some‐
             times, this isn't desirable if, for example, you have root mounted over NFS or SSH
             clients connect to this host and they need to be notified of the host shutting down.
             You can use this option to stop this from happening.

Should I remove this?

Last edited by HuckleSmothered (2015-06-27 13:20:00)

Offline

#2 2015-06-14 19:52:09

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

HuckleSmothered wrote:

It works, but I know in a day or so I'll have three, then four IPs. When I get a new one, shouldn't the old one be automatically removed?

...

By default, dhcpcd.conf seems to have an option for "persistent".

     -p, --persistent
             dhcpcd normally de-configures the interface and configuration when it exits.  Some‐
             times, this isn't desirable if, for example, you have root mounted over NFS or SSH
             clients connect to this host and they need to be notified of the host shutting down.
             You can use this option to stop this from happening.

Should I remove this?

Could you please state what version of dhcpcd you are using?
There was an issue with non removal of addresses in 6.9.0 which I have only recently fixed, but that was to do with the transition of IPv4LL addresses, not what you are describing. Still, it is possible it could be the same issuel.
Can you try the latest dhcpcd code please? Either clone the latest fossil head or download a trunk snapshot here: http://roy.marples.name/projects/dhcpcd (log as anonymous, the link is on that page).

I'm not sure removing persistent will address your issue as dhcpcd doesn't exist on suspend.
Well, I guess that's how it's configured I guess. If it's being started/stopped on carrier up/down by a third party such as ifplugd then it might fix it, otherwise probably not.

Offline

#3 2015-06-14 20:15:41

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

Current version: local/dhcpcd 6.9.0-1 (base)

I'll upgrade from the link you provided, test it out, and update soon.

Offline

#4 2015-06-15 17:05:14

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

I first tried to disable the "persistent" setting. Suspended the computer, came back up and there was an additional IP address.

Uninstalled dhcpcd and installed the fossil head instance from the link. I cleared any IPs I had, ensured no dhcpcd service was running, then started up the new fossil head one. This gave me an IP. I suspended my computer, resumed it, and I had a 2nd IP.

When I checked the version of the fossil head install I got from the link provided, it still showed as 6.9.0. I'm assuming I did something wrong.

Offline

#5 2015-06-15 19:15:04

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

HuckleSmothered wrote:

When I checked the version of the fossil head install I got from the link provided, it still showed as 6.9.0. I'm assuming I did something wrong.

I haven't worked out how to embed the fossil revision into the version number for snapshot releases yet, while keeping it out for proper releases AND making this easy to use for me.
I think I need to test if VERSION == fossil tag of latest revision. That may work.

My latest version also shows 6.9.0 smile

On a side note, you should be able to replicate this by bringing the carrier down and up again instead of suspending / resuming.
I'll see if I can work on a fix.
In the meantime I would appreciate it if you filed a ticked for this on my project page incase I forget smile

Offline

#6 2015-06-15 21:21:02

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

OK, I cannot replicate this (sadly I don't have a linux on my laptop, just the BSDs) but I'm sure it's not suspend / resume specific.
Can you add the debug directive to dhcpcd.conf and obtain a syslog of dhcpcd resuming please so I can see the order of events where dhcpcd adds an ip address, get a different one on resume and fails to remove the old one?

Thanks

Offline

#7 2015-06-16 01:26:40

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

Created ticket uid: 2b46dcdce251f1046beac01ef4aba2127e2621df on your site.

Initially I thought it was related to suspend/resume. You suggested bringing the carrier down then up. Before I tested this, I had another IP added to my system (without a suspend/resume either).

So ... I added -d to my /usr/lib/systemd/system/dhcpcd.service file. Reloaded the service daemons, then restarted dhcpcd. I got one IP. I suspended (because it's easy for me to do to get another IP), and resumed to find two IPs.

Funny thing, the journalctl _SYSTEMD_UNIT=dhcpcd.service doesn't show the second IP address. Not sure why ... maybe it is not dhcpcd. I dunno.

Jun 15 20:29:06 box dhcpcd[14333]: dhcpcd-6.9.0 starting
Jun 15 20:29:06 box dhcpcd[14333]: forking to background
Jun 15 20:29:06 box dhcpcd[14333]: forked to background, child pid 14334
Jun 15 20:29:06 box dhcpcd[14334]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 15 20:29:06 box dhcpcd[14334]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 15 20:29:06 box dhcpcd[14334]: DUID 00:01:00:01:1d:11:7b:d6:d0:50:99:09:33:4e
Jun 15 20:29:06 box dhcpcd[14334]: enp5s0: IAID 99:09:33:4e
Jun 15 20:29:06 box dhcpcd[14334]: enp5s0: delaying IPv6 router solicitation for 0.8 seconds
Jun 15 20:29:06 box dhcpcd[14334]: enp5s0: delaying IPv4 for 0.9 seconds
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: IAID a5:28:2d:71
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: delaying IPv6 router solicitation for 0.5 seconds
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: delaying IPv4 for 0.1 seconds
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: soliciting a DHCP lease
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 4.2 seconds
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: soliciting an IPv6 router
Jun 15 20:29:06 box dhcpcd[14334]: wlp2s0: sending Router Solicitation
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: soliciting an IPv6 router
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: sending Router Solicitation
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: reading lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: rebinding lease of 173.169.144.3
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: sending REQUEST (xid 0xb9347333), next in 4.5 seconds
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: acknowledged 173.169.144.3 from 10.126.64.1
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: leased 173.169.144.3 for 37083 seconds
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: renew in 18541 seconds, rebind in 32447 seconds
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: writing lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: adding IP address 173.169.144.3/19
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: adding route to 173.169.128.0/19
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: adding default route via 173.169.128.1
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' REBOOT
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: ARP announcing 173.169.144.3 (1 of 2), next in 2.0 seconds
Jun 15 20:29:07 box dhcpcd[14334]: enp5s0: removing route to 173.169.128.0/19
Jun 15 20:29:09 box dhcpcd[14334]: enp5s0: ARP announcing 173.169.144.3 (2 of 2)
Jun 15 20:29:10 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 7.7 seconds
Jun 15 20:29:10 box dhcpcd[14334]: wlp2s0: sending Router Solicitation
Jun 15 20:29:11 box dhcpcd[14334]: enp5s0: sending Router Solicitation
Jun 15 20:29:14 box dhcpcd[14334]: wlp2s0: sending Router Solicitation
Jun 15 20:29:15 box dhcpcd[14334]: enp5s0: sending Router Solicitation
Jun 15 20:29:18 box dhcpcd[14334]: enp5s0: xid 0x2e6 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:29:18 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 16.8 seconds
Jun 15 20:29:18 box dhcpcd[14334]: wlp2s0: sending Router Solicitation
Jun 15 20:29:18 box dhcpcd[14334]: wlp2s0: no IPv6 Routers available
Jun 15 20:29:19 box dhcpcd[14334]: enp5s0: sending Router Solicitation
Jun 15 20:29:19 box dhcpcd[14334]: enp5s0: no IPv6 Routers available
Jun 15 20:29:26 box dhcpcd[14334]: enp5s0: xid 0xb89 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:29:35 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 32.6 seconds
Jun 15 20:29:43 box dhcpcd[14334]: enp5s0: xid 0x2e7 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:29:44 box dhcpcd[14334]: enp5s0: xid 0x11702c20 is for hwaddr 00:0c:41:a8:61:cd:00:00:00:00:00:00:00:00:00:00
Jun 15 20:29:45 box dhcpcd[14334]: enp5s0: xid 0x11702c21 is for hwaddr 00:0c:41:a8:61:cd:00:00:00:00:00:00:00:00:00:00
Jun 15 20:30:07 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 63.4 seconds
Jun 15 20:30:08 box dhcpcd[14334]: enp5s0: xid 0x3b is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:30:16 box dhcpcd[14334]: enp5s0: xid 0x8de is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:30:34 box dhcpcd[14334]: enp5s0: xid 0x1e283b6d is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 15 20:30:52 box dhcpcd[14334]: enp5s0: xid 0x933951af is for hwaddr 74:86:7a:5e:40:78:00:00:00:00:00:00:00:00:00:00
Jun 15 20:31:06 box dhcpcd[14334]: enp5s0: xid 0x633 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:31:11 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 63.4 seconds
Jun 15 20:31:23 box dhcpcd[14334]: enp5s0: xid 0x24a0 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:31:36 box dhcpcd[14334]: enp5s0: xid 0x1e283b70 is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 15 20:31:48 box dhcpcd[14334]: enp5s0: xid 0x21f4 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:31:56 box dhcpcd[14334]: enp5s0: xid 0x388 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:08 box dhcpcd[14334]: enp5s0: xid 0x67730c28 is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:09 box dhcpcd[14334]: enp5s0: xid 0x67730c29 is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:13 box dhcpcd[14334]: enp5s0: xid 0x21f5 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:14 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 64.1 seconds
Jun 15 20:32:38 box dhcpcd[14334]: enp5s0: xid 0x1f48 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:39 box dhcpcd[14334]: enp5s0: xid 0x19b2dba8 is for hwaddr dc:0e:a1:af:ad:22:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:39 box dhcpcd[14334]: enp5s0: xid 0x19b2dba8 is for hwaddr dc:0e:a1:af:ad:22:00:00:00:00:00:00:00:00:00:00
Jun 15 20:32:46 box dhcpcd[14334]: enp5s0: xid 0xdc is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:03 box dhcpcd[14334]: enp5s0: xid 0x1f49 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:14 box dhcpcd[14334]: enp5s0: xid 0x44c9b188 is for hwaddr 2c:9e:5f:55:70:16:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:16 box dhcpcd[14334]: enp5s0: xid 0x44c9b188 is for hwaddr 2c:9e:5f:55:70:16:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:18 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 64.7 seconds
Jun 15 20:33:28 box dhcpcd[14334]: enp5s0: xid 0x1c9d is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:35 box dhcpcd[14334]: enp5s0: xid 0x44c9b189 is for hwaddr 2c:9e:5f:55:70:17:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:36 box dhcpcd[14334]: enp5s0: xid 0x2541 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:37 box dhcpcd[14334]: enp5s0: xid 0x44c9b189 is for hwaddr 2c:9e:5f:55:70:17:00:00:00:00:00:00:00:00:00:00
Jun 15 20:33:53 box dhcpcd[14334]: enp5s0: xid 0x1c9e is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:34:09 box dhcpcd[14334]: enp5s0: xid 0x3d8 is for hwaddr 68:9c:e2:51:7f:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:34:13 box dhcpcd[14334]: enp5s0: xid 0x3d8 is for hwaddr 68:9c:e2:51:7f:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:34:17 box dhcpcd[14334]: enp5s0: xid 0x3d8 is for hwaddr 68:9c:e2:51:7f:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:34:18 box dhcpcd[14334]: enp5s0: xid 0x19f1 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:34:23 box dhcpcd[14334]: wlp2s0: sending DISCOVER (xid 0xf0a00a0f), next in 64.2 seconds
Jun 15 20:34:26 box dhcpcd[14334]: enp5s0: xid 0x2296 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:35:08 box dhcpcd[14334]: enp5s0: xid 0x1746 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:35:09 box dhcpcd[14716]: sending signal TERM to pid 14334
Jun 15 20:35:09 box dhcpcd[14716]: waiting for pid 14334 to exit
Jun 15 20:35:09 box dhcpcd[14334]: received SIGTERM, stopping
Jun 15 20:35:09 box dhcpcd[14334]: wlp2s0: removing interface
Jun 15 20:35:09 box dhcpcd[14334]: enp5s0: adding route to 173.169.128.0/19
Jun 15 20:35:09 box dhcpcd[14334]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Jun 15 20:35:09 box dhcpcd[14334]: enp5s0: removing interface
Jun 15 20:35:09 box dhcpcd[14334]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Jun 15 20:35:09 box dhcpcd[14716]: sending signal TERM to pid 14334
Jun 15 20:35:09 box dhcpcd[14716]: waiting for pid 14334 to exit
Jun 15 20:35:27 box dhcpcd[14854]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 15 20:35:27 box dhcpcd[14854]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Jun 15 20:35:28 box dhcpcd[14854]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 15 20:35:28 box dhcpcd[14854]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: waiting for carrier
Jun 15 20:35:28 box dhcpcd[14854]: wlp2s0: waiting for carrier
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: carrier acquired
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 15 20:35:28 box dhcpcd[14854]: DUID 00:01:00:01:1d:11:7b:d6:d0:50:99:09:33:4e
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: IAID 99:09:33:4e
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: delaying IPv6 router solicitation for 0.5 seconds
Jun 15 20:35:28 box dhcpcd[14854]: enp5s0: delaying IPv4 for 0.8 seconds
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: soliciting an IPv6 router
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: sending Router Solicitation
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: reading lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: rebinding lease of 173.169.144.3
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: sending REQUEST (xid 0xfa8632e6), next in 4.6 seconds
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: acknowledged 173.169.144.3 from 10.126.64.1
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: leased 173.169.144.3 for 36699 seconds
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: renew in 18349 seconds, rebind in 32111 seconds
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: writing lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: IP address 173.169.144.3/19 already exists
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: changing route to 173.169.128.0/19
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: adding default route via 173.169.128.1
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' REBOOT
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: ARP announcing 173.169.144.3 (1 of 2), next in 2.0 seconds
Jun 15 20:35:29 box dhcpcd[14854]: enp5s0: removing default route via 173.169.128.1
Jun 15 20:35:30 box dhcpcd[14854]: enp5s0: xid 0x863656b9 is for hwaddr b8:97:5a:38:d6:a3:00:00:00:00:00:00:00:00:00:00
Jun 15 20:35:31 box dhcpcd[14854]: enp5s0: ARP announcing 173.169.144.3 (2 of 2)
Jun 15 20:35:33 box dhcpcd[14854]: enp5s0: xid 0x47608efb is for hwaddr b0:77:ac:97:4c:bd:00:00:00:00:00:00:00:00:00:00
Jun 15 20:35:33 box dhcpcd[14854]: enp5s0: xid 0x1747 is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:35:33 box dhcpcd[14854]: enp5s0: sending Router Solicitation
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: carrier acquired
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: IAID a5:28:2d:71
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: delaying IPv6 router solicitation for 0.2 seconds
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: delaying IPv4 for 0.5 seconds
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: soliciting an IPv6 router
Jun 15 20:35:33 box dhcpcd[14854]: wlp2s0: sending Router Solicitation
Jun 15 20:35:34 box dhcpcd[14854]: wlp2s0: soliciting a DHCP lease
Jun 15 20:35:34 box dhcpcd[14854]: wlp2s0: sending DISCOVER (xid 0x6760dacf), next in 4.8 seconds
Jun 15 20:35:37 box dhcpcd[14854]: enp5s0: sending Router Solicitation
Jun 15 20:35:37 box dhcpcd[14854]: wlp2s0: sending Router Solicitation
Jun 15 20:35:38 box dhcpcd[14854]: wlp2s0: sending DISCOVER (xid 0x6760dacf), next in 8.3 seconds
Jun 15 20:35:41 box dhcpcd[14854]: enp5s0: sending Router Solicitation
Jun 15 20:35:41 box dhcpcd[14854]: enp5s0: no IPv6 Routers available
Jun 15 20:35:41 box dhcpcd[14854]: wlp2s0: sending Router Solicitation
Jun 15 20:35:45 box dhcpcd[14854]: wlp2s0: sending Router Solicitation
Jun 15 20:35:45 box dhcpcd[14854]: wlp2s0: no IPv6 Routers available
Jun 15 20:35:47 box dhcpcd[14854]: wlp2s0: sending DISCOVER (xid 0x6760dacf), next in 16.6 seconds
Jun 15 20:35:57 box dhcpcd[14854]: enp5s0: xid 0x149a is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:36:03 box dhcpcd[14854]: wlp2s0: sending DISCOVER (xid 0x6760dacf), next in 32.2 seconds
Jun 15 20:36:06 box dhcpcd[14854]: enp5s0: xid 0x1d40 is for hwaddr e0:2f:6d:ff:75:04:00:00:00:00:00:00:00:00:00:00
Jun 15 20:36:23 box dhcpcd[14854]: enp5s0: xid 0x149b is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00
Jun 15 20:36:36 box dhcpcd[14854]: wlp2s0: sending DISCOVER (xid 0x6760dacf), next in 64.3 seconds
Jun 15 20:36:47 box dhcpcd[14854]: enp5s0: xid 0x11ef is for hwaddr dc:a5:f4:04:d6:a0:00:00:00:00:00:00:00:00:00:00

Offline

#8 2015-06-20 13:26:02

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

I captured where I renewed a lease for 16307 seconds (4.5 hours?). This was at 10:23pm. The computer was suspended. In the morning, around 8:38am it is offered a different IP. My "$ip a" still shows the old IP though.

There is a mention that the expired lease is discarded at 8:38am. Seems it is not totally discarding it, however. 

Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: discarding expired lease

$ip a

2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d0:50:99:09:33:4e brd ff:ff:ff:ff:ff:ff
    inet 173.170.238.109/21 brd 255.255.255.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet 173.169.204.187/20 brd 173.169.207.255 scope global dynamic enp5s0
       valid_lft 1336sec preferred_lft 1336sec
    inet 173.169.202.251/20 brd 255.255.255.255 scope global secondary enp5s0
       valid_lft forever preferred_lft forever

$journalctl -u dhcpcd.service -e |pcregrep 'enp5s0'

Jun 19 22:23:14 box dhcpcd[29044]: enp5s0: renewing lease of 173.170.238.109
Jun 19 22:23:14 box dhcpcd[29044]: enp5s0: rebind in 12230 seconds, expire in 16307 seconds
Jun 19 22:23:14 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 3.3 seconds
Jun 19 22:23:17 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 7.9 seconds
Jun 19 22:23:25 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 16.1 seconds
Jun 19 22:23:40 box dhcpcd[29044]: enp5s0: xid 0x59337b86 is for hwaddr 00:26:6c:49:91:db:00:00:00:00:00:00:00:00:00:00
Jun 19 22:23:40 box dhcpcd[29044]: enp5s0: xid 0x59337b86 is for hwaddr 00:26:6c:49:91:db:00:00:00:00:00:00:00:00:00:00
Jun 19 22:23:41 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 31.7 seconds
Jun 19 22:24:02 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:03 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:06 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:09 box dhcpcd[29044]: enp5s0: xid 0x1e286072 is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:10 box dhcpcd[29044]: enp5s0: xid 0x49192669 is for hwaddr 00:23:69:a3:4b:1d:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:10 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:12 box dhcpcd[29044]: enp5s0: xid 0x4919266a is for hwaddr 00:23:69:a3:4b:1d:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:13 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.7 seconds
Jun 19 22:24:19 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:24:35 box dhcpcd[29044]: enp5s0: xid 0x27acfe40 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:25:17 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.3 seconds
Jun 19 22:26:01 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:26:02 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:26:05 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:26:09 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:26:18 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:26:21 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.5 seconds
Jun 19 22:26:34 box dhcpcd[29044]: enp5s0: xid 0x27aecf18 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:27:12 box dhcpcd[29044]: enp5s0: xid 0x6ecf30 is for hwaddr 00:11:2f:50:49:d5:00:00:00:00:00:00:00:00:00:00
Jun 19 22:27:13 box dhcpcd[29044]: enp5s0: xid 0x6ecf31 is for hwaddr 00:11:2f:50:49:d5:00:00:00:00:00:00:00:00:00:00
Jun 19 22:27:24 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.4 seconds
Jun 19 22:27:35 box dhcpcd[29044]: enp5s0: xid 0x633d1dd9 is for hwaddr e2:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:27:51 box dhcpcd[29044]: enp5s0: xid 0x7623be6c is for hwaddr b8:ac:6f:e6:85:a5:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:00 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:01 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:04 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:08 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:17 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:28 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.1 seconds
Jun 19 22:28:33 box dhcpcd[29044]: enp5s0: xid 0x27b09ff0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:44 box dhcpcd[29044]: enp5s0: xid 0x7c84a9c9 is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
Jun 19 22:28:45 box dhcpcd[29044]: enp5s0: xid 0x7c84a9ca is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
Jun 19 22:29:32 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.2 seconds
Jun 19 22:29:59 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:00 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:03 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:07 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:16 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:24 box dhcpcd[29044]: enp5s0: xid 0x1e28607d is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:31 box dhcpcd[29044]: enp5s0: xid 0x727bc53b is for hwaddr b0:77:ac:97:33:af:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:32 box dhcpcd[29044]: enp5s0: xid 0x27b270c8 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:36 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.9 seconds
Jun 19 22:30:54 box dhcpcd[29044]: enp5s0: xid 0x3f0ead8a is for hwaddr 00:12:17:4c:e2:0d:00:00:00:00:00:00:00:00:00:00
Jun 19 22:30:59 box dhcpcd[29044]: enp5s0: xid 0x3f0ead8a is for hwaddr 00:12:17:4c:e2:0d:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:01 box dhcpcd[29044]: enp5s0: xid 0x7dd9d4a4 is for hwaddr 00:12:17:4c:e2:0d:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:02 box dhcpcd[29044]: enp5s0: xid 0x727bc53e is for hwaddr b0:77:ac:97:33:af:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:04 box dhcpcd[29044]: enp5s0: xid 0xfb22c795 is for hwaddr 9c:8e:99:ec:4e:f5:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:04 box dhcpcd[29044]: enp5s0: xid 0xfb22c795 is for hwaddr 9c:8e:99:ec:4e:f5:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:24 box dhcpcd[29044]: enp5s0: xid 0x1e286080 is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:30 box dhcpcd[29044]: enp5s0: xid 0xcccb3a94 is for hwaddr 78:e3:b5:b8:4c:02:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:34 box dhcpcd[29044]: enp5s0: xid 0x7151 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:36 box dhcpcd[29044]: enp5s0: xid 0x7151 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:41 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.1 seconds
Jun 19 22:31:50 box dhcpcd[29044]: enp5s0: xid 0xc50 is for hwaddr 1c:1d:86:35:4a:00:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:51 box dhcpcd[29044]: enp5s0: xid 0xc50 is for hwaddr 1c:1d:86:35:4a:00:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:58 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:31:59 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:02 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:06 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:15 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:31 box dhcpcd[29044]: enp5s0: xid 0x27b441a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:32 box dhcpcd[29044]: enp5s0: xid 0x2976042d is for hwaddr 00:26:18:1a:a9:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:44 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.4 seconds
Jun 19 22:32:54 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:32:54 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:33:49 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.7 seconds
Jun 19 22:33:57 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:33:58 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:01 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:05 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:12 box dhcpcd[29044]: enp5s0: xid 0x1e286084 is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:14 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:30 box dhcpcd[29044]: enp5s0: xid 0x27b61278 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:34:52 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.1 seconds
Jun 19 22:35:55 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.7 seconds
Jun 19 22:35:56 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:35:57 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:00 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:04 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:13 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:15 box dhcpcd[29044]: enp5s0: xid 0x119f is for hwaddr 68:9c:e2:51:be:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:15 box dhcpcd[29044]: enp5s0: xid 0x119f is for hwaddr 68:9c:e2:51:be:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:29 box dhcpcd[29044]: enp5s0: xid 0x27b7e350 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:36:30 box dhcpcd[29044]: enp5s0: xid 0x2c402154 is for hwaddr 10:bf:48:d4:df:dd:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:00 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.4 seconds
Jun 19 22:37:16 box dhcpcd[29044]: enp5s0: xid 0x7b7aa96 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:16 box dhcpcd[29044]: enp5s0: xid 0x7b7aa96 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:21 box dhcpcd[29044]: enp5s0: xid 0x450b656c is for hwaddr c0:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:30 box dhcpcd[29044]: enp5s0: xid 0x1124 is for hwaddr 00:18:39:61:95:7e:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:30 box dhcpcd[29044]: enp5s0: xid 0x1124 is for hwaddr 00:18:39:61:95:7e:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:51 box dhcpcd[29044]: enp5s0: xid 0x4760b8bd is for hwaddr b0:77:ac:97:4c:bd:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:53 box dhcpcd[29044]: enp5s0: xid 0x6d90864a is for hwaddr 2c:9e:5f:57:25:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:56 box dhcpcd[29044]: enp5s0: xid 0x4760b8bf is for hwaddr b0:77:ac:97:4c:bd:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:56 box dhcpcd[29044]: enp5s0: xid 0x27b9b428 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:37:59 box dhcpcd[29044]: enp5s0: xid 0x27b9b428 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:01 box dhcpcd[29044]: enp5s0: xid 0x4760b8c0 is for hwaddr b0:77:ac:97:4c:bd:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:01 box dhcpcd[29044]: enp5s0: xid 0x6d90864c is for hwaddr 2c:9e:5f:57:25:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:01 box dhcpcd[29044]: enp5s0: xid 0x6d90864d is for hwaddr 2c:9e:5f:57:25:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:01 box dhcpcd[29044]: enp5s0: xid 0x6d90864f is for hwaddr 2c:9e:5f:57:25:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:03 box dhcpcd[29044]: enp5s0: xid 0x27b9b428 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:05 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.8 seconds
Jun 19 22:38:08 box dhcpcd[29044]: enp5s0: xid 0x1e28608c is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:12 box dhcpcd[29044]: enp5s0: xid 0x27b9b428 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:28 box dhcpcd[29044]: enp5s0: xid 0x27b9b428 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:31 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:38:31 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:08 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 65.0 seconds
Jun 19 22:39:09 box dhcpcd[29044]: enp5s0: xid 0x1e28608e is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:16 box dhcpcd[29044]: enp5s0: xid 0x2c8cd622 is for hwaddr 7c:bf:b1:c7:a3:04:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:18 box dhcpcd[29044]: enp5s0: xid 0x2c8cd622 is for hwaddr 7c:bf:b1:c7:a3:04:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:18 box dhcpcd[29044]: enp5s0: xid 0x21787a3 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:18 box dhcpcd[29044]: enp5s0: xid 0x21787a3 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:43 box dhcpcd[29044]: enp5s0: xid 0x1e28608f is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:46 box dhcpcd[29044]: enp5s0: xid 0x2c8cd623 is for hwaddr 7c:bf:b1:c7:a3:05:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:48 box dhcpcd[29044]: enp5s0: xid 0x2c8cd623 is for hwaddr 7c:bf:b1:c7:a3:05:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:51 box dhcpcd[29044]: enp5s0: xid 0x69cb5323 is for hwaddr 30:b5:c2:e4:e2:a7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:51 box dhcpcd[29044]: enp5s0: xid 0x69cb5323 is for hwaddr 30:b5:c2:e4:e2:a7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:54 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:55 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:39:57 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:40:02 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:40:10 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:40:13 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.5 seconds
Jun 19 22:40:27 box dhcpcd[29044]: enp5s0: xid 0x27bb8500 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:17 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.2 seconds
Jun 19 22:41:20 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:20 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:54 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:55 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:57 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:59 box dhcpcd[29044]: enp5s0: xid 0x2477674e is for hwaddr c8:be:19:6c:9c:2e:00:00:00:00:00:00:00:00:00:00
Jun 19 22:41:59 box dhcpcd[29044]: enp5s0: xid 0x2477674e is for hwaddr c8:be:19:6c:9c:2e:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:02 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:10 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:11 box dhcpcd[29044]: enp5s0: xid 0x72b475c is for hwaddr 00:08:0d:11:32:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:11 box dhcpcd[29044]: enp5s0: xid 0x72b475c is for hwaddr 00:08:0d:11:32:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:13 box dhcpcd[29044]: enp5s0: xid 0x5b4cf3d1 is for hwaddr f8:0f:41:11:59:d2:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:13 box dhcpcd[29044]: enp5s0: xid 0x5b4cf3d1 is for hwaddr f8:0f:41:11:59:d2:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:20 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 65.0 seconds
Jun 19 22:42:23 box dhcpcd[29044]: enp5s0: xid 0xed84eef4 is for hwaddr e2:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:27 box dhcpcd[29044]: enp5s0: xid 0x27bd59c0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:45 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:42:45 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:19 box dhcpcd[29044]: enp5s0: xid 0x5f6a31d8 is for hwaddr b0:77:ac:96:35:b7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:21 box dhcpcd[29044]: enp5s0: xid 0x5f6a31d8 is for hwaddr b0:77:ac:96:35:b7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:25 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.7 seconds
Jun 19 22:43:26 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:26 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:40 box dhcpcd[29044]: enp5s0: xid 0x14bd is for hwaddr 1c:1d:86:35:30:80:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:40 box dhcpcd[29044]: enp5s0: xid 0x14bd is for hwaddr 1c:1d:86:35:30:80:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:47 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:47 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:53 box dhcpcd[29044]: enp5s0: xid 0x9024f0ec is for hwaddr c0:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:54 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:54 box dhcpcd[29044]: enp5s0: xid 0x7f0c146c is for hwaddr 88:5a:92:60:47:09:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:54 box dhcpcd[29044]: enp5s0: xid 0x7f0c146c is for hwaddr 88:5a:92:60:47:09:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:55 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:57 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:58 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:43:58 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:02 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:03 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:03 box dhcpcd[29044]: enp5s0: xid 0x5fb27570 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:06 box dhcpcd[29044]: enp5s0: xid 0xd0e4a018 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:06 box dhcpcd[29044]: enp5s0: xid 0xd0e4a018 is for hwaddr 90:94:e4:b0:4a:23:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:10 box dhcpcd[29044]: enp5s0: xid 0x1a3bf287 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:10 box dhcpcd[29044]: enp5s0: xid 0x1a3bf287 is for hwaddr 00:08:0d:47:48:45:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:10 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:27 box dhcpcd[29044]: enp5s0: xid 0x27bf2e80 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:44:29 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.0 seconds
Jun 19 22:45:08 box dhcpcd[29044]: enp5s0: xid 0x1a97 is for hwaddr 50:1c:bf:49:66:e0:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:08 box dhcpcd[29044]: enp5s0: xid 0x1a97 is for hwaddr 50:1c:bf:49:66:e0:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:33 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.3 seconds
Jun 19 22:45:40 box dhcpcd[29044]: enp5s0: xid 0xe185b631 is for hwaddr 38:60:77:4b:b9:c3:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:42 box dhcpcd[29044]: enp5s0: xid 0xe185b631 is for hwaddr 38:60:77:4b:b9:c3:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:52 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:54 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:45:57 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:46:01 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:46:09 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:46:26 box dhcpcd[29044]: enp5s0: xid 0x27c0ff58 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:46:36 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.6 seconds
Jun 19 22:46:50 box dhcpcd[29044]: enp5s0: xid 0x687a590 is for hwaddr 00:08:0d:11:32:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:46:50 box dhcpcd[29044]: enp5s0: xid 0x687a590 is for hwaddr 00:08:0d:11:32:40:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:03 box dhcpcd[29044]: enp5s0: xid 0xcab6e6f8 is for hwaddr a0:d3:c1:0d:18:58:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:03 box dhcpcd[29044]: enp5s0: xid 0xcab6e6f8 is for hwaddr a0:d3:c1:0d:18:58:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:18 box dhcpcd[29044]: enp5s0: xid 0xc47b3501 is for hwaddr c8:1f:66:00:ac:dd:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:36 box dhcpcd[29044]: enp5s0: xid 0x1157a9a1 is for hwaddr 00:90:a9:ae:07:90:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:36 box dhcpcd[29044]: enp5s0: xid 0x1157a9a1 is for hwaddr 00:90:a9:ae:07:90:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:41 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.8 seconds
Jun 19 22:47:51 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:53 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:47:55 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:48:00 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:48:08 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:48:25 box dhcpcd[29044]: enp5s0: xid 0x27c2d030 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:48:45 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.7 seconds
Jun 19 22:48:51 box dhcpcd[29044]: enp5s0: xid 0xe319c45e is for hwaddr e2:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:10 box dhcpcd[29044]: enp5s0: xid 0x1e2860a0 is for hwaddr b0:77:ac:97:48:f4:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:23 box dhcpcd[29044]: enp5s0: xid 0x9024ce0d is for hwaddr 4c:72:b9:b0:b4:6f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:49 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 65.0 seconds
Jun 19 22:49:50 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:52 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:54 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:49:59 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:07 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:12 box dhcpcd[29044]: enp5s0: xid 0x2961ef4e is for hwaddr 00:19:b9:55:48:d7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:12 box dhcpcd[29044]: enp5s0: xid 0x2961ef4e is for hwaddr 00:19:b9:55:48:d7:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:20 box dhcpcd[29044]: enp5s0: xid 0xf039cbcc is for hwaddr 78:2b:cb:83:09:3b:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:20 box dhcpcd[29044]: enp5s0: xid 0xf039cbcc is for hwaddr 78:2b:cb:83:09:3b:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:24 box dhcpcd[29044]: enp5s0: xid 0x27c4a108 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:48 box dhcpcd[29044]: enp5s0: xid 0xcf81d992 is for hwaddr c0:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
Jun 19 22:50:54 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.5 seconds
Jun 19 22:51:30 box dhcpcd[29044]: enp5s0: xid 0x7ff6a20c is for hwaddr 78:24:af:c5:d3:cb:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:30 box dhcpcd[29044]: enp5s0: xid 0x7ff6a20c is for hwaddr 78:24:af:c5:d3:cb:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:49 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:51 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:53 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:58 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:51:59 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.2 seconds
Jun 19 22:52:06 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:52:23 box dhcpcd[29044]: enp5s0: xid 0x27c671e0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:53:03 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.6 seconds
Jun 19 22:53:49 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:53:51 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:53:53 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:53:58 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:07 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:08 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 63.4 seconds
Jun 19 22:54:14 box dhcpcd[29044]: enp5s0: xid 0x616c9a12 is for hwaddr 94:cc:b9:4c:24:46:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:16 box dhcpcd[29044]: enp5s0: xid 0x616c9a12 is for hwaddr 94:cc:b9:4c:24:46:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:23 box dhcpcd[29044]: enp5s0: xid 0x27c846a0 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:36 box dhcpcd[29044]: enp5s0: xid 0x616c9a13 is for hwaddr 94:cc:b9:4c:24:47:00:00:00:00:00:00:00:00:00:00
Jun 19 22:54:38 box dhcpcd[29044]: enp5s0: xid 0x616c9a13 is for hwaddr 94:cc:b9:4c:24:47:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:11 box dhcpcd[29044]: enp5s0: sending REQUEST (xid 0xcc10d39d), next in 64.4 seconds
Jun 19 22:55:33 box dhcpcd[29044]: enp5s0: xid 0x2bcbcb05 is for hwaddr 00:26:18:1a:a9:3f:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:38 box dhcpcd[29044]: enp5s0: xid 0xab03591e is for hwaddr 50:e5:49:ee:08:47:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:48 box dhcpcd[29044]: enp5s0: xid 0x27ca1778 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:50 box dhcpcd[29044]: enp5s0: xid 0x27ca1778 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:52 box dhcpcd[29044]: enp5s0: xid 0x27ca1778 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:55:57 box dhcpcd[29044]: enp5s0: xid 0x27ca1778 is for hwaddr 00:0f:66:a3:be:57:00:00:00:00:00:00:00:00:00:00
Jun 19 22:56:02 box dhcpcd[29044]: enp5s0: adding route to 173.170.232.0/21
Jun 19 22:56:02 box dhcpcd[29044]: enp5s0: removing interface
Jun 19 22:56:02 box dhcpcd[29044]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Jun 20 08:38:48 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 20 08:38:48 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: waiting for carrier
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: carrier acquired
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: IAID 99:09:33:4e
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: delaying IPv6 router solicitation for 0.1 seconds
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: delaying IPv4 for 0.5 seconds
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: soliciting an IPv6 router
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: sending Router Solicitation
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: reading lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: discarding expired lease
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: soliciting a DHCP lease
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: sending DISCOVER (xid 0xe17bebd0), next in 3.8 seconds
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: offered 173.169.202.251 from 10.126.64.1
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: sending REQUEST (xid 0xe17bebd0), next in 4.5 seconds
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: acknowledged 173.169.202.251 from 10.126.64.1
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: leased 173.169.202.251 for 3600 seconds
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: renew in 1800 seconds, rebind in 3150 seconds
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: writing lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: adding IP address 173.169.202.251/20
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: adding route to 173.169.192.0/20
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: changing default route via 173.169.192.1
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: deleting route to 173.170.232.0/21
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' BOUND
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: ARP announcing 173.169.202.251 (1 of 2), next in 2.0 seconds
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: removing route to 173.169.192.0/20
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: removing default route via 173.169.192.1
Jun 20 08:38:52 box dhcpcd[31917]: enp5s0: ARP announcing 173.169.202.251 (2 of 2)
Jun 20 08:38:53 box dhcpcd[31917]: enp5s0: sending Router Solicitation
Jun 20 08:38:57 box dhcpcd[31917]: enp5s0: sending Router Solicitation
Jun 20 08:38:59 box dhcpcd[31917]: enp5s0: xid 0x6d908a8b is for hwaddr 2c:9e:5f:57:25:3f:00:00:00:00:00:00:00:00:00:00
Jun 20 08:39:01 box dhcpcd[31917]: enp5s0: sending Router Solicitation
Jun 20 08:39:01 box dhcpcd[31917]: enp5s0: no IPv6 Routers available

Offline

#9 2015-06-20 15:32:51

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,350

Re: [SOLVED] Multiple IP addresses accumulating

Your system is the DHCP server?  It is running dhcpcd and is (it seems) handing out addresses (I think) to about five different MAC addresses. 
Are there multiple DHCP servers running on the domain?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#10 2015-06-20 18:02:12

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

ewaller wrote:

Your system is the DHCP server?  It is running dhcpcd and is (it seems) handing out addresses (I think) to about five different MAC addresses. 
Are there multiple DHCP servers running on the domain?

DHCP messages are broadcast until both server and client agree on an address.
As such, each machine on the same network will see this traffic.

Most DHCP clients will close the DHCP port once an address is obtained as they no longer need it, but dhcpcd is the only (or was when i last looked) to support FORCE RENEW.
For this to work, it needs to keep the port open and thus you see this traffic when dhcpcd debugging is enabled.

Offline

#11 2015-06-20 18:10:07

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

Here is the key part. I trimmed some lines in the middle for brevity, but it still shows the problem I think.

Jun 19 22:56:02 box dhcpcd[29044]: enp5s0: removing interface
Jun 19 22:56:02 box dhcpcd[29044]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Jun 20 08:38:48 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jun 20 08:38:48 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Jun 20 08:38:49 box dhcpcd[31917]: enp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: reading lease `/var/lib/dhcpcd/dhcpcd-enp5s0.lease'
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: discarding expired lease
Jun 20 08:38:50 box dhcpcd[31917]: enp5s0: soliciting a DHCP lease

dhcpcd itself is not suspended.
Instead it is stopped and started again, which I find odd. Probably some software thinking it knows better than dhcpcd, but there we go. You would not see this issue if dhcpcd was left to its own devices.

dhcpcd only recently gained the ability to see if an old lease was assigned at boot time and clean it if needed, but as we can see it looks buggy (not proven this is the issue, just a guess) as the lease IS discarded correctly but the old IP address not removed.
I'll see if I can fix this over the next week.

Offline

#12 2015-06-20 18:41:12

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,350

Re: [SOLVED] Multiple IP addresses accumulating

Sorry, I had a senior moment.  Of course dhcpcd is the client.  I was thinking you were running hdcpd.   
Ignore the noise.

Edit:  But the question remains :  Any chance there are multiple DHCP servers on the network?

Last edited by ewaller (2015-06-20 18:42:37)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#13 2015-06-20 18:54:09

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

My box has two network cards; enp5s0 and wlp2s0. The wired enp5s0 is connected directly to the cable modem and gets the IP from that. The wireless wlp2s0 serves as a wireless access point to about five devices, yes. Hence, this box is a WAP and forwards traffic from wlp2s0 to enp5s0 (the interwebs). wlp2s0 runs dhcpd4 for the clients attaching there. The range that dhcpd4 provides IPs in is 10.1.1.*.

Offline

#14 2015-06-26 20:21:41

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

I think I now have this resolved!
If you could try a new trunk build (use the same link to download a refresh copy) and test it for me I would very much appreciate it smile

Offline

#15 2015-06-26 22:44:59

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

Just tested. It still added another address once the network was stopped and restarted.

1. Stopped and removed dhcpcd from distribution.
2. Downloaded and installed trunk version from this site (version says 6.9.0 but I'm assuming it installed ok ... shasum = d56ff256a65588bfdaa15739dec706ee09c5a9a7  /usr/bin/dhcpcd)
3. Started dhcpcd -Bdz enp5s0
4. Received an IP

    inet 173.169.145.49/19 brd 255.255.255.255 scope global enp5s0
       valid_lft forever preferred_lft forever

5. Restarted networking ($ systemctl restart systemd-networkd)
6. Immediately received another IP in addition to previous one.

    inet 173.169.145.49/19 brd 255.255.255.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet 173.169.146.190/19 brd 173.169.159.255 scope global secondary dynamic enp5s0
       valid_lft 42894sec preferred_lft 42894sec

The dhcpcd output did not mention this second address:

$ sudo dhcpcd -Bdz enp5s0

dhcpcd-6.9.0 starting
dev: loaded udev
enp5s0: executing `/libexec/dhcpcd-run-hooks' PREINIT
enp5s0: executing `/libexec/dhcpcd-run-hooks' CARRIER
DUID 00:01:00:01:1d:11:7b:d6:d0:50:99:09:33:4e
enp5s0: IAID 99:09:33:4e
enp5s0: delaying IPv6 router solicitation for 0.1 seconds
enp5s0: delaying IPv4 for 1.0 seconds
enp5s0: soliciting an IPv6 router
enp5s0: sending Router Solicitation
enp5s0: soliciting a DHCP lease
enp5s0: sending DISCOVER (xid 0x20bce2b9), next in 3.6 seconds
enp5s0: offered 173.169.145.49 from 10.126.64.1
enp5s0: sending REQUEST (xid 0x20bce2b9), next in 3.7 seconds
enp5s0: acknowledged 173.169.145.49 from 10.126.64.1
enp5s0: probing for 173.169.145.49
enp5s0: ARP probing 173.169.145.49 (1 of 3), next in 1.3 seconds
enp5s0: ARP probing 173.169.145.49 (2 of 3), next in 1.7 seconds
enp5s0: sending Router Solicitation
enp5s0: ARP probing 173.169.145.49 (3 of 3), next in 2.0 seconds
enp5s0: DAD completed for 173.169.145.49
enp5s0: leased 173.169.145.49 for 1967 seconds
enp5s0: renew in 983 seconds, rebind in 1721 seconds
enp5s0: writing lease `/var/db/dhcpcd-enp5s0.lease'
enp5s0: adding IP address 173.169.145.49/19
enp5s0: adding route to 173.169.128.0/19
enp5s0: adding default route via 173.169.128.1
enp5s0: executing `/libexec/dhcpcd-run-hooks' BOUND
enp5s0: ARP announcing 173.169.145.49 (1 of 2), next in 2.0 seconds
enp5s0: sending Router Solicitation
enp5s0: ARP announcing 173.169.145.49 (2 of 2)
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: sending Router Solicitation
enp5s0: no IPv6 Routers available
enp5s0: xid 0xb6f7fb29 is for hwaddr 98:fc:11:5c:e6:3b:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0xb6f7fb2a is for hwaddr 98:fc:11:5c:e6:3b:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x9b8143e0 is for hwaddr 00:13:10:30:e4:dc:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x9b8143e1 is for hwaddr 00:13:10:30:e4:dc:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x1a93 is for hwaddr 50:1c:bf:49:66:e0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x1a93 is for hwaddr 50:1c:bf:49:66:e0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0xd0 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x2533 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0xcbfdc860 is for hwaddr e2:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x2534 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x2288 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x2289 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x1fdc is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x1fdd is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x8004a4c is for hwaddr 00:08:0d:9e:d4:49:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x8004a4c is for hwaddr 00:08:0d:9e:d4:49:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x16cfb0f2 is for hwaddr 00:23:69:d6:72:a5:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x16cfb0f3 is for hwaddr 00:23:69:d6:72:a5:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0xe8f8cff7 is for hwaddr 34:23:87:11:d2:10:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x9b is for hwaddr 68:9c:e2:51:7f:a0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x9b is for hwaddr 68:9c:e2:51:7f:a0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x6500e9f3 is for hwaddr c0:18:85:8f:cd:13:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x17db is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x28e7311 is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x28e7312 is for hwaddr 00:21:29:9f:42:f3:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x1284 is for hwaddr 70:10:5c:b4:ff:c0:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00
enp5s0: xid 0x3317 is for hwaddr 00:16:b6:df:17:1a:00:00:00:00:00:00:00:00:00:00

$ systemctl status systemd-networkd

Jun 26 18:34:04 box systemd[1]: Starting Network Service...
Jun 26 18:34:04 box systemd-networkd[28828]: Enumeration completed
Jun 26 18:34:04 box systemd[1]: Started Network Service.
Jun 26 18:34:05 box systemd-networkd[28828]: enp5s0          : DHCPv4 address 173.169.146.190/19 via 173.169.128.1
Jun 26 18:34:05 box systemd-networkd[28828]: enp5s0          : link configured

Offline

#16 2015-06-26 22:54:29

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

Jun 26 18:34:05 box systemd-networkd[28828]: enp5s0          : DHCPv4 address 173.169.146.190/19 via 173.169.128.1

Could the problem be that you're running 2 DHCP clients? systemd-networkd and dhcpcd?

Offline

#17 2015-06-26 23:46:37

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

<sigh> Maybe.

I do not understand systemd as well as I should. I did not realize systemd-networkd was a dhcp client. It appears I was playing around with it on 6/19 and created a file to get addresses. Did I have this file before the 19th? I don't think so, but can't say for sure. I think this was part of my attempts to troubleshoot the accumulating IPs. But I apparently left it on.

I just tried to disable and stop it. Then remove the addresses and do a suspend/resume with only dhcpcd active and providing one IP. Oddly, systemd-networkd.service restarted despite being disabled and stopped. Apparently systemd-networkd.socket can start systemd-networkd.service. I disabled and stopped the socket, too. Then repeated the suspend/resume with dhcpcd active and providing one IP. As of now, I have only one IP.

Could all this be a really stupid mistake on my part because I was messing around with a systemd feature I did not fully understand? Yes. I'll update tomorrow morning with my IP status. I anticipate only one IP. If so, I owe Roy a few hours of his life back for troubleshooting and fixing a phantom bug.

Offline

#18 2015-06-27 13:19:48

HuckleSmothered
Member
Registered: 2010-03-25
Posts: 68

Re: [SOLVED] Multiple IP addresses accumulating

Only one IP this morning. PEBCAK ... problem exists between chair and keyboard.

Offline

#19 2015-06-27 15:20:02

rsmarples
Member
Registered: 2009-05-12
Posts: 287

Re: [SOLVED] Multiple IP addresses accumulating

Don't fret about the "wasted" hours, because they are not. Your report revealed real bugs in dhcpcd which are now solved smile

Offline

Pages: 1

Board footer

Powered by FluxBB