From owner-freebsd-questions@freebsd.org Wed Jun 26 18:57:32 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7287315CF850 for ; Wed, 26 Jun 2019 18:57:32 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [208.111.40.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA49C83768 for ; Wed, 26 Jun 2019 18:57:31 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (catnip [73.240.250.185]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id 19E3F38D0C; Wed, 26 Jun 2019 11:57:30 -0700 (PDT) Received: from [IPv6:2601:1c2:1402:1770:70d3:d328:7143:b8ad] (unknown [IPv6:2601:1c2:1402:1770:70d3:d328:7143:b8ad]) by chombo.houseloki.net (Postfix) with ESMTPSA id 8822E3166; Wed, 26 Jun 2019 11:57:29 -0700 (PDT) Subject: Re: IPv6-only network--is NAT64+DNS64 really this easy now? To: FreeBSD Mailing List , Lowell Gilbert References: <5e24739b-bbd0-d94a-5b0e-53fdeba81245@bluerosetech.com> <19784363-6543-ccc1-b13f-5f1a67dc10d1@bluerosetech.com> <44v9wtr8o9.fsf@be-well.ilk.org> From: Mel Pilgrim Message-ID: Date: Wed, 26 Jun 2019 11:57:27 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <44v9wtr8o9.fsf@be-well.ilk.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: DA49C83768 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 208.111.40.118 as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-3.02 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[bluerosetech.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: echo.brtsvcs.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.93)[-0.928,0]; IP_SCORE(-0.79)[asn: 36236(-3.88), country: US(-0.06)]; RECEIVED_SPAMHAUS_PBL(0.00)[185.250.240.73.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:36236, ipnet:208.111.40.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 18:57:32 -0000 On 2019-06-25 8:23, Lowell Gilbert wrote: > Mel Pilgrim writes: >> Yes, that is why I wrote "Waving a hand at bug-hunting and >> lamentations over the inertia of embedded systems designers". > > I'm an embedded system designer, and the system I develop works fine under > IPv6. We say we don't support it, because we don't specifically test it, > but a lot of the time the applications are1 actually running over IPv6 > without anybody noticing. The Windows GUI pieces can't configure IPv6 > addresses, but we really prefer running with link-local anyway. That's the problem, though. If the vendor doesn't support or test it, I can't rely on it in production. That's a big part of what I mean by lamenting embedded systems designers. Until we have IPv6 parity, all those printers and multifunction devices sit on their own IPv4-only VLAN, accessible only through print servers so that I don't have to worry about things like unsecured SNMP over IPv6 because the vendor didn't bother making their ACLs dual-stack or only added the "read-only" config bit for IPv4, leaving the IPv6 SNMP open to unauthorized writing (actual observed behaviour with a major printer manufacturer).