Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 4537 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP Server Bug?

jaredscheringer

On multiple occasions i've noticed the DHCP Server on the sophos try to hand out an IP that is explicitly RESERVED on the sophos. Is there a known bug on a bug tracker i can contribute to? 

 

The only workaround i've figured out is to turn off the Internal DHCP Server Scope on the sophos and immediately turn it back on so it flushes cache/appropriately hands out a different ip to a requesting machine as opposed to hammering a reserved IP down its throat lol

I've seen this across a few revisions, but the problem has occurred so frequently now that i figured i'd post. we are on Firmware version 9.510-5



This thread was automatically locked due to age.
Parents
  • 0

    Here is what transpires in the log, it just happened again.


    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPDISCOVER from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPOFFER on 192.168.17.78 to 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: reuse_lease: lease age 441 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.17.78
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPREQUEST for 192.168.17.78 (192.168.17.1) from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPACK on 192.168.17.78 to 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:29 bh-hotel-gw-1 dhcpd: DHCPDECLINE of 192.168.17.78 from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0: ignored

     

    The attached picture is the current reservation on that IP.

     

     

    SEPARATELY, while monitoring for this client's issue, i saw the following in the logs for another client. This time though it actually recommends something to do, but i figured a DHCP reservation should supercede and the DHCP server should simply know not to hand it out? I mean that's how it's SUPPOSED to work lol

    Have i missed a crucial configuration step on the sophos?

    BTW the Lease time is set to 1800, a relic setting from a scope move, but i believe this should not be relevant to the issue unless it pertains to a bug

    2019:01:21-12:04:10 bh-hotel-gw-1 dhcpd: Dynamic and static leases present for 192.168.17.176.
    2019:01:21-12:04:10 bh-hotel-gw-1 dhcpd: Remove host declaration REF_NetHosItcleon or remove 192.168.17.176
    from the dynamic address pool for 192.168.17.0/24

Reply
  • 0

    Here is what transpires in the log, it just happened again.


    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPDISCOVER from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPOFFER on 192.168.17.78 to 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: reuse_lease: lease age 441 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.17.78
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPREQUEST for 192.168.17.78 (192.168.17.1) from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:28 bh-hotel-gw-1 dhcpd: DHCPACK on 192.168.17.78 to 00:25:64:93:b3:78 (HTLBHPDK08) via eth0
    2019:01:21-12:05:29 bh-hotel-gw-1 dhcpd: DHCPDECLINE of 192.168.17.78 from 00:25:64:93:b3:78 (HTLBHPDK08) via eth0: ignored

     

    The attached picture is the current reservation on that IP.

     

     

    SEPARATELY, while monitoring for this client's issue, i saw the following in the logs for another client. This time though it actually recommends something to do, but i figured a DHCP reservation should supercede and the DHCP server should simply know not to hand it out? I mean that's how it's SUPPOSED to work lol

    Have i missed a crucial configuration step on the sophos?

    BTW the Lease time is set to 1800, a relic setting from a scope move, but i believe this should not be relevant to the issue unless it pertains to a bug

    2019:01:21-12:04:10 bh-hotel-gw-1 dhcpd: Dynamic and static leases present for 192.168.17.176.
    2019:01:21-12:04:10 bh-hotel-gw-1 dhcpd: Remove host declaration REF_NetHosItcleon or remove 192.168.17.176
    from the dynamic address pool for 192.168.17.0/24

Children
No Data
Unfiltered HTML