ISC DHCP Users

Option 82 Issues

classic Classic list List threaded Threaded
♦
♦
 6 messages Options
Mike Hammett
Reply | Threaded
Open this post in threaded view
♦
♦
|

Option 82 Issues

Mike Hammett
=====
# dhcpd.conf
option domain-name "[redacted]";

default-lease-time 60000;
max-lease-time 720000;

ddns-update-style none;

log-facility local7;

# Local
subnet [redacted] netmask 255.255.255.224 {
        deny unknown-clients;
        }
# 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;
                }
[cut for brevity]
=====



It's not going to serve any local DHCP, only remote, but I figured out I needed a local subnet for it to even fire up.

I don't want any pools, only reservations\hosts assigning the same IP to the same DSLAM port (well, to be more specific, to the line I have configured to send from the DSLAM) every time.

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.

Webmin recognizes all of the host entries (although not the circuit-id information because it doesn't support it), so I assume they're setup correctly.

I also get this, but Google was no help, "parse_option_buffer: malformed option vendor.<unknown> (code 808464740): option length exceeds option buffer length." Calix says the agent.circuit-id field can support 63 characters and I'm only using 27. Could be related, could not be. I pulled the information in agent.circuit-id out of tcpdump as dhcpd didn't seem to have a way of revealing that.



Thoughts?


-----
Mike Hammett
Intelligent Computing Solutions

Midwest Internet Exchange

The Brothers WISP

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Christian Kratzer
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Option 82 Issues

Christian Kratzer
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:   [hidden email]               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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Mike Hammett
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Option 82 Issues

Mike Hammett
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.

From: "Christian Kratzer" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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:   [hidden email]               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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Patrick Trapp
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Option 82 Issues

Patrick Trapp
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 <[hidden email]> 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.

From: "Christian Kratzer" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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:   [hidden email]               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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

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

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Mike Hammett
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Option 82 Issues

Mike Hammett
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.

From: "Patrick Trapp" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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 <[hidden email]> 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.

From: "Christian Kratzer" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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:   [hidden email]               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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

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

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


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Patrick Trapp
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Option 82 Issues

Patrick Trapp

Sounds like quite a project and more than a little familiar. Glad you appear to have a clear path forward, long as it may be.

 

All the best.

 

From: dhcp-users <[hidden email]> On Behalf Of Mike Hammett
Sent: Saturday, August 25, 2018 4:29 PM
To: Users of ISC DHCP <[hidden email]>
Subject: Re: Option 82 Issues

 

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.

From: "Patrick Trapp" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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 <[hidden email]> 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.

From: "Christian Kratzer" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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:   [hidden email]               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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

 

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


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

 


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Free forum by Nabble Edit this page