From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 3BC9E21F1EC for ; Mon, 24 Mar 2014 09:54:18 -0700 (PDT) Received: by mail-wg0-f45.google.com with SMTP id l18so3706305wgh.16 for ; Mon, 24 Mar 2014 09:54:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=bhK8OOaXn6Rnl4MXeglfMtYTEDe4bmK1C5R7ega6BcQ=; b=0Kz4wT+5tCZ5CN6lf0v8mNjCj63ZOJgDkr8lh21gip0RrkC0DcA3WQaU3O7eAMnuuH rRwQZgiXZng1gXsWk2LtEEzxfhd41ocpqL9euVzftTRcDjXfJPMuzkhDLmcQLfSsIYN1 mE6gFCezKl44cwKsJLv8pZ4ETc1WGC0IBHcBAn4nHjCK+mtvE9KKnHxEOnjphVHYChvN Z20iRtN2LFrrMMrkCd5enXRQlTHEUCIPo7GogMAtfX3b4CL14DDXgyttKiNcgpmtres0 aDFFG5JHBr4Gv91AERoM0Lks1pEykuoCdt6e5h0T+rKZT7UjX9Agz8apIUDVP9lCLgf8 /aNA== MIME-Version: 1.0 X-Received: by 10.180.36.226 with SMTP id t2mr1629377wij.37.1395680056026; Mon, 24 Mar 2014 09:54:16 -0700 (PDT) Received: by 10.216.8.1 with HTTP; Mon, 24 Mar 2014 09:54:15 -0700 (PDT) Date: Mon, 24 Mar 2014 09:54:15 -0700 Message-ID: From: Dave Taht To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] upnp and PCP for ipv6 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2014 16:54:18 -0000 Does anyone care/have a use for at the moment - pcp for ipv6? ---------- Forwarded message ---------- From: miniupnp Date: Mon, Mar 24, 2014 at 4:15 AM Subject: Re: *Wrt PCP support? To: Markus Stenberg Cc: Dave Taht , Steven Barth Hello, I have made the necessary changes so miniupnpd listen for IPv6 packets sent to PCP port (5351) https://github.com/miniupnp/miniupnp/commit/ad88cc0819321eb2841958f846138ac= 3a225152f There is still work to enable the "IPv6 firewall" and NAT64 PCP scenarios. The PCP code was assuming the client want NAT44. Regards, Thomas Le 07/03/2014 12:52, Markus Stenberg a =E9crit : > On 7.3.2014, at 11.45, miniupnp wrote: > >> Le 07/03/2014 12:19, Markus Stenberg a =E9crit : >> >>> On 7.3.2014, at 11.00, miniupnp wrote: >>> >>> >>>> Of course it is IPv4 oriented, nobody needs port mapping for IPv6... >>>> >>>> >>> Well, given default-deny IPv6 firewall, I'd agree to disagree with you.= (It can be used to make holes in firewall on IPv6 side.) >>> >>> >> Don't forget to configure miniupnpd for IPv6 and PCP support : >> ./genconfig.sh --ipv6 --pcp-peer >> --igd2 : some clients have compatibility issues with IGDv2 (XBox) but it >> adds the "IPv6 pinhole" service to make hole in firewall. >> > Sounds cool, I'll play with it, thanks. > > Peter Tatrai told me the IPv6 pinhole stuff isn't done for PCP, but he gu= essed it wouldn't be very hard to do as you have it already for IGDv2. (We = can take a look at that if it helps, we're paid to care about IPv6.) > > Cheers, > > -Markus --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html