> 
> So let me paint the picture here. Several subnets. Each behind a common
> firewall and each in its own firewall zone. Each subnet has a dhcp relay
> listener via the firewall that forwards the request to a server. Lets call
> it DHCP1.  That server handles ALL dhcp requests from ALL subnets as well
> as, via DDNS, updating the local DNS zone. It also services it's own local
> subnet dhcp requests. Can you help me just build out one of these subnets?
> The documentation is just really hard to follow. I went from just building
> pools to now creating delegated networks with subnets within subnets and
> defining some delegated-len that is even another number. None of this makes
> sense and the documentation doesn't help. The link you sent me shows some
> weird example where a subnet actually returns a totally different subnet??
> Why? I do NOT understand why that is the example the documentation chose.
> Can't we just show a simple example?
> 

Here’s a redacted excerpt of a config file I’ve got doing just that…Hope that 
helps.


    "interfaces-config" : {
      "interfaces" : [ “eth0/xxxx:xxxx:xxxx:1::200:231" ],
      "service-sockets-require-all": true
    },
    "subnet6": [
      # The subnet where the server is attached
      #  (i.e., the server has an address in this subnet)
      {
        "id": 1,
        "user-context": {
          "vlan": “first-clan"
        },
        "subnet": “xxxx:xxxx:xxxx:1::/64",
        "rapid-commit": true,
        "interface": "eth0",
        "pools": [
          {
            # Use a broad range for addres assignment, but avoid conflicts with 
SLAAC
            "pool": “xxxx:xxxx:xxxx:1::d8c:0:0 - 
xxxx:xxxx:xxxx:1::d8c:ffff:ffff"
          }
        ],
        "pd-pools": [
          {
            # Use the a particular /112 prefix for temporary addresses
            #  (i.e., direct application of RFC 4941)
            # Some /64 prefixes available for Prefix Delegation (RFC 3633)
            "prefix": "xxxx:xxxx:xxxx:4000::",
            "delegated-len": 56,
            "prefix-len": 52
          }
        ],
        "reservations": [
          {
            "hostname": "conserver01-lan",
            "hw-address": "dc:a6:32:8b:13:8c",
            "ip-addresses": [
                "xxxx:xxxx:xxxx:1::200:135"
            ]
          }
        ]
      },
      {
        "id": 2,
        "user-context": {
          "vlan": “second-clan"
        },
        "subnet": “xxxx:xxxx:xxxx:2000::/64",
        "rapid-commit": true,
        "pools": [
          {
            # Use a broad range for addres assignment, but avoid conflicts with 
SLAAC
            "pool": "xxxx:xxxx:xxxx:2000::d8c:0:0 - 
xxxx:xxxx:xxxx:2000::d8c:ffff:ffff"
          }
        ],
        "interface": "eth1",
        "reservations": [
          {
            "hostname": "test-pi1",
            "duid": "00:03:00:01:d8:3a:dd:xx:xx:xx",
            "ip-addresses": [
                "xxxx:xxxx:xxxx:2000::200"
            ]
          },
          {
            "hostname": "test-pi2",
            "duid": "00:04:f3:8f:6b:10:ea:6c:47:17:43:43:ba:1f:27:48:20:7f",
            "ip-addresses": [
                "xxxx:xxxx:xxxx:2000::201"
            ]
          }
        ]
      }
    ]


-- 
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users

Reply via email to