Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 1308 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 service will not start after pushing configuration via API

Nick Dann

Hello Sophos Community,

I'm facing an issue where the DHCP server service fails to start after I've pushed my DHCP configuration through the API. Even when I navigate to the System Services in the Web GUI and press the start button, I encounter a peculiar situation. A green banner appears at the top indicating "Started Service," yet the service status remains on "Stopped."

Interestingly, the service resumes only after I perform any action within the Network -> DHCP section. For example, simply entering a configuration page and hitting save is enough to kickstart the service again. This implies that I need to make some sort of modification via the Web GUI for the service to successfully launch.

I'm puzzled as to why this is happening. Could it be that the API push is not properly initializing some required settings or there's a missing step that the Web GUI somehow completes?

For reference, my configuration XML (test.xml) is structured as follows:

<DHCPServer>
<Name>Test</Name>
<Status>1</Status>
<Interface>Port6</Interface>
<ConflictDetection>Disable</ConflictDetection>
<LeaseForRelay>Disable</LeaseForRelay>
<SubnetMask>255.255.255.0</SubnetMask>
<DomainName>munk.de</DomainName>
<DefaultLeaseTime>1440</DefaultLeaseTime>
<MaxLeaseTime>2880</MaxLeaseTime>
<UseApplianceDNSSettings>Disable</UseApplianceDNSSettings>
<StaticLease>
<Lease>
<HostName>test1</HostName>
<MACAddress>AA-AA-AA-AA-AA-AA</MACAddress>
<IPAddress>192.168.29.3</IPAddress>
</Lease>
<Lease>
<HostName>test2</HostName>
<MACAddress>AA-AA-AA-AA-AA-AA</MACAddress>
<IPAddress>192.168.29.2</IPAddress>
</Lease>
</StaticLease>
<PrimaryDNSServer>192.168.29.254</PrimaryDNSServer>
<SecondaryDNSServer/>
<PrimaryWINSServer/>
<SecondaryWINSServer/>
<Gateway>192.168.29.254</Gateway>
<UseInterfaceIPasGateway>UseInterfaceIPAsGateway</UseInterfaceIPasGateway>
<DHCPOption>
<Options>
<OptionName>NTP_Servers(42)</OptionName>
<OptionCode>42</OptionCode>
<OptionType>arr_ipaddr</OptionType>
<OptionValue>192.168.200.143</OptionValue>
</Options>
</DHCPOption>
</DHCPServer>

The push also says:

<DHCPServer transactionid="">
<Status code="200">Configuration applied successfully.</Status>
</DHCPServer>

I'd greatly appreciate any insights or suggestions on why this behavior is occurring and how to resolve it. It seems like there's a disconnect between the API configuration process and the service's ability to recognize and act upon these settings without manual intervention through the GUI.

Thank you in advance for your help and advice!



This thread was automatically locked due to age.
  • 0

    Could you manually configure this DHCP Server and export it via XML? 
    Then try to match the values you are setting with the ones, SFOS webadmin would set. Maybe there is something wrong here. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    After comparing the configurations before and after, I noticed that the MAC addresses were separated by colons (":"), even though I had pushed them through my XML with dashes ("-"). I've adjusted my XML accordingly, and now it seems to be working properly.

Unfiltered HTML