Bug 354 - Example of the dhcpd.conf file contains a nested subnet section
Summary: Example of the dhcpd.conf file contains a nested subnet section
Status: ASSIGNED
Alias: None
Product: LTSP
Classification: Unclassified
Component: ltspcfg (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Jim McQuillan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 107124
  Show dependency treegraph
 
Reported: 2004-03-20 08:50 UTC by Jim McQuillan
Modified: 2018-07-05 10:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jim McQuillan 2004-03-20 08:50:24 UTC
It has been reported that the dhcpd.conf file created by ltspcfg contains a
nested subnet section.  It is commented out, so it doesn't cause a big problem,
but the comments indicate that you can un-comment that section to create a pool
of IP addresses.  It should be moved out of the enlosing section.

Here is the email sent by Jose Manuel Gomez:

================================================================================

Hello Jim

I have found something that may be an error on the dhcpd.conf file 
generated by ltspcfg.

This config includes this code:

subnet 172.27.0.0 netmask 255.255.0.0 {
    use-host-decl-names      on;
    option log-servers       172.27.6.152;


##
## If you want to use static IP address for your workstations, then un-comment
## the following section and modify to suit your network.
## Then, duplicate this section for each workstation that needs a static
## IP address.
##
##    host ws001 {                                       <----- Fix this
hostname
##        hardware ethernet    00:11:22:33:44:55;           <-- Fix this MAC
addr
##        fixed-address        192.168.0.1;                 <-- Fix this IP
addr
##        filename             "/lts/vmlinuz-2.4.21-ltsp-1";
##    }

##
## If you want to use a dynamic pool of addresses, then un-comment the
following
## lines and modify to match your network.
##
##    subnet  192.168.0.0 netmask 255.255.255.0 {
##        range dynamic-bootp 192.168.0.1 192.168.0.253;
##    }
##


}

As you can see, subnet section is repeated. The error says 'subnet section not
allowed' or something like that.

I now have this:

subnet 172.27.0.0 netmask 255.255.0.0 {

    use-host-decl-names      on;
    option log-servers       172.27.6.152;

##
## If you want to use static IP address for your workstations, then un-comment
## the following section and modify to suit your network.
## Then, duplicate this section for each workstation that needs a static
## IP address.
##
#     host ws001 {                                       <----- Fix this
hostname
#         hardware ethernet    00:1E:A6:1C:19:D3;           <-- Fix this MAC
addr
#         fixed-address        172.27.6.5;                 <-- Fix this IP addr
#         filename             "/lts/vmlinuz-2.4.24-ltsp-1";
#         filename              "/lts/2.4.24-ltsp-1/pxelinux.0";
#     }

pool {
  option domain-name-servers bogus.example.com;
  max-lease-time 28800;
  range 172.27.6.10 172.27.6.20;
  if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
    filename "/eb-nforce2.zpxe";
    #filename "/lts/vmlinuz.ltsp";
  } else {
    filename "/lts/vmlinuz.ltsp";
  }
  allow unknown clients;
  #deny unknown clients;
}



}
Comment 1 chemtech 2013-03-15 13:31:47 UTC
Jim McQuillan,
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 2 Jim McQuillan 2013-03-15 13:36:19 UTC
No, close it.


On Fri, Mar 15, 2013 at 9:31 AM, <bugzilla-daemon@freedesktop.org> wrote:

>   *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=354#c1> on bug
> 354 <https://bugs.freedesktop.org/show_bug.cgi?id=354> from chemtech<patsev.anton@gmail.com>
> *
>
> Jim McQuillan,
> Do you still experience this issue with newer drivers ?
> Please check the status of your issue.
>
>  ------------------------------
> You are receiving this mail because:
>
>    - You are the assignee for the bug.
>    - You reported the bug.
>
>


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.