Bug #452
closed
DHCP Hostname can't use periods
0%
Description
I wasn't sure if I should update my previous bug(Bug #427) or add a new one. Since you guys committed the changes to 1.2 and say it's in 2.0 and I just run into this issue, I figured I would file a new bug.
I tried to use a hostname in a static DHCP lease with a period in it and DHCP fails to start with a syntax error.
Mar 25 13:03:22 dhcpd: /var/dhcpd/etc/dhcpd.conf line 43: semicolon expected.
Mar 25 13:03:22 dhcpd: /var/dhcpd/etc/dhcpd.conf line 43: semicolon expected.
Mar 25 13:03:22 dhcpd: option host-name host.
Mar 25 13:03:22 dhcpd: option host-name host.
Mar 25 13:03:22 dhcpd: ^
Mar 25 13:03:22 dhcpd: ^
Mar 25 13:03:22 dhcpd: Configuration file errors encountered -- exiting
Mar 25 13:03:22 dhcpd: Configuration file errors encountered -- exiting
This might be something that needs to be caught by the portal or I need to try qouting the hostname to prevent the issue.
When I get sometime I will test some changes unless you guys know the fix.
-c
Updated by Chris Buechler over 14 years ago
- Target version changed from 1.2.3 to 2.0
- Affected Version changed from All to 2.0
Updated by Pierre POMES over 14 years ago
In 2.0, you cannot enter hostname with "." (periods), it is already fixed.
Updated by Chris Buechler over 14 years ago
- Status changed from New to Feedback
Yeah that's right, you did fix that Pierre. Setting to feedback for more info if it's still somehow possible to run into this.
Updated by Chris Buechler over 14 years ago
- Status changed from Feedback to Resolved
I can't find any possible way to see this in 2.0. Will need more info if problem can still be replicated with latest 2.0 snapshot.