[SOLVED] DHCP client connecting at random

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
ajgringo619

[SOLVED] DHCP client connecting at random

Post by ajgringo619 »

I got a new modem to replace my faulty one (from Cox) about a week ago. One of the first things I changed was to set the lease time to forever. While this seems to be working, I don't understand the following messages:

Code: Select all

Jul 25 13:29:53 dss-mint19-cinnamon dhclient[23799]: DHCPREQUEST of 192.168.0.11 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x4ad7632d)
Jul 25 13:29:54 dss-mint19-cinnamon NetworkManager[1400]: <info>  [1564086594.9817] dhcp6 (wlxbcec23100000): dhclient started with pid 23828
Jul 25 13:29:55 dss-mint19-cinnamon dhclient[23828]: XMT: Confirm on wlxbcec23100000, interval 1090ms.
Jul 25 13:29:55 dss-mint19-cinnamon dhclient[23828]: RCV: Reply message on wlxbcec23100000 from fe80::966a:77ff:fed5:d1a.
Jul 25 13:29:55 dss-mint19-cinnamon dhclient[23828]: message status code Success: "Your addresses are correct for this link! Yay!"
Jul 25 13:29:55 dss-mint19-cinnamon dhclient[23828]: PRC: Rebinding lease on wlxbcec23100000.
Jul 25 13:29:55 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 10740ms.
Jul 25 13:29:56 dss-mint19-cinnamon dhclient[23799]: DHCPREQUEST of 192.168.0.11 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x4ad7632d)
Jul 25 13:29:56 dss-mint19-cinnamon dhclient[23799]: DHCPACK of 192.168.0.11 from 192.168.0.1
Jul 25 13:29:56 dss-mint19-cinnamon dhclient[23799]: bound to 192.168.0.11 -- renewal in 2147483648 seconds.
Jul 25 13:30:06 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 21110ms.
Jul 25 13:30:27 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 42500ms.
Jul 25 13:31:10 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 87120ms.
Jul 25 13:32:37 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 177760ms.
Jul 25 13:35:35 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 340600ms.
Jul 25 13:36:05 dss-mint19-cinnamon sudo[28152]: summersd : TTY=pts/2 ; PWD=/etc/dhcp ; USER=root ; COMMAND=/usr/bin/vi dhclient.conf
Jul 25 13:41:16 dss-mint19-cinnamon dhclient[23828]: XMT: Rebind on wlxbcec23100000, interval 548380ms.
Jul 25 13:49:28 dss-mint19-cinnamon audit[1214]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1214 comm="apparmor_parser"
Jul 25 13:49:28 dss-mint19-cinnamon audit[1214]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1214 comm="apparmor_parser"
Jul 25 13:49:29 dss-mint19-cinnamon NetworkManager[1351]: <info>  [1564087769.1288] dhcp-init: Using DHCP client 'dhclient'
Jul 25 13:49:34 dss-mint19-cinnamon NetworkManager[1351]: <info>  [1564087774.3739] dhcp4 (wlxbcec23100000): dhclient started with pid 1957
Jul 25 13:49:34 dss-mint19-cinnamon dhclient[1957]: DHCPREQUEST of 192.168.0.11 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0xce2ace7)
Jul 25 13:49:34 dss-mint19-cinnamon dhclient[1957]: DHCPACK of 192.168.0.11 from 192.168.0.1
Jul 25 13:49:34 dss-mint19-cinnamon dhclient[1957]: bound to 192.168.0.11 -- renewal in 2147483648 seconds.
Jul 25 13:49:35 dss-mint19-cinnamon NetworkManager[1351]: <info>  [1564087775.9234] dhcp6 (wlxbcec23100000): dhclient started with pid 2049
Jul 25 13:49:36 dss-mint19-cinnamon dhclient[2049]: XMT: Confirm on wlxbcec23100000, interval 910ms.
Jul 25 13:49:36 dss-mint19-cinnamon dhclient[2049]: RCV: Reply message on wlxbcec23100000 from fe80::966a:77ff:fed5:d1a.
Jul 25 13:49:36 dss-mint19-cinnamon dhclient[2049]: message status code Success: "Your addresses are correct for this link! Yay!"
Jul 25 13:49:36 dss-mint19-cinnamon dhclient[2049]: PRC: Rebinding lease on wlxbcec23100000.
Jul 25 13:49:36 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 9650ms.
Jul 25 13:49:46 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 20250ms.
Jul 25 13:50:06 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 40260ms.
Jul 25 13:50:47 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 77200ms.
Jul 25 13:52:04 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 157890ms.
Jul 25 13:54:42 dss-mint19-cinnamon dhclient[2049]: XMT: Rebind on wlxbcec23100000, interval 303750ms.
There are a ton more of the Rebind messages; this is just in the last 25 minutes.

Now, with my previous modem, I went back and checked a month ago and none of the Rebind messages appeared:

Code: Select all

Jun 25 08:25:40 dss-mint19-xfce NetworkManager[1181]: <info>  [1561476340.0202] dhcp4 (wlxbcec23100000): dhclient started with pid 1655
Jun 25 08:25:40 dss-mint19-xfce dhclient[1655]: DHCPREQUEST of 192.168.0.10 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x73c77fef)
Jun 25 08:25:40 dss-mint19-xfce dhclient[1655]: DHCPACK of 192.168.0.10 from 192.168.0.1
Jun 25 08:25:40 dss-mint19-xfce dhclient[1655]: bound to 192.168.0.10 -- renewal in 35430 seconds.
Jun 25 08:25:42 dss-mint19-xfce NetworkManager[1181]: <info>  [1561476342.7490] dhcp6 (wlxbcec23100000): dhclient started with pid 1952
Jun 25 08:25:43 dss-mint19-xfce dhclient[1952]: XMT: Info-Request on wlxbcec23100000, interval 1000ms.
Jun 25 08:25:44 dss-mint19-xfce dhclient[1952]: XMT: Info-Request on wlxbcec23100000, interval 1920ms.
Jun 25 08:25:45 dss-mint19-xfce dhclient[1952]: RCV: Reply message on wlxbcec23100000 from fe80::3a70:cff:feca:8385.
Jun 25 15:53:25 dss-mint19-xfce NetworkManager[1181]: <info>  [1561503205.2072] dhcp4 (wlxbcec23100000): dhclient started with pid 13145
Jun 25 15:53:25 dss-mint19-xfce dhclient[13145]: DHCPREQUEST of 192.168.0.10 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x47a709f9)
Jun 25 15:53:25 dss-mint19-xfce dhclient[13145]: DHCPACK of 192.168.0.10 from 192.168.0.1
Jun 25 15:53:25 dss-mint19-xfce dhclient[13145]: bound to 192.168.0.10 -- renewal in 40878 seconds.
Jun 25 15:53:31 dss-mint19-xfce NetworkManager[1181]: <info>  [1561503211.0842] dhcp6 (wlxbcec23100000): dhclient started with pid 13402
Jun 25 15:53:31 dss-mint19-xfce dhclient[13402]: XMT: Info-Request on wlxbcec23100000, interval 940ms.
Jun 25 15:53:31 dss-mint19-xfce dhclient[13402]: RCV: Reply message on wlxbcec23100000 from fe80::3a70:cff:feca:8385.
Jun 25 17:03:09 dss-mint19-xfce audit[1097]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Jun 25 17:03:09 dss-mint19-xfce audit[1097]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1097 comm="apparmor_parser"
Jun 25 17:03:10 dss-mint19-xfce NetworkManager[1217]: <info>  [1561507390.1371] dhcp-init: Using DHCP client 'dhclient'
Jun 25 17:03:20 dss-mint19-xfce NetworkManager[1217]: <info>  [1561507400.4868] dhcp4 (wlxbcec23100000): dhclient started with pid 1709
Jun 25 17:03:20 dss-mint19-xfce dhclient[1709]: DHCPREQUEST of 192.168.0.10 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x3c5009b)
Jun 25 17:03:22 dss-mint19-xfce NetworkManager[1217]: <info>  [1561507402.9066] dhcp6 (wlxbcec23100000): dhclient started with pid 1987
Jun 25 17:03:23 dss-mint19-xfce dhclient[1987]: XMT: Info-Request on wlxbcec23100000, interval 940ms.
Jun 25 17:03:23 dss-mint19-xfce dhclient[1987]: RCV: Reply message on wlxbcec23100000 from fe80::3a70:cff:feca:8385.
Jun 25 17:03:23 dss-mint19-xfce dhclient[1709]: DHCPREQUEST of 192.168.0.10 on wlxbcec23100000 to 255.255.255.255 port 67 (xid=0x3c5009b)
Jun 25 17:03:23 dss-mint19-xfce dhclient[1709]: DHCPACK of 192.168.0.10 from 192.168.0.1
Jun 25 17:03:23 dss-mint19-xfce dhclient[1709]: bound to 192.168.0.10 -- renewal in 37190 seconds.
This sample is the entire day.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

It's the host doing DHCP requests, I guess NetworkManager is involved in this.

Why you want forever?
Can you assign static IP's on that router?
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

I actually set both, so I don't even know why this is happening. It's not the actual lease that's getting renewed, it's this "rebind" message that I can't seem to find any reference on. My last modem would do this on very rare occasions - the new one is like once every 10 minutes. It's not affecting my network, so I'm not that worried; just curious about the messages, that's all.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

Are you assigning statics outside of the DHCP pool?
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

No - my IP pool range is 2-20, and everything that I've configured for permanent leases are auto-discovered.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

So you're saying 2-20 is DHCP and the 21-up is for static?
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

I don't use anything above 20, at least not at the moment. The system I've posted about is using 11.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

What DHCP range is set in your modem?
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

2-20
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

And you assigned .11 as static?
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

No, reserved lease.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: DHCP client connecting at random

Post by Pippin »

Ok, just ruling out some things.

Regarding rebind:
https://lazyadmin.nl/home-network/dhcp-lease-time/

But the log shows that mint is doing requests even the modem is set to infinite lease.... (infinite is not clearly defined in modem world)
..... NetworkManager.... just thinking :-)
Maybe do a packet capture and let someone look at it that has the protocol knowledge of how it should work.
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

I changed the lease time to 24 hours, but it hasn't made any difference. Later on tonight I'm going to reboot the modem, just to make sure the settings are truly in effect. Thanks for all the help!
ajgringo619

Re: DHCP client connecting at random

Post by ajgringo619 »

How's this for a weird solution??? It turns out that the Cox modem that I got has issues with passwords that contain special characters; once I changed this, the error messages stopped.
User avatar
Pippin
Level 4
Level 4
Posts: 441
Joined: Wed Dec 13, 2017 11:14 am
Location: The Shire

Re: [SOLVED] DHCP client connecting at random

Post by Pippin »

Indeed very weird :?
Glad it's working.
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
Locked

Return to “Networking”