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: DHCP server behing Cisco relay (Hernan Saltiel)
2. Re: DHCP server behing Cisco relay (Jeff Wieland)
3. Re: DHCP server behing Cisco relay (Hernan Saltiel)
----------------------------------------------------------------------
Message: 1
Date: Fri, 20 May 2016 23:09:12 -0300
From: Hernan Saltiel <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP server behing Cisco relay
Message-ID:
<CAMXef5KAG0kQjacqC+V1ZQgHN=wz-txflmkz_gwynjtzdok...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Jos?,
Today, I have a Windows machine running a DHCP server, with IP address
192.168.120.20/24, and serving DHCP address range 10.0.0.10 ->
10.0.200.200. Then, I can assume that my Cisco switch is working just fine.
It's a soho switch, so it has only "secondary subnets", a concept that may
sound like vlans, but are not. But this is working fine.
Thanks, and best regards,
HeCSa.
On Fri, May 20, 2016 at 6:46 PM, Jos? Queiroz <[email protected]> wrote:
> Hi Hernan,
>
> Could you please post the Cisco Switch's relevant configuration, also?
> Including the VLAN interfaces serving the 10.0.0.0/16 network.
>
> By the way, does this switch have conectivity with your dhcp server? This
> is mandatory for the DHCP relay to work, as the relay agent needs to
> forward DHCP messages for clients in unicast to the DHCP server; and the
> reverse path must be available also, once you're checking the direct path,
> give some time checking this also.
>
>
> 2016-05-20 17:58 GMT-03:00 Hernan Saltiel <[email protected]>:
>
>> Hi everybody.
>>
>> Maybe I'm asking something previously answered.
>> I configured my new iscp-dhcp-server (Ubuntu 16.04) to server requests
>> from a network of APs.
>> Those APs are connected to a Cisco switch, having 192.168.120.1/24 as
>> primary address, and a secondary subnet with address 10.0.0.1/16 (yes,
>> 16...). It has relay configured, just to send the dhcp requests to
>> 192.168.120.20, a Windows machine.
>> Today I have a Windows machine connected there, where I use the AP
>> controller software, and TFTPD64, a thin software that works as a DHCP
>> server. I configured there a range (10.0.0.10 -> 10.0.200.200) and
>> everything works well, but it's Windows, then from time to time, I have to
>> reboot the system.
>> This is why I configured the new machine as 192.168.120.40/24, installed
>> isc-dhcp-server package, and configured the following lines on
>> /etc/dhcp/dhcpd.conf:
>>
>> default lease-time 600;
>> max-lease-time 7200;
>>
>> subnet 10.0.0.0 netmask 255.255.0.0 {
>> range 10.0.0.10 10.0.200.200;
>> option subnet-mask 255.255.0.0;
>> option routers 10.0.0.1;
>> option domain-name-servers 8.8.8.8, 8.8.4.4;
>> }
>>
>> subnet 192.168.120.0 netmask 255.255.255.0 {
>> }
>>
>> When I start the server, I only see it trying to answer requests using
>> network 192.168.120.0, then saying "no free leases", and not serving any
>> 10.0.0.0/16 address.
>>
>> Now I'm living with TFTPD64, but I plan to move that to a better solution.
>> Does anybody know about this configuration? Is there something I'm doing
>> wrong?
>> Thanks a lot in advance, and best regards.
>>
>> --
>> HeCSa
>>
>> _______________________________________________
>> dhcp-users mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
--
HeCSa
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160520/f213e607/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 20 May 2016 22:09:14 -0400
From: Jeff Wieland <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP server behing Cisco relay
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On May 20, 2016 4:58:23 PM EDT, Hernan Saltiel <[email protected]> wrote:
>Hi everybody.
>
>Maybe I'm asking something previously answered.
>I configured my new iscp-dhcp-server (Ubuntu 16.04) to server requests
>from
>a network of APs.
>Those APs are connected to a Cisco switch, having 192.168.120.1/24 as
>primary address, and a secondary subnet with address 10.0.0.1/16 (yes,
>16...). It has relay configured, just to send the dhcp requests to
>192.168.120.20, a Windows machine.
>Today I have a Windows machine connected there, where I use the AP
>controller software, and TFTPD64, a thin software that works as a DHCP
>server. I configured there a range (10.0.0.10 -> 10.0.200.200) and
>everything works well, but it's Windows, then from time to time, I have
>to
>reboot the system.
>This is why I configured the new machine as 192.168.120.40/24,
>installed
>isc-dhcp-server package, and configured the following lines on
>/etc/dhcp/dhcpd.conf:
>
>default lease-time 600;
>max-lease-time 7200;
>
>subnet 10.0.0.0 netmask 255.255.0.0 {
> range 10.0.0.10 10.0.200.200;
> option subnet-mask 255.255.0.0;
> option routers 10.0.0.1;
> option domain-name-servers 8.8.8.8, 8.8.4.4;
>}
>
>subnet 192.168.120.0 netmask 255.255.255.0 {
>}
>
>When I start the server, I only see it trying to answer requests using
>network 192.168.120.0, then saying "no free leases", and not serving
>any
>10.0.0.0/16 address.
>
>Now I'm living with TFTPD64, but I plan to move that to a better
>solution.
>Does anybody know about this configuration? Is there something I'm
>doing
>wrong?
>Thanks a lot in advance, and best regards.
>
>--
>HeCSa
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>dhcp-users mailing list
>[email protected]
>https://lists.isc.org/mailman/listinfo/dhcp-users
Since both networks are on the same wire, I believe that you need to place your
two subnet statements within a shared-network statement.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160520/adf672ff/attachment-0001.html>
------------------------------
Message: 3
Date: Fri, 20 May 2016 23:51:08 -0300
From: Hernan Saltiel <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP server behing Cisco relay
Message-ID:
<CAMXef5K4veU7iid7kQia24MmuXpcS=ztqhvejx-talhrp__...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks a lot!
I tried that configuration, and now it's working like a charm!
Best regards,
HeCSa.
On Fri, May 20, 2016 at 6:54 PM, Patrick Trapp <[email protected]> wrote:
> Also, if you are intending for addresses to be made available from both of
> the subnets, I believe you may need to define those pools as a shared
> network. Look up shared-network in your handy DHCP documentation, but I
> would wonder if something like this would make a difference:
>
> default lease-time 600;
> max-lease-time 7200;
>
> shared-network Combined-pools {
> subnet 10.0.0.0 netmask 255.255.0.0 {
> range 10.0.0.10 10.0.200.200;
> option subnet-mask 255.255.0.0;
> option routers 10.0.0.1;
>
> option domain-name-servers 8.8.8.8, 8.8.4.4;
> }
>
> subnet 192.168.120.0 netmask 255.255.255.0 {
> }
>
> }
>
> Or, so be more generic
>
> shared-network shared-network-label
> {
> subnet1 x.x.x.x netmask 255.x.x.x
> {
> } (to close subnet1)
> subnet2 y.y.y.y netmask 255.y.y.y
> {
> } (to close subnet2)
> } (to close the shared-network declaration)
>
> ------------------------------
> *From:* [email protected] [[email protected]]
> on behalf of Jos? Queiroz [[email protected]]
> *Sent:* Friday, May 20, 2016 4:46 PM
> *To:* Users of ISC DHCP
> *Subject:* Re: DHCP server behing Cisco relay
>
> Hi Hernan,
>
> Could you please post the Cisco Switch's relevant configuration, also?
> Including the VLAN interfaces serving the 10.0.0.0/16 network.
>
> By the way, does this switch have conectivity with your dhcp server? This
> is mandatory for the DHCP relay to work, as the relay agent needs to
> forward DHCP messages for clients in unicast to the DHCP server; and the
> reverse path must be available also, once you're checking the direct path,
> give some time checking this also.
>
>
> 2016-05-20 17:58 GMT-03:00 Hernan Saltiel <[email protected]>:
>
>> Hi everybody.
>>
>> Maybe I'm asking something previously answered.
>> I configured my new iscp-dhcp-server (Ubuntu 16.04) to server requests
>> from a network of APs.
>> Those APs are connected to a Cisco switch, having 192.168.120.1/24 as
>> primary address, and a secondary subnet with address 10.0.0.1/16 (yes,
>> 16...). It has relay configured, just to send the dhcp requests to
>> 192.168.120.20, a Windows machine.
>> Today I have a Windows machine connected there, where I use the AP
>> controller software, and TFTPD64, a thin software that works as a DHCP
>> server. I configured there a range (10.0.0.10 -> 10.0.200.200) and
>> everything works well, but it's Windows, then from time to time, I have to
>> reboot the system.
>> This is why I configured the new machine as 192.168.120.40/24, installed
>> isc-dhcp-server package, and configured the following lines on
>> /etc/dhcp/dhcpd.conf:
>>
>> default lease-time 600;
>> max-lease-time 7200;
>>
>> subnet 10.0.0.0 netmask 255.255.0.0 {
>> range 10.0.0.10 10.0.200.200;
>> option subnet-mask 255.255.0.0;
>> option routers 10.0.0.1;
>> option domain-name-servers 8.8.8.8, 8.8.4.4;
>> }
>>
>> subnet 192.168.120.0 netmask 255.255.255.0 {
>> }
>>
>> When I start the server, I only see it trying to answer requests using
>> network 192.168.120.0, then saying "no free leases", and not serving any
>> 10.0.0.0/16 address.
>>
>> Now I'm living with TFTPD64, but I plan to move that to a better solution.
>> Does anybody know about this configuration? Is there something I'm doing
>> wrong?
>> Thanks a lot in advance, and best regards.
>>
>> --
>> HeCSa
>>
>> _______________________________________________
>> dhcp-users mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
--
HeCSa
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160520/7d216fea/attachment.html>
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 91, Issue 25
******************************************
