Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] upnp and PCP for ipv6
Date: Mon, 24 Mar 2014 09:54:15 -0700	[thread overview]
Message-ID: <CAA93jw5jA+GmudH5orGfVSUmLx2847KFgtxSiSmunW8StnPoVg@mail.gmail.com> (raw)

Does anyone care/have a use for at the moment - pcp for ipv6?


---------- Forwarded message ----------
From: miniupnp <miniupnp@free.fr>
Date: Mon, Mar 24, 2014 at 4:15 AM
Subject: Re: *Wrt PCP support?
To: Markus Stenberg <markus.stenberg@iki.fi>
Cc: Dave Taht <dave.taht@gmail.com>, Steven Barth <cyrus@openwrt.org>


Hello,

I have made the necessary changes so miniupnpd listen for IPv6 packets
sent to PCP port (5351)
https://github.com/miniupnp/miniupnp/commit/ad88cc0819321eb2841958f846138ac3a225152f

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 écrit :
> On 7.3.2014, at 11.45, miniupnp <miniupnp@free.fr> wrote:
>
>> Le 07/03/2014 12:19, Markus Stenberg a écrit :
>>
>>> On 7.3.2014, at 11.00, miniupnp <miniupnp@free.fr> 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 guessed 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



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

             reply	other threads:[~2014-03-24 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:54 Dave Taht [this message]
2014-03-24 17:37 ` Toke Høiland-Jørgensen
2014-03-24 19:00   ` Paul Handly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw5jA+GmudH5orGfVSUmLx2847KFgtxSiSmunW8StnPoVg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox