Losing DHCP Gateway

This problem started with 17.5.0 GA.  The firewall is handling DHCP for my lan.  Users have started to lose the default gateway(the Firewall) randomly throughout the day.  I have to either reset the switch or the desktop network adapter in order to regain internet connectivity.  This does NOT happen to all users at the same time.

I updated to XG 115 SFOS 17.5.5 MR5 but the problem still exists.  This actually introduced another problem of not being able to access the gui from Sophos Central, but that's not as pressing.  Any thoughts on this would be appreciated.

Thanks

Larnel

  • In reply to deeptibhavsar:

    Hi Deepti,

    Unfortunately this hasn’t fixed on MR6, can you provide us ETA for fix?

    Thanks

    Parham

  • In reply to Parham Pourkhosravy:

    Hi,

     

    Request to share the backup of appliance.

     

    Regards,

    Deepti

  • In reply to deeptibhavsar:

    Hi Deepti,

    Have already sent it.

    Thanks,

    Parham

  • In reply to Parham Pourkhosravy:

    Hi all,

    After upgrading to version 17.5.6 MR6, SFOS home DHCP works as it should. Earlier, however, with version 17.5.5, I used the command "dhcp system conf-generation-method old".

    Regards
    Jan

  • In reply to JanSadlik:

    If you run

    > dhcp system conf-generation-method show

    This will tell you whether you are using the old or new method.

    On a fresh install, the method chosen is "new" and this doesn't work, an ungraded from 17.5.5 to 17.5.6 seems to keep the "old" setting if previously set - so I would suspect that this is why it's working for you as it should.

    The command : -

    > dhcp system conf-generation-method new

    Will set it to the new method.

  • In reply to BLS:

    Hello

    The command is "system dhcp ... "  and not "dhcp system ...".

    Paul Jr

  • In reply to BLS:

    Hello

    Just did a new install and went to MR6 can confirm this issue is still not resolved.

    I had to manually run the fix command to get it working for now.

    Thanks

  • In reply to waghelak:

    How can this not be fixed yet?  I'm not upgrading all of my clients until this is fixed.  It's a joke that we should be required to run a command to fix a known problem.  Why don't you just issue a hot fix that automatically disables DHCP new for everyone?  I'm so disappointed in Sophos right now.  This is unacceptable.

  • In reply to BLS:

    I all,

    never have the pb on many 17.5mr5 fresh install.

    but many problems upgrading from 17.5.X => 17.5.5 and 17.5.6

     how can it be possible to break a basic thing like DHCP ????!!!!

  • In reply to guillaume bottollier:

    A clue could be in this "New" versus "Old" config method ...  While upgrading to newer SFOS, some failures may have occurred. 

    Maybe re-configuring DHCP from scratch - i.e. wipe old DHCP configuration - would solve the problem.

    Theorizing here ...

    Paul Jr Robitaille

  • In reply to Big_Buck:

    Hi Buck,

    thanks for your reply, and i read about the workarround and inform my team about this one.

    But i still consider it is totally unacceptable to release a production version that breaks a basic feature like DHCP.

    It is just impossible for us to recreate the all DHCP configuration of all of our clients.

    as a result, we are waiting for a REAL stable update MR.

  • We too are experiencing this issue. Extremely frustrating and make us look bad. Just had to call a client and have them reboot all of their machines.

  • In reply to Big_Buck:

    Hi,

    Could any of the Sophos team explain to us what exactly means "old" or "new" in the DHCP configuration?

    Regards
    Jan

  • In reply to guillaume bottollier:

    guillaume bottollier

    Hi Buck,

    thanks for your reply, and i read about the workarround and inform my team about this one.

    But i still consider it is totally unacceptable to release a production version that breaks a basic feature like DHCP.

    It is just impossible for us to recreate the all DHCP configuration of all of our clients.

    as a result, we are waiting for a REAL stable update MR.

     

     

    Most companies probably haven't noticed that DHCP is broken, certainly true for a lot of the ones that I support - they all use Active Directory DHCP as it ties in with AD DNS and other aspects of Active Directory - so they wouldn't have noticed that DHCP is broken as they don't use it.

    Plus the capabilities of the DHCP server in Sophos XG is more suited to SME's and Home users anyway, it's very basic in it's functionality.

  • In reply to Big_Buck:

    Big_Buck

    Hello

    The command is "system dhcp ... "  and not "dhcp system ...".

    Paul Jr

     

     

    Thanks Paul - apologies I was typing from memory on a phone, so thanks for getting the command in the right order :)