Send kea-dev mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."


Today's Topics:

   1. Re:  Building KEA on OpenBSD (Mike)
   2. Re:  Building KEA on OpenBSD (Patrik Lundin)
   3. Re:  DHCPv6 server reaction to repeated Solicit/Requests
      (Marcin Siodelski)


----------------------------------------------------------------------

Message: 1
Date: Sun, 6 Dec 2015 12:30:30 -0500
From: Mike <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Building KEA on OpenBSD
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252

On 12/6/2015 12:02 PM, Mike wrote:
> On 12/6/2015 11:36 AM, Patrik Lundin wrote:
>> Hello,
>>
>> I am working on a OpenBSD port for KEA 0.9.2 and I have some questions.
>>
>> First of all, running tests currently fail, however it seems to be a
>> problem with the tests rather than the code being tested:
>> ===
>> [major snip]
> 
> 
> Last week I wrote a quick script (more of a sketch than a script) to
> download and build kea 0.9.2 on OpenBSD 5.8 current.  All the tests
> pass.  Specifically, here's the test that fails in your test:
> 
> START TEST keactrl.start_all_servers_no_verbose_test
> Creating Kea configuration file:
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/test_config.json.
> Creating keactrl configuration file:
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/keactrl_test.conf.
> Kea log will be stored in
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/test.log.
> Starting Kea: /home/kea-build/kea-0.9.2/src/bin/keactrl/keactrl start -c
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/keactrl_test.conf -s all
> INFO/keactrl: Starting kea-dhcp4 -c
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/test_config.json
> INFO/keactrl: Starting kea-dhcp6 -c
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/test_config.json
> INFO/keactrl: Starting kea-dhcp-ddns -c
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/test_config.json
> INFO/test_lib: wait_for_message DHCP6_CONFIG_COMPLETE: ..
> INFO/test_lib: wait_for_message DHCP4_CONFIG_COMPLETE: .
> INFO/test_lib: wait_for_message DCTL_CONFIG_COMPLETE: .
> Stopping Kea: /home/kea-build/kea-0.9.2/src/bin/keactrl/keactrl stop  -c
> /home/kea-build/kea-0.9.2/src/bin/keactrl/tests/keactrl_test.conf
> INFO/keactrl: Stopping kea-dhcp4...
> INFO/keactrl: Stopping kea-dhcp6...
> INFO/keactrl: Stopping kea-dhcp-ddns...
> INFO/test_lib: wait_for_message DHCP6_SHUTDOWN: .
> INFO/test_lib: wait_for_message DHCP4_SHUTDOWN: .
> INFO/test_lib: wait_for_message DHCP_DDNS_SHUTDOWN: .
> INFO/test_lib: wait_for_server_down kea-dhcp: .
> PASSED keactrl.start_all_servers_no_verbose_test
> 
> 
> 
> 
> I have not yet had the chance to set up an environment to see if the kea
> I build actually works beyond passing the tests. :)  I hope to get there
> in the next couple of weeks...
> 
> 
> 
> If it helps, here is the script I use:
> [snip]


In case it matters, here are the packages and their versions I had
installed when I built kea (some were installed for reasons other than kea):

% pkg_info
autoconf-2.69p1     automatically configure source code on many Un*x
platforms
automake-1.15       GNU Standards-compliant Makefile generator
boost-1.58.0p0      free peer-reviewed portable C++ source libraries
bzip2-1.0.6p7       block-sorting file compressor, unencumbered
curl-7.45.0p0       get files from FTP, Gopher, HTTP or HTTPS servers
cvsps-2.1p0         generate patchsets from CVS repositories
drill-1.6.17        DNS debugger
echoping-5.2.0      test performance of a remote TCP service
gettext-0.19.6      GNU gettext runtime libraries and programs
git-2.6.3           GIT - Tree History Storage Tool
gmake-4.1p0         GNU make
gtar-1.28p1         GNU version of the traditional tape archiver
gtest-1.4.0p2       C++ unit test framework
iwn-firmware-5.11p1 firmware binary images for iwn(4) driver
libffi-3.2.1        Foreign Function Interface
libiconv-1.14p3     character set conversion library
libidn-1.32         internationalized string handling
libldns-1.6.17p1    DNS library modelled after Net::DNS
libltdl-2.4.2p1     GNU libtool system independent dlopen wrapper
libtool-2.4.2p0     generic shared library support script
log4cplus-1.1.2     logging API for C++
logtail-1.3.17      mail anomalies in the system logfiles to the
administrator
metaauto-1.0p1      wrapper for gnu auto*
nano-2.4.2          Pico editor clone with enhancements
nghttp2-1.4.0       library for HTTP/2
p5-Error-0.17024    error/exception handling in an OO-ish way
quirks-2.161        exceptions to pkg_add rules
rsync-3.1.1         mirroring/synchronization over low bandwidth links
sipcalc-1.1.6       ipv4 and ipv6 subnet calculator
smartmontools-6.4   control and monitor storage systems using SMART
tcsh-6.19.00        extended C-shell with many useful features
vnstat-1.14p4       network traffic monitor
xz-5.2.2            LZMA compression and decompression tools




------------------------------

Message: 2
Date: Sun, 6 Dec 2015 18:48:32 +0100
From: Patrik Lundin <[email protected]>
To: Mike <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] Building KEA on OpenBSD
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

On Sun, Dec 06, 2015 at 12:02:09PM -0500, Mike wrote:
> On 12/6/2015 11:36 AM, Patrik Lundin wrote:
> > Hello,
> > 
> > I am working on a OpenBSD port for KEA 0.9.2 and I have some questions.
> > 
> > First of all, running tests currently fail, however it seems to be a
> > problem with the tests rather than the code being tested:
> > ===
> > [major snip]
> 
> 
> Last week I wrote a quick script (more of a sketch than a script) to
> download and build kea 0.9.2 on OpenBSD 5.8 current.  All the tests
> pass.  Specifically, here's the test that fails in your test:
> 

Thanks for the information :). I am guessing the arguments for the
involved processes differ when the tests are run via the ports
infrastructure rather than directly like you are doing.

I still feel the pgrep diff is suitable however, since it is more strict
in what it is matching against.

-- 
Patrik Lundin


------------------------------

Message: 3
Date: Mon, 7 Dec 2015 11:49:48 +0100
From: Marcin Siodelski <[email protected]>
To: "Templin, Fred L" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] DHCPv6 server reaction to repeated
        Solicit/Requests
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

Fred,

The behavior you have described is incorrect on the server side. When
the client reboots and issues a Solicit the server should find existing
binding for this client and return this binding in the Reply message
(assuming that the lease doesn't expire and is not hijacked by another
client). I am surprised that you observe different behavior.

Can you please answer the following clarification questions:
- What do you mean by "Kea ignores subsequent Solicit". Does it mean
that Kea doesn't respond to Solicit, i.e. drops it?
- What is the lease database backend you're using? Memfile - leases
stored in the CSV file?
- Is the client only requesting PD or also NA?
- When the client reboots, does it use the same client identifier (DUID)
when it issues a second Solicit?
- Can you please provide me a traffic capture that demonstrates this
behavior?

Marcin

On 02.12.2015 18:45, Templin, Fred L wrote:
> Hi,
>
> I have a DHCPv6 client that frequently reboots, loses its memory,
> comes back up,
> and reissues a DHCPv6 PD Solicit/Request. It appears that the kea
> server issues
> the PD on the first Solicit/Request, but then ignores subsequent
> Solicit/Requests
> after each client reboot. Rebooting the kea server clears this condition.
>
> Is this the correct behavior per RFC3315/RFC3633? Or, should the kea
> server
> process each subsequent Solicit/Request as if it were a Renew?
>
> Thanks - Fred
> [email protected]
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
>



------------------------------

_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev

End of kea-dev Digest, Vol 21, Issue 5
**************************************

Reply via email to