@C0RR0SIVE I am a residential subscriber. I personally was never promised static IPv6 addresses (or any IPv6 at all, for that matter) during the sales process, but it appears that others have been. Regardless, every other ISP that I'm aware of in the US provides static IPv6 prefixes to its fixed customers. This is a central design feature of IPv6, evidenced by the lack of wide support for IPv6 dynamic DNS and Hughesnet's own IPv6 firewall design in its HT2000W router. The firewall rules must be built with the end device's IPv6 address, so if those addresses are dynamic, the user would need to reconfigure their firewall rules every few days.
@C0RR0SIVE I'm also a residential subscriber, but offered to become a business subscriber if it would make a difference (After our discovery that these ipv6 delegates arent static). I was toldf it works the same way for business subscribers, and the only way to have a static ipv4 or ipv6 address is to be a legacy business customer.
Just a quick update for anyone looking for answers to this in the future.
Until HughesNet addresses thier very strange implementation of ipv6, I have reverted to using a raspberry pi plugged directly into the hughesnet modem to perform DDNS via DYNv6. Anything you want to access remotely (besides the pi) will need to be configured to use stateless ipv6 (making your mac address public). You then would need to alter the DYNv6 update script on the pi (they supply a nice one on thier website) to glue together the /51 assigned by hughes to the stateless address on your device... or you can just use the pi to route/redirect ports instead. I believe @pswired has done something similar using his own script. If anyone needs step by step for the raspberry pi let me know.
Note that this effectively puts the pi open to the world, and you should take measures to secure it against such.
Haven't heard anything back. I've pinged them for any news to share.
Did my post answer your question? Accept as Solution to help others find it faster.--------------------------------->
Where do we stand on a firmware update for the HT2000W to enable IPv6 inbound traffic and ultimately customers' ability to access LANs via public IP address without all the workarounds noted in this thread? Looks like the last response on this thread was on 11/20/2017...This is a very important issue that needs to be resolved for the rapidly expanding availability of the IOT's -- especially security systems that do NOT work through the vendor's server.
Ditto, any update from the "Engineers" regarding this issue?
I am new to this forum, but also have 3 "systems" inside a LAN that need to be remotely accessed by IP (IPv6 I guess, as IPv4 seems impossible via HT2000W). Anyway, these 3 devices include: pool-system controller, security camera NVR, and security system. I'm not sure all of these devices have the ability to change/set their IPv6 address, so I'm hoping that the HT2000W will be able to NAT from some IPv6 (or DDNS IPv6) address to a LAN IPv4 with an associated Port #.
From another forum:
"There are scenarios where a person may have already deployed a private IPv6 network using ULA space (unique local address; it's equivalent to the RFC1918 private IP space (192.168.x.x etc)). If they didn't want to re-IP their network, they could use NAPT (network address/port translation) to forward requests from the ISP supplied GUA (globally unique address aka public IP) to the ULA network and vice versa."
No updates, and I imagine that the whole Gen5 system grinding to a halt due to oversubscription is probably a big enough distraction that we won't see much progress on this anytime soon.
I will note that the frequency of my Hughes-assigned IPv6 prefix changing has gone way down since this thread started. It stayed constant for most of the month of December, then changed during the outage that took down everyone on Echostar 19 on New Years Day.