Losing DHCP Gateway

Hi,

Thank you for the feedback.

Request to run below command from CLI, in case of facing issue & give us feedback.

Hi Deepti,

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

Thanks

Parham

Hi,

Request to share the backup of appliance.

Regards,

Deepti

Hi Deepti,

Have already sent it.

Thanks,

Parham

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

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.

Hello

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

Paul Jr

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

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.

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 ????!!!!

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

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

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.

Hi,

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

Regards
Jan

guillaume bottollier said:

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.

Heck. XG DHCP provides IPs.  That's it that's all.  Absolutely basic.  Will work for "Guest Wireless", but that's the end of it.

Paul Jr