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

    Troubleshooting Client Disconnect

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 5 Posters 1.4k Views 5 Watching
    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.
    • J Offline
      jpvonhemel
      last edited by

      Hello,

      I am an SG-2440 pfsense home user with a disconnect issue. I have a Honeywell Redlink Gateway device that connects to my HVAC system that had worked well for maybe a year or so that is starting to disconnect from the LAN. It connects via ethernet to my LAN. I have moved it around the house but it initially connects, but will eventually disconnect regardless of where I use it. I did have a DHCP reservation for it and deleted it so it takes a pool ip, but this did not help. I don't seem to be having any other network issues and the LAN is stable.

      I am trying to figure if the DCHP server is dropping it for some reason or if perhaps it is disconnected. The last pool IP address it was assigned is 192.68.1.226. I installed Wireshark and have my logs. Not sure how best to post Wireshark info here.

      Here is the DCHP log activity for the device. I powered it on at 11:47 and noticed it was booted around 11:52.

      Thanks,
      Jerold

      Nov 24 11:53:55 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:44 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:36 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:29 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:24 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:23 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:16 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:53:03 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:50 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:41 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:33 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:28 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:24 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:23 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:52:21 dhcpd: DHCPRELEASE of 192.168.1.226 from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1 (found)
      Nov 24 11:47:47 dhcpd: DHCPACK on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
      Nov 24 11:47:47 dhcpd: DHCPREQUEST for 192.168.1.226 (192.168.1.1) from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1

      1 Reply Last reply Reply Quote 0
      • J Offline
        jpvonhemel
        last edited by

        Here is the log as of now. I cannot ping the ip at this time.

        Nov 24 12:21:24 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:24 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:21 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:21 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:18 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:18 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:14 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:21:14 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:59 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:59 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:48 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:48 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:38 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:38 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:31 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:31 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:24 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:24 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:19 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:19 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:17 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:17 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:12 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:20:12 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:19:58 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:19:58 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:19:47 dhcpd: DHCPOFFER on 192.168.1.226 to 00:d0:2d:e3:38:30 (GatewayE33830) via igb1
        Nov 24 12:19:47 dhcpd: DHCPDISCOVER from 00:d0:2d:e3:38:30 (GatewayE33830) via igb1

        JKnottJ 1 Reply Last reply Reply Quote 0
        • NollipfSenseN Offline
          NollipfSense
          last edited by NollipfSense

          In your case, I would give it a static address from the pool since it seems that's what that device needs...especially. that had worked in the pass. It reminds me of network cameras for surveillance...best to have them on static IP addresses.

          pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
          pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

          1 Reply Last reply Reply Quote 0
          • J Offline
            jpvonhemel
            last edited by

            Thanks for responding. I worked well for about a year and a half and then suddenly started dropping off off the LAN using the static IP, that is why I pulled the reservation and let it be assigned from the from the pool. It didn’t seem to matter whether it was static or dhcp.

            It looks to me like the router is trying to offer the device an IP, but does not get a response back. Thinking about just buying a replacement but thought I would look a bit deeper to see if it was something else. Support for the Honeywell device didn’t get me anywhere.

            1 Reply Last reply Reply Quote 0
            • NollipfSenseN Offline
              NollipfSense
              last edited by

              It there a way to increase the timing on that device? Yes, it seems to timeout before it accepts the IP.

              pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
              pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

              1 Reply Last reply Reply Quote 0
              • J Offline
                jpvonhemel
                last edited by

                Unfortunately, it does not have a way to configure any settings.

                1 Reply Last reply Reply Quote 0
                • JKnottJ Offline
                  JKnott @jpvonhemel
                  last edited by

                  @jpvonhemel said in Troubleshooting Client Disconnect:

                  Here is the log as of now. I cannot ping the ip at this time.

                  After the server sends the offer, the client is supposed to respond with a request. I don't see that. That appears to be a problem with that device. Can you test with another DHCP server? Just configure it as you would the pfSense one and then disable the server on pfSense.

                  PfSense running on Qotom mini PC
                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                  UniFi AC-Lite access point

                  I haven't lost my mind. It's around here...somewhere...

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    jpvonhemel
                    last edited by

                    I tried the Honeywell Gateway device using a separate TPLink branded router and did not have any issues with the device dropping off the LAN. I know ethernet, TCP/IP and DHCP are all standards based thus I am not sure why this little device would not like my PFSense router or any of the switches on my network. Perhaps it does not like my DCHP server settings.

                    I am not sure what to do next.

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S Offline
                      stephenw10 Netgate Administrator
                      last edited by

                      I mean really 'call Honeywell' but I can imagine that would get you no where at all!

                      You could get a packet capture of the dhcp exchange with another server that works and see what's different. Then try to match that in pfSense, there are some configurable DHCP options.

                      You could put a different dhcp server on that subnet that it does work with.

                      You could put it behind another router but have that on the pfSense LAN.

                      Assuming it needs internet access for some IoT type activity it should probably be on an isolated subnet anyway.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        jpvonhemel
                        last edited by

                        Thanks for your response. Like you said, Honeywell support said it was defective and buy a new one.

                        It appears to be an issue between my D-Link DGS-1100 switch and the Honeywell device. It works when connected directly with the SG-2440 Lan adapter.

                        Working with D-Link support on the issue.

                        Thanks,

                        Jerold

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S Offline
                          stephenw10 Netgate Administrator
                          last edited by

                          Ah, interesting. I guess an additional switch is probably cheaper than the Honeywell device at least. 😉

                          1 Reply Last reply Reply Quote 0
                          • W Offline
                            willmoser
                            last edited by

                            Were you ever able to resolve this issue with D-Link support? I am having the exact same problem here, its strange too as we have some of the older v1 redlinks which work perfect but all of our v2 redlinks are behaving just like yours.

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              jpvonhemel
                              last edited by

                              Sorry for the late post but wanted to close it out here in the rare case someone searches for the issue. I gave up on Dlink support and this device. It should have auto negotiated and been fine. My first solution was to use a tplink ac740 in wifi bridge mode, then connect the hub to the ac740 using an Ethernet cable.

                              Since then I added a Ubiquiti 24 port poe switch and have zero issues with the Honeywell hub when going through a different switch. Isn't IOT wonderful!

                              1 Reply Last reply Reply Quote 1
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.