Subject: Re: [ISC-Bugs #48804] any, with libraries containing fix for RT #46709 - isc-dhcp crashes when running in DHCPv6 mode In-Reply-To: X-RT-Original-Encoding: utf-8 X-MS-Tnef-Correlator: Thread-Index: AQHUrBK8FUhv+6XNakSMSF4lA9Haz6Wuz850 X-GM-Message-State: AJcUukfX3VrPZKEkLrZ4/t73u47YwG18xVHO9ecKaE7zGxBIFGbPwlqd pntxtS9/scJVb+q0k3e6B6//GDlWeWk= X-Spam-Status: No, score=0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, FROM_EXCESS_BASE64,RCVD_IN_DNSWL_NONE,SPF_PASS,T_DKIMWL_WL_MED autolearn=disabled version=3.4.1 Message-ID: Date: Mon, 14 Jan 2019 14:18:09 +0000 X-MS-Exchange-Messagesentrepresentingtype: 1 Accept-Language: cs-CZ, en-US X-Google-SMTP-Source: ALg8bN6gkm2gm1yMWVc2MMiovDNaWCsIrPflZPUCe3quJ6hAxU1O+P8a2PqcLEsFEDC+lTtxQQhjZw== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=jE4gyV3DODJVSb5TwvL6j5PLhifX1W5192X5sT0uE6A=; b=o9FV3EuzvOwXpaTaRd65ZPydpp4LeugcSYYHET8HwiB0/cj337V3nYIaxlRoOUb1D/ dHYCh9jkCBtbEq/g7ortXxdyOJYy98hkCon3pUdVFUW0Bj5YA3Jxr1Bfjgbw1uFRZYMF 17euSOFUDNOkwD7uOQSzKd1tRyqRpr11EjJjzKcYtLPS3j84eC8AvvPBgXfEpIh2pJVK 6s3vupY5/Hs6fMo+k95fmKTY7yH4Fiat720g5YnuTmUtOEChryTarsJnsxDhq7zgghh5 Q0nifT7OnnO3v5b/brlZZYjc3DUJp4eLWImrIyhQ2/bhMt9TkX6XJhpgYx5cqaK1wz6N ityw== Content-Transfer-Encoding: base64 MIME-Version: 1.0 To: "dhcp-public@isc.org" Delivered-To: dhcp-public@bugs.isc.org Content-Language: en-US content-type: text/plain; charset="utf-8" X-RT-Interface: Email X-Original-To: dhcp-public@bugs.isc.org X-MS-Exchange-Organization-Recordreviewcfmtype: 0 Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.pao1.isc.org", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 1CB1DD78A16 for ; Mon, 14 Jan 2019 14:18:17 +0000 (UTC) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 6E9F13AB003 for ; Mon, 14 Jan 2019 14:18:13 +0000 (UTC) Received: by mail-wr1-x433.google.com with SMTP id z5so23015194wrt.11 for ; Mon, 14 Jan 2019 06:18:13 -0800 (PST) Received: from VI1PR1001MB1453.EURPRD10.PROD.OUTLOOK.COM ([40.101.68.77]) by smtp.gmail.com with ESMTPSA id o5sm50920771wmg.25.2019.01.14.06.18.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Jan 2019 06:18:10 -0800 (PST) X-RT-Incoming-Encryption: Not encrypted Return-Path: X-Received: by 2002:adf:94e4:: with SMTP id 91mr25711082wrr.322.1547475491590; Mon, 14 Jan 2019 06:18:11 -0800 (PST) From: "Radek Zajíc" X-MS-Exchange-Organization-SCL: -1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mx.pao1.isc.org References: <320af239b12d3dc44e23399129493513@www.isc.org> Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zajic-v-pytli-cz.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=jE4gyV3DODJVSb5TwvL6j5PLhifX1W5192X5sT0uE6A=; b=yBWKyen8hb4p2Zi6EtS3V7zvpbdmOYsQFzJ1sIuVgdp3YnDBlZUVqlQoK5S9DcZSg8 axvrYAwOgWC69VhZ7hjjkHDs0tO9PJ16xQ2JFPmTJhIZ/ENcUdqSn7vBlBeaSVmvFuoh Kk7JFabCy6DZQCOWm57ZPw4fu+1wT+XCpzM7PI63gi9/3bPy0WDHTXG496rd4wpI7gxb 6BDv9uex9Kve6G1aunBsaD5mSe9t3CKhBqAVwPq210/Qw04WjmCLUaY8pP4vWyY2I2ow Ovy9vs7pk9Psz3nQmfcICNiilHTZM5MHpNDuaHQ104zID6IFi8BXGvMKD/jpSvXcxUmY unYQ== Thread-Topic: [ISC-Bugs #48804] any, with libraries containing fix for RT #46709 - isc-dhcp crashes when running in DHCPv6 mode From radek@zajic.v.pytli.cz Mon Jan 14 14:18:17 2019 X-MS-Has-Attach: RT-Message-ID: Content-Length: 2054 Hi Thomas, Thank you for your prompt response. Unfortunately the attachment seems to be missing in this e-mail message. Would you mind rechecking if it has been sent or not? (I do not have access to the bugreport on https://bugs.isc.org/Public/Ticket/Display.html?id=48804 so cannot check if the file is there.) As for Kea, I have already tried (and somehow succeeded) in migrating of my configuration to Kea, however the JSON config file is a horrible idea. Besides the JSON config file, Kea does not have the powerful conditional logic capabilities of ISC DHCP, which is something I need to perform network boot with different config files/filename paths (legacy boot, UEFI TFTP boot, UEFI HTTP boot, Raspberry Pi network boot, via IPv4 and IPv6). I have somehow managed to hack most of it in, but it's not something I'd call clean and DRY. I definitely support the thinking behind Kea, but am afraid the upgrade path will not be straightforward for many ISC DHCP users. Thank you for your support. Kind regards, Radek Zajic Dne 14.01.19 15:09, Thomas Markwalder via RT napsal(a): Hello Radek: This issue was corrected in ISC DHCP 4.4.1 under rt46719. ISC DHCP 4.3.* is EOL at this point. I have attached a patch that should work 4.3.6 but keep in mind that it does not represent an official, tested patch. Our official response for your issue is to suggest you upgrade 4.4.1. Upgrading from 4.3.5 to 4.4.1 should be painless, they are architecturally compatible. Speaking of EOL, 4.4.1 is the last feature release of ISC DHCP as we are putting our focus on new DHCP product: https://www.isc.org/kea While we do plan on doing some maintenance releases for ISC DHCP, the next one (4.4.2) has not yet been scheduled. It might be a good time for you to look into migrating to Kea. Thank you for your inquiry, I help this addresses the issue for you. Sincerely, Thomas Markwalder ISC Software Engineering