Tim Howe writes:
> This had actually occurred to me, but I only saw the
> outbound-interface in the docs as being an option for IPv4. Also, when
> I try to add it to the interface clause for dhcpv6 I get a syntax error.
=> you are right: the code for DHCPv6 is missing without good reasons,
On Mon, 22 Jan 2018 23:38:10 +
Francis Dupont wrote:
> => 2607:fda0:101:1601::1 (the relay closest to the server) is not
> reachable according to the kernel which returns an error on sendmsg()
> system call. IMHO something is wrong in the server system configuration.
> BTW if the problem is
Tim Howe writes:
> ...
> 2018-01-22 12:11:34.743 DEBUG [kea-dhcp6.packets/55758] DHCP6_RESPONSE_DATA r
> esponding with packet type 2 data is localAddr=[2607:fda0:101:1600::2]:547 re
> moteAddr=[2607:fda0:101:1601::1]:547
> msgtype=2(ADVERTISE), transid=0xa09dfc
>
> 2018-01-22 12:11:34.743 ERROR [k
On Fri, 12 Jan 2018 06:15:44 +
Francis Dupont wrote:
> 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 th
On Fri, 12 Jan 2018 06:15:44 +
Francis Dupont wrote:
> 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 th
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":
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
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
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
Just a shot in the dark, but have you tried a /64 pool? Maybe Kea doesn’t
support subnets longer than that.
> On Jan 10, 2018, at 3:18 PM, Tim Howe wrote:
>
> Any clue is much appreciated. I haven't actually managed a single
> working config yet (have v4 working fine).
>
> I'm trying to get
Any clue is much appreciated. I haven't actually managed a single
working config yet (have v4 working fine).
I'm trying to get just the most stripped down basic DHCP6 functions
working ATM.
There is only one subnet configured, and I'm not trying to select it in
any fancy ways yet, but it seems t
15 matches
Mail list logo
