UPnP/IPv6 support in home routers?

Fri Dec 15 01:51:59 UTC 2017

On Mon, 11 Dec 2017 12:10:39 -0300, Fernando Gont said:

> On 12/11/2017 10:44 AM, valdis.kletnieks at vt.edu wrote:

> > Unfortunately, if you want your Xbox or Playstation to be able
> > to work, you need to be using IGDv1.
>
> Could you elaborate on why IGDv1 is needed? (why things break with IGDv2)

Because my Playstation 3 and Playstation 4 both speak IDGv1, and when they
talk to an IGDv2-capable miniupnpd on Openwrt/Lede, it Just Doesn't Work, and
will continue to do so until Sony ships a software update to make it work with both
v1 and v2.

It's possible that miniupnp simply botched backward combatability - I didn't
debug further. Googling for 'miniupnp idgv2' seems to indicate that nobody else
has debugged/fixed the issue either.

https://forum.lede-project.org/t/miniupnp-with-igd2-not-compatible-with-consoles/2016

(More recent Lede builds changed back to IDGv1 by default for this exact reason).

Interesting fact:  My PS/4 will dhcpv6 and assign itself an address and answers
ping6 even from outside my home network (so it has a default route), but
doesn't seem to do anything else with IPv6 (for instance, the assigned address
isn't listed under 'view connection status', nor does nmap find any open ports,
though it hits 2 open http ports on IPv4).

> I see your point. Now, how are apps that currently rely on punching
> holes into the NAT or filtering device to work in a v6-only scenario?

I wonder if doing IDGv2 on IPv6 and IDGv1 on IPV4 is a viable solution....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20171214/f55eb5ec/attachment.sig>