Guest User!

You are not Sophos Staff.

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 Relay

After the update to 19.0 DHCP Relay did not work anymore. The clients were no longer assigned an IP address. After I opened all DHCP Relay settings on Sophos XG and saved them again (without any change) it works again. I hope this was a one-time "update" problem and does not happen again after every failover...



This thread was automatically locked due to age.
Parents
  • Hey, ah, so this bug is still there in v19. I expected this. We're having it since moving from v17 ti v18.

    Sometimes DHCP Server on XG will fail, sometimes DHCP Relay to Windows Server will fail.

    Re-Saving does not help on our XG, we need to delete and recreate a random DHCP Server or Relay to get it working again.

    Have a case open currently but no technical feedback after weeks.

    05158330 / 05128430

    I ask you to open a case and refer to my case no#

    do you have CheckMK?

    We can see it in the DHCP Statistics on our Windows DHCP Server for Relay.

    issue start= clients not getting DHCP address

    issue fixed= we recreated one of a dozend DHCP Relays on XG

  • Likely it is actually a Flood Prevention of DHCP Relay and not a Bug.

    The point is: DHCP Relay has a Builtin Feature called Flood Protection. 

    If the DHCP Server was not reachable for the first DHCP requests, the relay will stop for some time to prevent a DHCP storm to the Servers. 

    This prevents networks to go down from DHCP floods of requests which nobody answers. 

    All the cases, i worked in, this was the case. The DHCP server was not reachable or did not answer for some reasons. 

    And this screenshot actually makes me wonder: Why are there so many requests in this window? 

    A Tcpdump of those requests in the affected area would help to see, who to blame. DHCP Relays work with the DHCP agent IPs. This means, if the server answers incorrectly, this could cause this. Only proveable in a tcpdump. 

    __________________________________________________________________________________________________________________

Reply
  • Likely it is actually a Flood Prevention of DHCP Relay and not a Bug.

    The point is: DHCP Relay has a Builtin Feature called Flood Protection. 

    If the DHCP Server was not reachable for the first DHCP requests, the relay will stop for some time to prevent a DHCP storm to the Servers. 

    This prevents networks to go down from DHCP floods of requests which nobody answers. 

    All the cases, i worked in, this was the case. The DHCP server was not reachable or did not answer for some reasons. 

    And this screenshot actually makes me wonder: Why are there so many requests in this window? 

    A Tcpdump of those requests in the affected area would help to see, who to blame. DHCP Relays work with the DHCP agent IPs. This means, if the server answers incorrectly, this could cause this. Only proveable in a tcpdump. 

    __________________________________________________________________________________________________________________

Children
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?