06-03-2023 08:42 AM
Hi folks.
Having issue with Nest WiFi router upnp. It does work only for IPv4.
upnpc-shared -6 -L
keeps saying that no valid IGD upnp device found on the network. Adding the interface name
upnpc-shared -6 -L -m "Wi-Fi 1"
does not help.
IPv4 is okay'ish but it does not allow to open IPv6 pinhole (I get 401) due to security constraints - request to open a port should be coming from the same IP which it is opening for. Static port forwarding is not an option as IPv6 addresses will change over the time.
Current firmware version on my Nest WiFi router is v. 14150.376.32.
Would be great to see this working so that we are not locked up behind public and dynamic IPv6 addresses.
Another thing I noticed is that upnp reports that firewall is Off on the router.
C:\>"%programfiles(x86)%\upnpc\upnpc-shared" -S
upnpc : miniupnpc library test client, version 2.1.
(c) 2005-2018 Thomas Bernard.
Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://router-ipv4-here:5000/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
Found valid IGD : http://router-ipv4-here:5000/ctl/IPConn
Local LAN ip address : router-ipv4-here
FirewallEnabled: 0 & Inbound Pinhole Allowed: 0
GetFirewallStatus:
Firewall Enabled: No
Inbound Pinhole Allowed: No
Bytes: Sent: 4294967295 Recv: 4294967295
Packets: Sent: 422302834 Recv: 359886953
which is wrong as I am able to connect to the IPv6 endpoints only if I manually add specific port in Port Management.
Please advise if I am wrong.
07-28-2023 11:29 PM
Hello vayvanne,
Thanks for posting here in the Community.
We appreciate you bringing this to our attention and we'll take this as feedback. If you have anything else that you want to file regarding this concern, feel free to share your feedback using the Google Home app by using this link for more steps.
Let us know if you have additional questions or concerns; otherwise, we'll close the thread after 24 hours.
Cheers,
Lovely