Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    S30 Thermostat dhcp log spam?

    Off-Topic & Non-Support Discussion
    3
    5
    535
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator
      last edited by

      Ok I noticed this morning, there was dhcp question, and was looking in my dhcp log for an example of normal dhcp process. I don't normally have any reason to look in this log, so not sure how long this might have been going on - most likely for ever from this device. But now that I am aware of it - its bugging me ;)

      Dec 16 08:52:02 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:52:02 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:52:02 	dhcpd 	77091 	DHCPOFFER on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:52:02 	dhcpd 	77091 	DHCPDISCOVER from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:49:03 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:49:03 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:49:03 	dhcpd 	77091 	DHCPOFFER on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:49:03 	dhcpd 	77091 	DHCPDISCOVER from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:47:07 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:47:07 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:47:07 	dhcpd 	77091 	DHCPOFFER on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:47:07 	dhcpd 	77091 	DHCPDISCOVER from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:43:36 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:43:36 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:43:36 	dhcpd 	77091 	DHCPOFFER on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 16 08:43:36 	dhcpd 	77091 	DHCPDISCOVER from 88:3f:4a:f0:cb:9c via igb2.4

      I have not noticed any issue with the thermostat working. Its just annoying that it fills the logs because it keeps sending discover, and while it gets the same IP which I have a reservation set for. I validated that the lease time is being sent as 2 hours, so it should really only do a renew every hour.. But its not sending renew, its sending discover.

      This is highly unlikely to have anything to do with dhcp in pfsense, I don't see any other clients doing this.. Just hoping some of the smart people here might have the same icomfort S30 thermostat from lennox. Maybe you could look to see if seeing the same behavior?

      I tried doing a reboot of it and its hub.. Same behavior - which is odd is its not on a specific say every X minute cycle, there is some variance to it - but it does it so much that log is just filled with it, and make its harder to spot other clients, etc.

      If I could just set a static on the device, I would do that and be done with it. But there does not seem to be any option on the device to do that.

      I am not seeing any sort of problem with the device.. It works just fine, my guess is just horrible dhcp client setup on it the device code.. Its just annoying spam in the log..

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.03 | Lab VMs 2.7.2, 24.03

      H 1 Reply Last reply Reply Quote 0
      • H
        heper @johnpoz
        last edited by

        @johnpoz is this wired or WiFi?
        Perhaps it does this each time the ap bumps the device from 2.4 gf hz to 5ghz and back?

        johnpozJ 1 Reply Last reply Reply Quote 1
        • johnpozJ
          johnpoz LAYER 8 Global Moderator @heper
          last edited by johnpoz

          @heper its wireless - believe me I wish I could wire it.. But I don't see it moving between AP or 2.4 and 5 per my logs that line up with dhcp noise.

          In the logs I do see a disconnect and connection at 5:47 this morning but same band, same AP.. Now there is an entry there at that time with discover, but stupid unifi logs don't give second.. So can not be sure if related to that or just in the same minute.. And still seeing way more entries before that and after that time with nothing in the unifi log about a disconnect or moving between AP, etc.

          But that is an fantastic suggestion, and had high hopes that might of been it. But either unifi is not logging all the disconnects and or moving between AP? Or its not related to that - I see lots of entries when for when my phone moves about to different AP in the house.. so seems odd that I do see a time where it disconnected and reconnected.. But if it was causing the dhcp logs - whey only that one entry in the unifi log about a disconnect?

          But - some good news is looking a bit closer at the logs, after I changed the lease time down to 2 hours.. It looks to be renewing every hour like it should, not seeing all those discovers

          Dec 17 11:02:40 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 11:02:40 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 10:02:40 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 10:02:40 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 09:02:40 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 09:02:40 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 08:02:40 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 17 08:02:40 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4

          I had changed it yesterday from the 24 hours that was being handed out per my sniff back to the default 2 hour lease time..

          But I will keep a eye on it and see if discovers only match up to when shows a disconnect from the AP.. or channel change or move, etc. I don't ever see it connecting at 5ghz so I believe it only supports 2.4

          I will see how it runs for a few days, and then see maybe if I can up the lease time from 2 hours to 4 etc.

          Maybe it didn't like or couldn't understand the long lease of 24 hours.. But it seems to be ok with just doing a renew every hour.. These crap little iot devices with their shit networking stacks ;)

          I get having wifi on them - but how much really would it cost to add a simple 10/100 or even just a 10mbps interface even.. Its not like thermostats move about and would require wifi ;)

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.03 | Lab VMs 2.7.2, 24.03

          johnpozJ 1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @johnpoz
            last edited by

            Ok well saw discover this morning from it

            Dec 18 08:13:22 	dhcpd 	52789 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 08:13:22 	dhcpd 	52789 	DHCPREQUEST for 192.168.4.89 (192.168.4.253) from 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 08:13:22 	dhcpd 	52789 	DHCPOFFER on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 08:13:22 	dhcpd 	52789 	DHCPDISCOVER from 88:3f:4a:f0:cb:9c via igb2.4

            But per my unifi logs its been connected for 13 some hours this session.

            So makes no sense that disconnection and reconnect causing the discover. And I see where it did normal renews

            Dec 18 06:51:57 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 06:51:57 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 05:51:57 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 05:51:57 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 04:51:58 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 04:51:58 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 03:51:57 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 03:51:57 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 02:51:57 	dhcpd 	77091 	DHCPACK on 192.168.4.89 to 88:3f:4a:f0:cb:9c via igb2.4
Dec 18 02:51:57 	dhcpd 	77091 	DHCPREQUEST for 192.168.4.89 from 88:3f:4a:f0:cb:9c via igb2.4

            So its not flooding with discover every few minutes any more - but curious why it decided to do a dhcp discover 8:13 - this is not in line with its renew interval.. And per the log on unifi I don't see any issues or changes with its connection.

            Going to try bumping the lease time up to 8 hours and see if renews on that schedule..

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.03 | Lab VMs 2.7.2, 24.03

            1 Reply Last reply Reply Quote 0
            • M
              markster
              last edited by

              I am having similar issue with EcoBee thermostat. It happens only after firmware updates. Unfortunately there is no means to disable it. If I try to reconnect ecobee back to AP it fails.
              The fix for me is to reboot the AP and things start to work.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post