Option 82 Issues

Sat Aug 25 21:29:04 UTC 2018

The 192.168.120 has a bunch of management interfaces, including the DSLAMs, across the whole company. 

I'm breaking up each town into 172.19.xx.xx addresses. Getting the modem management moved, then modem Internet, then whatever modem VLANs\IP spaces there are. Then I'll actually move those DSLAM management IPs out of 192.168.120 into whatever 172.19 space is appropriate for it. Right now everything's a big mess and I'm cutting it up. Eventually I'll be able to drop the 192.168.120 range and possibly the shared network config altogether. 

Oh, I didn't realize I didn't report back. Yeah, the shared network did it. Working on the rest of the project now. 

----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

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

From: "Patrick Trapp" <ptrapp at nex-tech.com> 
To: "Users of ISC DHCP" <dhcp-users at lists.isc.org> 
Sent: Saturday, August 25, 2018 4:24:00 PM 
Subject: Re: Option 82 Issues 

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-users at 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 

Midwest Internet Exchange 

The Brothers WISP 

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

From: "Christian Kratzer" < ck-lists at cksoft.de > 
To: "Users of ISC DHCP" < dhcp-users at 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: ck at 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 at lists.isc.org 
https://lists.isc.org/mailman/listinfo/dhcp-users 

<blockquote>

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

</blockquote>

_______________________________________________ 
dhcp-users mailing list 
dhcp-users at 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/b21442bb/attachment.html>