New post on HughesNet's native IPv6 infrastructure. Very lengthy how-to on setting up a CentOS/RHEL router to service IPv6 clients. The post is rough around the edges but I'll be updating it over the next few days.
Hmm, maybe I should change my avatar back to Mr. Finch...!
If your wife's workplace is IPv6 enabled, it *should* work. You'd probably need to register with a dynamic DNS service (foo, that's what I forgot to mention) for when the prefix changes, and run a little daemon like ddclient to update your IPv6 address on occasion.
I just did a few file transfers via SCP from my desktop to a VPS I have. What a weird feeling--directly accessing a computer with no port forwarding.
IPv6 is supposed to get rid of the end-to-end breakage nonsense of NAT, so these are PUBLIC addresses (although dynamic). NAT is such a hack...
Even with scp, I saturated my uplink at 1MBit/s. Not sure what I hit when transferring a file back to the desktop because it transferred too fast.
I think it's safe to say that performance on a VPN would be reasonable, if not the full 10MBit/s download. (Remember, pulling a file *from* your home computer is using your lower-speed uplink, not your downlink.)
Keep in mind that you're gonna have to reconsider how you think of firewalling, security, etc. There are no private addresses on IPv6. (Well, there are, but, there aren't.) Each of your machines should have an IPv6 firewall on them and your border router should have one too.
I am half tempted to beg you to figure out what I can NOT get figured out... IPv6 with PFSense 2.1RC0 Tue Jul 23 build still fails with IPv6 on my LAN, and WAN it feels like, especially when I have SQUID running locally.
When enabled it wants to assign FE: addressing which is a non-routable address from what I can find. The LAN is set to track WAN, but refuses to assign the proper addresses. Changing it at all on my box, will result in the WAN option disappearing for good, till the OS is re-installed.
Charles, Yeah PFSense is pretty finicky. I have successfully used RC0 with servers at co-los over fiber but still have issues with certain web services. I suspect use over Hughes will require quite a fair bit of debugging, is edge case, and will probably not work for a while.
BTW, FEC-FEF are site-local and will forward where as FE8-FEB are link-local and will not.
Pretty sure it was wanting to assign FE80 or similar on the LAN side, really wish the developers would put more time into fixing IPv6 related issues instead of making things like the RRD graphs pretty...