> Try this, open a web browser and go to Lowes.com and see what it picks as a "local
That doesn't work. It is apparently getting information that is more localized to myself. If it was picking a Hugesnet server, the location would be more generalized.
For example, for wal-mart.com, it's picking our local store. There is no way Hughesnet has a server there. We're barely above using beavers to pound out messages, let alone huge tech companies setting up shop in the area.
I wonder if a traceroute will help....
Okay, this was helpful.
So now to the nuts and bolts.
I'm on Beam 43. if I want to, say, hit Google, where is my connection going?
I say www.google.com, my computer beams that request to the satellite. The satellite beams the request down to <x>, and from there it goes to google.com, which then sends the relevant information to <x>, back up to the satellite, and back down to my computer.
How do I find out where <x> is? Are there multiple <x>s? Does <x> move around? Does everything always route through MD regardless of where you are and where <x> is?
Hmm...Hughes certainly does make it difficult to figure out.
So the question remains: Does that IPGW ever change? Or is it static?
And where does it go from there? Is there one point in the line that is always stable?