Send dhcp-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: Is there any way to include dynamic info in the DHCP
      REQUEST? (Simon Hobson)
   2. Re: Is there any way to include dynamic info in the DHCP
      REQUEST? (Fredrik Persson)
   3. Re: Is there any way to include dynamic info in the DHCP
      REQUEST? (Sean McMurray)
   4. Re: Is there any way to include dynamic info in the DHCP
      REQUEST? (Fredrik Persson)
   5. Problem with shared-network ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Thu, 4 Jun 2015 13:20:09 +0100
From: Simon Hobson <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Is there any way to include dynamic info in the DHCP
        REQUEST?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Fredrik Persson <[email protected]> wrote:

> Is there a way to include dynamic information in a "send" to the dhcp server?
> 
> Something like this (I know that this does not work, but it gives an idea of 
> what I am looking for):
> 
> interface "eth0" {
>     send <some parameter> $SOME_ENV_VAR;
>     request subnet-mask,
>             broadcast-address,
> /* ... */
> }

Is this a Linux/Unix like system ? I know on GNU/Linux systems, the ISC client 
is typically called by a script, and also calls a script to configure the OS 
when it gets a lease or the lease expires.
Depending on how dynamic the information needs to be, then you can configure 
the client to add customer options - and if you configure the scripts 
correctly, to do something with options returned. You may have issues changing 
the information - you may have to detect the change, and restart the client for 
it to take effect.




------------------------------

Message: 2
Date: Thu, 4 Jun 2015 14:42:26 +0200
From: Fredrik Persson <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Is there any way to include dynamic info in the DHCP
        REQUEST?
Message-ID:
        <camy-fm+z25fvh96qecq+8onzfp9p270rzqxfd73-jgcgujf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Perhaps I was not clear in my original question.

Yes, this is a linux system. I know that there is a script
(dhclient-script) that is run when the lease is aquired but I want to send
things to the dhcp server in the request. And the thing I want to send is
read (in ways not related to the question) from the system during boot.

On Thu, Jun 4, 2015 at 2:20 PM, Simon Hobson <[email protected]> wrote:

> Fredrik Persson <[email protected]> wrote:
>
> > Is there a way to include dynamic information in a "send" to the dhcp
> server?
> >
> > Something like this (I know that this does not work, but it gives an
> idea of what I am looking for):
> >
> > interface "eth0" {
> >     send <some parameter> $SOME_ENV_VAR;
> >     request subnet-mask,
> >             broadcast-address,
> > /* ... */
> > }
>
> Is this a Linux/Unix like system ? I know on GNU/Linux systems, the ISC
> client is typically called by a script, and also calls a script to
> configure the OS when it gets a lease or the lease expires.
> Depending on how dynamic the information needs to be, then you can
> configure the client to add customer options - and if you configure the
> scripts correctly, to do something with options returned. You may have
> issues changing the information - you may have to detect the change, and
> restart the client for it to take effect.
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20150604/e4fe444b/attachment-0001.html>

------------------------------

Message: 3
Date: Thu, 04 Jun 2015 07:17:58 -0700
From: Sean McMurray <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Is there any way to include dynamic info in the DHCP
        REQUEST?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

man dhclient includes documentation for:
-I <dhcp-client-identifier>
               Specify the dhcp-client-identifier option to send to the 
DHCP server.
-H <host-name>
               Specify  the  host-name option to send to the DHCP server.
-V <vendor-class-identifier>
               Specify the vendor-class-identifier option to send to the 
DHCP server.
-R <option>[,<option>...]
               Specify the list of options the client is to request from 
the server.
               The default option list is:
                   subnet-mask, broadcast-address, time-offset, routers,
                   domain-search, domain-name, domain-name-servers, 
host-name,
                   nis-domain, nis-servers, ntp-servers, interface-mtu



On 06/04/2015 04:33 AM, Fredrik Persson wrote:
> Hi, new to the list!
>
> Is there a way to include dynamic information in a "send" to the dhcp 
> server?
>
> Something like this (I know that this does not work, but it gives an 
> idea of what I am looking for):
>
> interface "eth0" {
>     send <some parameter> $SOME_ENV_VAR;
>     request subnet-mask,
>             broadcast-address,
> /* ... */
> }
>
> Thanks in advance,
>
> Fredrik Persson
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20150604/f35c26ae/attachment-0001.html>

------------------------------

Message: 4
Date: Thu, 4 Jun 2015 17:06:43 +0200
From: Fredrik Persson <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Is there any way to include dynamic info in the DHCP
        REQUEST?
Message-ID:
        <camy-fmj+x5a3vosk83fo2-_0fncknqxp_tgp0hvuwjrkjt+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thanks, those would be great and in principal this is what I need.

However, what I am looking for is to set the option 125 ("vivso") in this
way. (I am aware that vivso is also something that can be requested from
the dhcp server, but I am working with the part that sends vivso *from* the
client *to* the server, as required in the TR111 spec.)

On Thu, Jun 4, 2015 at 4:17 PM, Sean McMurray <[email protected]> wrote:

>  man dhclient includes documentation for:
> -I <dhcp-client-identifier>
>               Specify the dhcp-client-identifier option to send to the
> DHCP server.
> -H <host-name>
>               Specify  the  host-name option to send to the DHCP server.
> -V <vendor-class-identifier>
>               Specify the vendor-class-identifier option to send to the
> DHCP server.
> -R <option>[,<option>...]
>               Specify the list of options the client is to request from
> the server.
>               The default option list is:
>                   subnet-mask, broadcast-address, time-offset, routers,
>                   domain-search, domain-name, domain-name-servers,
> host-name,
>                   nis-domain, nis-servers, ntp-servers, interface-mtu
>
>
>
>
> On 06/04/2015 04:33 AM, Fredrik Persson wrote:
>
> Hi, new to the list!
>
>  Is there a way to include dynamic information in a "send" to the dhcp
> server?
>
>  Something like this (I know that this does not work, but it gives an
> idea of what I am looking for):
>
>  interface "eth0" {
>     send <some parameter> $SOME_ENV_VAR;
>     request subnet-mask,
>             broadcast-address,
> /* ... */
>  }
>
>  Thanks in advance,
>
>  Fredrik Persson
>
>
> _______________________________________________
> dhcp-users mailing 
> [email protected]https://lists.isc.org/mailman/listinfo/dhcp-users
>
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20150604/c0c19f29/attachment-0001.html>

------------------------------

Message: 5
Date: Thu, 4 Jun 2015 12:16:56 -0400
From: [email protected]
To: [email protected]
Subject: Problem with shared-network
Message-ID:
        <[email protected]>
Content-Type: text/plain;charset=iso-8859-1

I have a Debian 7.0 running isc-dhcp-server 4.2.2.

My server has a single NIC, and using iproute, I've added additional
addresses (some lines snipped for brevity):

eth0      Link encap:Ethernet  HWaddr 00:50:56:XX:XX:XX
          inet addr:192.168.220.111  Bcast:192.168.220.255 
Mask:255.255.255.0

eth0:1    Link encap:Ethernet  HWaddr 00:50:56:XX:XX:XX
          inet addr:10.111.111.1  Bcast:10.255.255.255  Mask:255.255.255.0

My goal is for the dhcp server to hand out unknown clients addresses from
the 10.111.111.X pool, and known client to get something from the
192.168.220.X pool. Since these are on the same subnet, I [believe] this
requires a shared-network block. My dhcpd.conf file looks like (with
comments and global options stripped out for brevity):

shared-network my-net {
        subnet 192.168.200.0 netmask 255.255.255.0 {
                range 192.168.200.194 192.168.200.200;
                range 192.168.200.215 192.168.200.250;

                ignore unknown-clients;
  <bunch of options removed>
        } #subnet 192.168.200.0

        subnet 10.111.111.0 netmask 255.255.255.0 {
                range 10.111.111.5 10.111.111.200;
                allow unknown-clients;
<bunch of options removed>
        } #subnet 10.111.111.0
} #shared-network

It runs, but only gives out 192 addresses. If I reverse the order, so the
10 subnet declaration comes first, then it hands out 10 addresses, but not
192 addresses.

Any ideas what I am doing wrong?



------------------------------

_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users

End of dhcp-users Digest, Vol 80, Issue 4
*****************************************

Reply via email to