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 (Jos? Queiroz)
3. Re: DHCP server behing Cisco relay (Niall O'Reilly)
----------------------------------------------------------------------
Message: 1
Date: Fri, 20 May 2016 23:52:25 -0300
From: Hernan Saltiel <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP server behing Cisco relay
Message-ID:
<CAMXef5L1sMzYQXOqPNMd0oB6p6=2Pd4Rpv6E3E6ChcFs+fS=l...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks a lot!
I'm using this configuration now, and is working perfectly.
Best regards,
HeCSa.
On Fri, May 20, 2016 at 11:09 PM, Jeff Wieland <[email protected]> wrote:
> 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.
>
> _______________________________________________
> 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/21a9ce71/attachment-0001.html>
------------------------------
Message: 2
Date: Sat, 21 May 2016 00:20:30 -0300
From: Jos? Queiroz <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP server behing Cisco relay
Message-ID:
<cadeazrwmwqhhuryzyc4fwogbku8-bqkik9mosnagwmb23t0...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Yes, that's it. The concept of dhcp relays is bound to the concept of
network segmentation. If your network is not segmented, you need shared
networks.
Be advised, however, that if you, later, need to offer DHCP also on the
192.168.200.0/24 network, you'll need a configuration much more elaborated.
2016-05-20 23:52 GMT-03:00 Hernan Saltiel <[email protected]>:
> Thanks a lot!
> I'm using this configuration now, and is working perfectly.
> Best regards,
>
> HeCSa.
>
> On Fri, May 20, 2016 at 11:09 PM, Jeff Wieland <[email protected]> wrote:
>
>> 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.
>>
>> _______________________________________________
>> dhcp-users mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
>
> --
> HeCSa
>
> _______________________________________________
> 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/20160521/4f722dcc/attachment-0001.html>
------------------------------
Message: 3
Date: Sat, 21 May 2016 10:47:27 +0100
From: "Niall O'Reilly" <[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; format=flowed
On 21 May 2016, at 3:09, Hernan Saltiel wrote:
> ? ?Today, I have a Windows machine running a DHCP server, with IP
> address?[192.168.120.20/24](http://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.
I expect you'll need a "shared-network" declaration to let dhcpd know
that
the two subnets belong together.
shared-network whatever {
subnet 10.0.0.0 netmask 255.255.0.0 {
# details ...
}
subnet 192.168.120.0 netmask 255.255.255.0 {
# details ...
}
}
I hope this helps.
Best regards,
Niall O'Reilly
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 91, Issue 26
******************************************
