It is not static at all, or at least hasn't been the past few days. Sometimes it lasts a couple days, other times a few hours and they assign a new prefix. Really annoying and not the way IPv6 is supposed to work. I'm still sorting out some sort of dynamic DNS solution to do the updates automatically.
I have a Pingdom monitor setup on it, will let you know if it changes... but note this is just the ipv6 of the HW modem, which is a totally seperate prefix then what I get from dhcpv6 (which hits the sonic, sonic sends reply to HW router and then dies before routing back to origin)
Ok, some more testing today both with and without the Sonicwall. From the sonicwall packet captures you can clearly see the packets accepted from HW modem --> Sonic responds but gets a ipv6 neighborhood error (i.e. doesnt know how to route the response packets... )
So then I connected my macbook directly to the ethernet port on the HW, disabled all WiFi and IPv4 in total on my macbok, and guess what?! The Macbook also couldnt resolve anything from the HW (not even the HW itself via ipv6). So it looks like the problem is within the HW itself, either not supporting a full ipv6 stack, or the ipv6 stack is misconfigured, or the ipv6 stack is configured for inbound only. You can't even hit googles ipv6 DNS.
Can you post all your HT2000W configuration settings? I am able to ping, traceroute, etc. both inbound and outbound on mine.
FWIW, I'm on the San Diego IP gateway.
Which settings? Just IPv6 pages?
Are you using MacOS/Windows/Linux ip stack? BTW, i'm on East Coast, no idea which gateway.
Sending you a PM with my contact info, maybe easier that way and we can post solution to board if we find one.
All posters, I am very interested in the outcome and solution to the issues described above. Ultimately what I'm trying to do is connect a Hikvision security camera DVR so I can monitor the cameras remotely via cell phone. I'm new to HughesNet (in fact business account being installed today at our church in Texas), but eager to learn.
Here's how to get it to work:
Go to your HT2000W setup page and, under advanced settings, in the firewall section:
-Enable the firewall
-Disable both intrusion detection checkboxes
-In IPv6 rules, add a rule with "::" as the client address (no quotes), TCP, start port 1, end port 1.
-REBOOT THE ROUTER USING THE WEB UI OPTION, then don't change any more firewall settings
Your Hikvision DVR (assuming it's moderately recent) will pick up an IPv6 address and will be accessible from the Internet if your device has IPv6 connectivity. You can see what the address of your DVR is by going to the network settings page in the web interface. It's also worth mentioning that any other IPv6 capable devices on your network will also receive publicly accessible Internet addresses, so be sure they have proper local firewalling, etc.
I am noticing my IPv6 previx change quite frequently, which is somewhat useless for remote access. But YMMV on that.
"I am noticing my IPv6 previx change quite frequently, which is somewhat useless for remote access. But YMMV on that."
Sounds like they need to lock prefix's on the system once they are established, give the user the option to lock or release it. Not a IPv6 user yet but seems they should start implementing more control on the user/client side. All I know is IPv6 was supposed to allow much more control and direct Internet addressing access for the average customer.
Sadly with how these units work, I don't think the gateways will tolerate it very well...