DHCPv4 and DHCPv6 are now more consistent when logging the
reasons why a packet was dropped. This information is now
available on debuglevel 15. Also added a section in the ARM
- discussing the debuglevels. The subnet selection failed log
+ discussing the debug levels. The subnet selection failed log
message now provides more useful information about the subnet.
(Gitlab #1915, #1916)
1912. [doc] fdupont, tomek
The Kea configuration syntax is now documented in BNF notation.
See new appendix in the ARM.
- (Gitlab #504)
+ (Gitlab #504, #745)
1911. [bug] andrei
Fixed a minor regression where kea-admin and keactrl would output
The non-relational nature of Cassandra makes it exceedingly difficult to implement more complex
DHCP features, such as the configuration backend. The configuration backend requires over 20
-tables of tighly related data that change over time and need to be kept in sync. With the
+tables of tightly coupled data that change over time and need to be kept in sync. With the
Cassandra philosophy of data duplication, this would require creating and maintaining a massive
number of tables. To be specific, there are 36 different types of `get` queries in the DHCPv4
code for the MySQL Configuration Backend. In the worst case, where each query required its
if (!ok) {
std::cout << "UDP data received not in order! Checking un ordered delivery"
<< std::endl;
- // We need to
+ // We need to double iterate through the messages to check every one
+ // against one another.
for (int i = 0; i < num_msgs; i++) {
ok = false;
for (int j = 0; j < num_msgs; j++) {
ASSERT_EQ(num_msgs, sent_ncrs_.size());
ASSERT_EQ(num_msgs, received_ncrs_.size());
- // Verify that what we sent matches what we received. Ingore the order
+ // Verify that what we sent matches what we received. Ignore the order
// if necessary.
checkUnordered(num_msgs, sent_ncrs_, received_ncrs_);