I found at least 2 easy ways to fix your problem:
- the first one is to have a second relay which fills the link address:
the code skips all link addresses which are undefined or link local
as it wants to be able to identify the relay. BTW the interface-id
option must be added by the first (
Mr. Dupont, thanks again for taking the time to answer a question of
mine...
On Thu, 11 Jan 2018 23:44:59 +
Francis Dupont wrote:
> => the link-address must not be :: cf RFC 3315 20.1.1 page 59.
> This is critical because it is the way Kea subnet selection recognizes
> direct vs relayed in
Tim Howe writes:
> I somehow managed to not make it part of my paste in my
> previous email, but I am attempting to select the subnet based on the
> interface-id (option-18).
=> so you have a relay.
> "subnet6": [
> {
> "interface-id": "3/2/1/1",
> "subnet":
Jason Guy writes:
> I do not see any documentation for specifying parameters this way, or what
> specifically needs to be entered into the row to utilize this. Any
> information or pointers on how to do this would be helpful.
=> there is a documentation somewhere but I don't remember where it is..
Tim Howe writes:
> 2018-01-11 09:04:51.971 ERROR [kea-dhcp6.dhcp6/45759] DHCP6_INIT_FAIL failed
> to initialize Kea server: configuration error using file '/usr/local/etc/kea/
> kea.conf': subnet configuration failed: parser error: interface (defined for
> locally reachable subnets) and interface
On Thu, 11 Jan 2018 08:36:59 +
Francis Dupont wrote:
> Tim Howe writes:
> > "subnet6": [
> > {
> > "subnet": "2607:fda0:101:1601::/64",
> > "pools": [ { "pool": "2607:fda0:101:1601:4::/80" } ]
> > }
> > ]
>
> => add an interface clause in you
Hi all. I am interested in a way to specify options on a per-host
reservation. Looking at the Kea mysql database 'host' table, I see the
following columns:
dhcp4_client_classes
dhcp6_client_classes
dhcp4_next_server
dhcp4_server_hostname
dhcp4_boot_file_name
I do not see any documentation for spec
On Thu, 11 Jan 2018 08:36:59 +
Francis Dupont wrote:
> => add an interface clause in your subnet6
oof. One step forward, two steps back...
2018-01-11 09:04:51.971 ERROR [kea-dhcp6.dhcp6/45759] DHCP6_INIT_FAIL failed to
initialize Kea server: configuration error using file
'/usr/l
On Thu, 11 Jan 2018 08:36:59 +
Francis Dupont wrote:
> => add an interface clause in your subnet6 (I assume clients are
> directly connected as you didn't mention relays). Without it
> no subnet is selected or with other words the server has no idea
> about where is the client...
>
> Regar
On Wed, 10 Jan 2018, Paiva, Gilson de wrote:
We've been using Mikrotik RouterOS as a DHCP server for a while now and
we're searching for alternatives since we want to expand our network... Kea
would be perfect since we 100% can integrate our backend applications to
feed data to it on its SQL tab
ddns-rev-domainname is marked as not translatable in the migration
assistant...
In the Kea code (d2_cfg_mgr.*) the constant has a @todo saying it should
be configurable so you should ask for this. Now we have a lot of things
to do for the current release and limited man-power...
Regards
Francis
Tim Howe writes:
> "subnet6": [
> {
> "subnet": "2607:fda0:101:1601::/64",
> "pools": [ { "pool": "2607:fda0:101:1601:4::/80" } ]
> }
> ]
=> add an interface clause in your subnet6 (I assume clients are
directly connected as you didn't mention relays
12 matches
Mail list logo
