Possible DHCP issue?

› Forums › Network Management › ZeroShell › Possible DHCP issue?

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 11, 2015 at 12:24 am #44373
    ultimoblaze
    Member

    I have a zeroshell box running 3.3.2 and is supporting 4 vlans with DHCP. Clients have been complaining about random network connectivity drops. They lose connection to the network and have to disconnect and reconnect to get connection again. I looked through the DHCP log on the router and saw this:

    19:59:11 DHCPINFORM from 192.168.110.112 via ETH01.10
    19:59:11 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    19:59:11 DHCPINFORM from 192.168.110.112 via ETH01.10
    19:59:11 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:01:47 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:01:47 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:01:47 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:01:47 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:03:39 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:03:39 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:03:39 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:03:39 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:07:07 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:07:07 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:07:07 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:07:07 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:08:44 DHCPINFORM from 192.168.110.100 via ETH01.10
    20:08:44 DHCPACK to 192.168.110.100 (d0:df:9a:d8:41:ee) via ETH01.10
    20:09:27 DHCPINFORM from 192.168.110.104 via ETH01.10
    20:09:27 DHCPACK to 192.168.110.104 (60:d8:19:3e:9b:c4) via ETH01.10
    20:10:15 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:10:15 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:10:15 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:10:15 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:12:19 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:12:19 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:12:19 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:12:19 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:15:33 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:15:33 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:15:33 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:15:33 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10
    20:16:59 DHCPINFORM from 192.168.110.112 via ETH01.10
    20:16:59 DHCPACK to 192.168.110.112 (48:ee:0c:87:d3:97) via ETH01.10

    I’m no expert in DHCP, but seeing the INFORM and ACK so frequently doesn’t seem right. This is happening on every DHCP client as far as I can tell. The default lease time is set to 8 hours. I’m told this happens multiple times in a work day.

    Does anybody have any ideas as to what is going on?

    Thanks,
    Ultimoblaze

    September 15, 2015 at 10:38 pm #53878
    ultimoblaze
    Member

    I have some more log data. Something must be going wrong, but I don’t know nearly enough about how DHCP works to try and fix it.

    Here is a small portion of the log from yesterday. The log is filled with pages and pages of INFORMs and ACKs and DISCOVERs.

    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPDISCOVER from 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10
    09:19:22 DHCPOFFER on 192.168.110.112 to 48:ee:0c:87:d3:97 (investment-PC) via ETH01.10

    Any suggestions?

    Thanks,
    Ultimoblaze

    September 16, 2015 at 2:05 am #53879
    ultimoblaze
    Member

    So I’ve turned off the DHCP server in Zeroshell and used this forum post https://www.zeroshell.org/forum/viewtopic.php?t=557 to set up dhcrelay to a DHCP server running on Windows 2008. Unfortunately, all of my clients get IP addresses from the same subnet. The startup script looks like this:

    dhcrelay -i ETH01.1 -i ETH01.10 -i ETH01.20 192.168.101.5

    All of my clients get IP addresses as if they were on VLAN 10. This might fix my issues with the DHCP server, but now my VLANs are all using the same subnet.

    Does anybody have any suggestions?

    Thanks,
    Ultimoblaze

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.