<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi<br> Does Any body knows why this secuense sometimes doesn´t work<br>service dhcpd restart, usually It says failed<br>but if you put /etc/init.d/dhcpd start, it works fine<br>I, am Confused<br><br>I appreciate any comment<br><br><br><br>--- On <b>Wed, 8/6/08, Ryan McCain <i><Ryan.McCain@dss.state.la.us></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Ryan McCain <Ryan.McCain@dss.state.la.us><br>Subject: RE: Best practice for defining static IP addresses?<br>To: dhcp-users@isc.org<br>Date: Wednesday, August 6, 2008, 2:08 PM<br><br><pre>Todd,<br><br>Thanks for the link.<br><br>>>> On Wed, Aug 6, 2008 at 9:45 AM, in message<br><1D8C9A4471119A40BD574F9D8D464AE301B85A76@XCH60YKF.rim.net>, "Todd<br>Snyder"<br><tsnyder@rim.com> wrote: <br>>
http://marc.info/?l=dhcp-users&m=121088413725977&w=2 Covers it I<br>think<br>> <br>> Cheers,<br>> <br>> Todd.<br>> <br>> -----Original Message-----<br>> From: dhcp-users-bounce@isc.org [mailto:dhcp-users-bounce@isc.org] On<br>> Behalf Of Ryan McCain<br>> Sent: Wednesday, August 06, 2008 10:24 AM<br>> To: dhcp-users@isc.org<br>> Subject: RE: Best practice for defining static IP addresses?<br>> <br>> Todd,<br>> <br>> Thanks for the info. Do you have a link to your thread?<br>> <br>> <br>>>>> On Tue, Aug 5, 2008 at 4:02 PM, in message<br>> <1D8C9A4471119A40BD574F9D8D464AE301B85A6C@XCH60YKF.rim.net>,<br>"Todd<br>> Snyder"<br>> <tsnyder@rim.com> wrote:<br>>> I thought this very same thing until a few months ago, and after<br>>> bashing my head about for a while, I came here and was corrected.<br>>><br>>> Static assignments need to be outside
any defined ranges. This is<br>>> different than Windows DHCP, which lets you 'reserve' an ip in<br>the<br>>> middle of range.<br>>><br>>> If you want to do the first option, you will have to define 2 ranges<br>>><br>>> range 10.119.14.1 10.119.14.99<br>>><br>>> and<br>>><br>>> range 10.119.14.101 10.199.14.179<br>>><br>>> Which isn't ideal.<br>>><br>>> Cheers,<br>>><br>>> Todd.<br>>><br>>> -----Original Message-----<br>>> From: dhcp-users-bounce@isc.org [mailto:dhcp-users-bounce@isc.org] On<br>>> Behalf Of Ryan McCain<br>>> Sent: Tuesday, August 05, 2008 4:55 PM<br>>> To: dhcp-users@isc.org<br>>> Subject: Best practice for defining static IP addresses?<br>>><br>>> Lets assume this is my DHCP scope:<br>>><br>>> subnet 10.119.14.0 netmask 255.255.255.0 {<br>>> range 10.119.14.1
10.119.14.179 ;<br>>> option routers 10.119.14.254 ;<br>>><br>>> If I wanted to assign a static IP address, would I do?<br>>><br>>> host Black {<br>>> hardware ethernet 00:19:5B:EC:A7:11;<br>>> fixed-address 10.119.14.100;<br>>> }<br>>><br>>> or<br>>><br>>> host Heart {<br>>> hardware ethernet 00:19:5B:EC:A7:12;<br>>> fixed-address 10.119.14.200;<br>>> }<br>>><br>>> ..Notice that 'Black' is within the defined range while<br>'Heart' is<br>> not.<br>>><br>>> I've always assume I could assign a static IP within the defined<br>range<br>> <br>>> and the MAC address would act as a 'key' to prevent it from<br>being<br>>> handed out (even though it's in a defined range).<br>>><br>>> Thanks for the
clarification..<br>>><br>>><br>>><br>>><br>>><br>>><br>>><br>>><br>>> ---------------------------------------------------------------------<br>>> This transmission (including any attachments) may contain confidential<br>> <br>>> information, privileged material (including material protected by the<br>>> solicitor-client or other applicable privileges), or constitute<br>>> non-public information. Any use of this information by anyone other<br>>> than the intended recipient is prohibited. If you have received this<br>>> transmission in error, please immediately reply to the sender and<br>>> delete this information from your system. Use, dissemination,<br>>> distribution, or reproduction of this transmission by unintended<br>> recipients is not authorized and may be unlawful.<br>> <br>> <br>> <br>>
---------------------------------------------------------------------<br>> This transmission (including any attachments) may contain confidential <br>> information, privileged material (including material protected by the <br>> solicitor-client or other applicable privileges), or constitute non-public<br><br>> information. Any use of this information by anyone other than the intended<br><br>> recipient is prohibited. If you have received this transmission in error, <br>> please immediately reply to the sender and delete this information from<br>your <br>> system. Use, dissemination, distribution, or reproduction of this <br>> transmission by unintended recipients is not authorized and may be<br>unlawful.<br><br><br></pre></blockquote></td></tr></table><br>