Ticket #1193 (closed defect: fixed)

Opened 20 months ago

Last modified 19 months ago

DHCP filename option should not be a file field

Reported by: james@… Owned by: iclerencia@…
Priority: high Milestone:
Component: dhcp Severity: major
Keywords: thin client Cc:

Description

Under the advanced tab for configuring DHCP it is a little bizarre to have a file field used to represent the filename option. Since this field is tied to what file to load from the next-server this should be a plain text field.

I had to modify /etc/dhcp3/dhcpd.conf directly to get my thin clients to work.

Attachments

Change History

Changed 20 months ago by ejhernandez@…

Is it necessary to set the filename if your option is not eBox itself?

Changed 20 months ago by ejhernandez@…

I answer myself, yes.

The correct solution will be:

  • Have a File field if the next server is eBox
  • Have a Text field if the next server is not eBox neither None

Thanks for your feedback and pointing out this bug.

Changed 20 months ago by iclerencia@…

  • owner changed from juruen@… to iclerencia@…
  • status changed from new to assigned

Changed 19 months ago by iclerencia@…

  • status changed from assigned to closed
  • resolution set to fixed

The current model framework doesn't allow this, so I have just added all the fields and added the needed logic to enforce the required rules.

Add/Change #1193 (DHCP filename option should not be a file field)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.