[Networking] IPv6 Routing Issues on HT1000
Has anyone tried IPv6 on the GEN4 HT1000? I'm having issues reaching certain sites that online traceroute/ping tools can reach, including a trace directly from the Level 3 VLAN where my issues begin. I have to believe that it's something in the source packets being filtered, but I haven't gotten anywhere with Hughes tech support. They did some "troubleshooting" and verified that yes, I am unable to contact these sites:
My traces never leave the Salt Lake Level 3 POP for freebsd.org (which is the first L3 hop), and get all the way to the edge of the VLAN in Munich for fedoraproject.org before timing out.
I've been able to reach Google, Facebook and several others on IPv6 so I've eliminated local configuration as an issue. This occurs on both Windows and Linux.
diablo1892Plough, sew, water, harvest. Repeat.Reviews:
said by dartonw:I am able to reach both of these sites, they load up less than 1 second.
They did some "troubleshooting" and verified that yes, I am unable to contact these sites:
Check my specs \/ \/ \/ \/ (my signature)
HT1000/ BeamID 32/ Power Max plan/ 4 pcs on a D-Link wired switch/ wireless D-Link router with password
Support only the gaming company's that matter the most, pay for something that actually is worth buying
or has a good reason for how much it's worth.
grohgregDunno. Ask The Chief
Dawson Springs, KY
|reply to dartonw |
Don't know if this will help in your instance, but I had selective address issues in the short period I had the HT1000. I suspected a DHCP conflict, and changed the range in my Belkin to the 192.168.2.100 -192.168.2.200 slot. No further address issues.
HN7000S - 98cm Prodelin/2w "pure" Osiris - ProPlus - G16/1001H - NOC:GTN - NAT 22.214.171.124 - Gateway 126.96.36.199 - DNS 188.8.131.52 and 184.108.40.206 - Firefox 15/MSIE9 - AV/Firewalled by NIS2012
|reply to dartonw |
You will experience IPv6 issue with these two IPv6 subnets. This 2001:1900::/32 IPv6 subnet block has been assigned from ARIN to Level3, but Hurricane Circuit and Yahoo are inappropriately advertising out to the internet.
2001:1900:2254::/48 Currently advertised by Yahoo
2001:1900:2262::/48 Currently advertised by Hurricane Electric
To troubleshoot whether the websites is using this IPv6 address , you can use nslookup q=aaaa . Below is an example:
nslookup -q=aaaa www.freebsd.org
www.freebsd.org canonical name = wfe0.ysv.freebsd.org.
wfe0.ysv.freebsd.org has AAAA address 2001:1900:2254:206a::50:0
On a related but separate issue, some device between Hughes and the fedoraproject.org site is rejecting the Hughes IPv6 block.
Neither of these issues are in Hughes' control, but Hughes is working with both entities to help them resolve the issue.
The Fedora Project issue has been corrected by the upstream provider, so HughesNet users can now reach that site via IPv6.
Indeed, I noticed it the day it was fixed but had forgotten about this post.
Thanks for moving the Internet forward with IPv6, HughesNet.