Subj : Connectivity Validation
To   : Scott Street
From : Michiel van der Vlist
Date : Wed Oct 06 2021 12:52:44

Hello Scott,

On Monday October 04 2021 23:54, you wrote to Wilfred van Velzen:

 SS> After much back and forth with Comcast/Xfinity;  I have found that I
 SS> needed to drop IPv6 support for incoming connections.  A shame really,
 SS> because Comcast's gateways do not support UPNP for IPv6.

The general consensus among the IPv6 Gurus is that UPNP should not be used for IPv6.

 SS> Oh, and why UPNP?  Because the router "calls home" to Comcast
 SS> periodically (often?) and gets new configuration information and it
 SS> seems that in my region, the port forwards are not saved.

Port forwarding is an IPv4 thing. In IPv6 one just creates a hole in the firewall to let the port go through.

 SS> So I discovered a simple workaround for there junk software;  now two
 SS> things happen, first when my DHCP client detects a network change it
 SS> runs my DNS update script and that script now includes 'upnpc'
 SS> commands to refresh the port mappings.  The script also runs every
 SS> five hours just in case the gateway's IP address changed without
 SS> changes on the inside.

I can see why that would not work for IPv6.

 SS> I wish I thought of UPNP a week or so ago;  would have saved me many
 SS> hours of hold time and fustration.

You may want to ask Andrew Leary (1:320/219) for help. He has IPv6 up and running on a Comcast connection. I don't know how he does it, but he obviously has found a way.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: ZC1 certified techno-dick (2:280/5555)

.