Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

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
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

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


Today's Topics:

   1. Re: Option 82 Issues (Mike Hammett)
   2. Re: Option 82 Issues (Patrick Trapp)


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

Message: 1
Date: Sat, 25 Aug 2018 07:15:50 -0500 (CDT)
From: Mike Hammett <isc-dhcp-us...@ics-il.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Option 82 Issues
Message-ID:
        <1421770463.2746.1535199343393.JavaMail.mhammett@ThunderFuck>
Content-Type: text/plain; charset="utf-8"

Long term I can probably move 192.168.120.x into 172.19.50.x. 

Short term, I'll see if the shared network will work. There is actually a 
single 192.168.120.x across all sites and I'm on a project to break them up 
into a subnet per site (172.19.50.x, 172.19.40.x, etc.). I'll work on a shared 
network for everything and then "unshare" when I can complete the migration. 


Thank you. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Christian Kratzer" <ck-li...@cksoft.de> 
To: "Users of ISC DHCP" <dhcp-users@lists.isc.org> 
Sent: Saturday, August 25, 2018 2:02:49 AM 
Subject: Re: Option 82 Issues 

Hi, 

On Fri, 24 Aug 2018, Mike Hammett wrote: 
<snipped/> 
> # Genoa 
> subnet 172.19.50.0 netmask 255.255.255.0 { 
> authoritative; 
> deny unknown-clients; 
> } 
> 
> 
> include "/etc/dhcp/dhcpd.d/Genoa.mgmt"; 
> # DSLAMs 
> subnet 192.168.120.0 netmask 255.255.255.0 { 
> } 
> #Genoa.mgmt 
> host Genoa_01_01_01 { 
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL1:0.36"; 
> fixed-address 172.19.50.1; 
> } 
> host Genoa_01_01_02 { 
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL2:0.36"; 
> fixed-address 172.19.50.2; 
> } 
> host Genoa_01_01_03 { 
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL3:0.36"; 
> fixed-address 172.19.50.3; 
> } 
<snippped/> 
> I added the DSLAMs subnet to stop this, " DHCPDISCOVER from d8:b6:b7:ea:8d:44 
> via 192.168.120.168: unknown network segment", but instead I got this, " 
> DHCPDISCOVER from d8:b6:b7:ea:8d:44 via 192.168.120.168: network 
> 192.168.120.0/24: no free leases". It isn't supposed to be getting an address 
> in the 192.168 range, but in the 172.19 range. That's why I specified the 
> host file. 

your issue is that your request is coming from the 192.168.120.0/24 range which 
does not match the 172.19.50.0/24 range your have cofigured for your hosts. 

You have two options depending on your network topology: 

1. configure the relay to send from the 172.19.50.0/24 range. 

2. put bot 192.168.120.0/24 and 172.19.50.0/24 subnets into a shared network. 


Greetings 
Christian 



-- 
Christian Kratzer CK Software GmbH 
Email: c...@cksoft.de Wildberger Weg 24/2 
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden 
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart 
Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer 
Web: http://www.cksoft.de/ 
_______________________________________________ 
dhcp-users mailing list 
dhcp-users@lists.isc.org 
https://lists.isc.org/mailman/listinfo/dhcp-users 

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

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

Message: 2
Date: Sat, 25 Aug 2018 21:24:00 +0000
From: Patrick Trapp <ptr...@nex-tech.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Option 82 Issues
Message-ID: <77e3f2f7-1a32-46b4-baad-e76c885e3...@nex-tech.com>
Content-Type: text/plain; charset="us-ascii"

We have to do exactly what Christian prescribed. The source network is not 
controlled by this DHCP system, so the shared network includes only the network 
statement, no provision to assign addresses. If you are able to carve up that 
192.168 range, that should work fine for you.

Patrick

On Aug 25, 2018, at 7:16 AM, Mike Hammett 
<isc-dhcp-us...@ics-il.net<mailto:isc-dhcp-us...@ics-il.net>> wrote:

Long term I can probably move 192.168.120.x into 172.19.50.x.

Short term, I'll see if the shared network will work. There is actually a 
single 192.168.120.x across all sites and I'm on a project to break them up 
into a subnet per site (172.19.50.x, 172.19.40.x, etc.). I'll work on a shared 
network for everything and then "unshare" when I can complete the migration.


Thank you.



-----
Mike Hammett
Intelligent Computing Solutions<http://www.ics-il.com/>
[http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL>
Midwest Internet Exchange<http://www.midwest-ix.com/>
[http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix>
The Brothers WISP<http://www.thebrotherswisp.com/>
[http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>
________________________________
From: "Christian Kratzer" <ck-li...@cksoft.de<mailto:ck-li...@cksoft.de>>
To: "Users of ISC DHCP" 
<dhcp-users@lists.isc.org<mailto:dhcp-users@lists.isc.org>>
Sent: Saturday, August 25, 2018 2:02:49 AM
Subject: Re: Option 82 Issues

Hi,

On Fri, 24 Aug 2018, Mike Hammett wrote:
<snipped/>
> # Genoa
> subnet 172.19.50.0 netmask 255.255.255.0 {
> authoritative;
> deny unknown-clients;
> }
>
>
> include "/etc/dhcp/dhcpd.d/Genoa.mgmt";
> # DSLAMs
> subnet 192.168.120.0 netmask 255.255.255.0 {
> }
> #Genoa.mgmt
> host Genoa_01_01_01 {
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL1:0.36";
> fixed-address 172.19.50.1;
> }
> host Genoa_01_01_02 {
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL2:0.36";
> fixed-address 172.19.50.2;
> }
> host Genoa_01_01_03 {
> host-identifier option agent.circuit-id "Genoa_01_01 atm 1/DSL3:0.36";
> fixed-address 172.19.50.3;
> }
<snippped/>
> I added the DSLAMs subnet to stop this, " DHCPDISCOVER from d8:b6:b7:ea:8d:44 
> via 192.168.120.168: unknown network segment", but instead I got this, " 
> DHCPDISCOVER from d8:b6:b7:ea:8d:44 via 192.168.120.168: network 
> 192.168.120.0/24: no free leases". It isn't supposed to be getting an address 
> in the 192.168 range, but in the 172.19 range. That's why I specified the 
> host file.

your issue is that your request is coming from the 192.168.120.0/24 range which 
does not match the 172.19.50.0/24 range your have cofigured for your hosts.

You have two options depending on your network topology:

1. configure the relay to send from the 172.19.50.0/24 range.

2. put bot 192.168.120.0/24 and 172.19.50.0/24 subnets into a shared network.


Greetings
Christian



--
Christian Kratzer                   CK Software GmbH
Email:   c...@cksoft.de<mailto:c...@cksoft.de>               Wildberger Weg 24/2
Phone:   +49 7032 893 997 - 0       D-71126 Gaeufelden
Fax:     +49 7032 893 997 - 9       HRB 245288, Amtsgericht Stuttgart
Mobile:  +49 171 1947 843           Geschaeftsfuehrer: Christian Kratzer
Web:     http://www.cksoft.de/
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org<mailto:dhcp-users@lists.isc.org>
https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org<mailto:dhcp-users@lists.isc.org>
https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180825/16c11651/attachment.html>

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

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


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

End of dhcp-users Digest, Vol 118, Issue 20
*******************************************

Reply via email to