About MarkJFine

Web acceleration only works for non-secure http links. Since the majority of the internet is now using secure links (https) HughesNet disabled Web Acceleration in order to test it's impact on the overall system. Older modems (e.g., HT1100) highlights this as an error, however it is currently a normally operating situation. In other words, just ignore it. ... View more

I offered to maintain it for free... ... View more

There are several sites that are routinely slow due to bad routes from HughesNet's provider (as shown through traceroutes). Steam is one of them, along with anything related to Microsoft, especially github. It's been really bad the past month or so. ... View more

Don't understand what you mean by "near duplex" since it's certainly not simplex, which implies a single click-to-talk channel like a walkie-talkie. You're just significantly lagged.   Understand that many real-time streaming and conferencing servers don't know how to deal with irregular packet delays. Often during congestion, an acknowledgement packet can be so late as to be ignored, which is why you can see a lot of what appears to be buffering. Many times it's not really buffering - the server is resending the whole requested frame because it never saw the late ack and just assumed a nack in the first place.   Streaming and conferencing is a very ping-intensive activity, not like simple web site browsing and file downloading. TV stations struggle with the delay in live satellite interviews even when they basically have an entire transponder's bandwidth to themselves. Now imagine sharing a spot beam with potentially hundereds of thousands of others that are all trying to stream and conference at the same time, and a groundstation that handles around 8 beams to gateway to the internet. It's complete bedlam. ... View more

That's a half-second per ping, depending upon potential needs to resend (which would of course multiply it) as well as system congestion and the ability for servers on the internet to be able to handle that half-second. Doubtful it's a flaw in your modem as it's likely some combination of the latter two. ... View more

When conisdering latency, did you realize that in satellite communications, the radio signal has to traverse a total of around 95k miles for a round-trip handshake? Edit: **bleep** keyboard... skipped the 'k'. ... View more

@Danny89 wrote: As an educational moment, im curious, why are internet speeds now more measured by bits per second as opposed to bytes? It certainly makes things look more impressive, but as someone who was in the dial up days, everything ive ever downloaded shows me data in bytes, and of course all storage is still measured in bytes. Feels like some Metric vs Imperial stuff 😛 My take: No one can agree what a byte is, but a bit is undeniable. Seriously.   First, there's the issue of how many bits make a byte: Is it the actual data word? Does it include parity and control bits? Does it include repetitive protocols required for forward error correction? It's not pretty, and hella confusing.   Second, there's the issue of the actual measurement, since no one can agree if 1k = 1,000 or 1,024, but that's a whole 'nother kettle o' wax. ... View more

It probably popped you onto a different route. I always reboot the modem to try and get a different route if things get squirrelly. Plus, if the DNS cache gets corrupted, rebooting clears it out. Not a bad strategy to do this once in a while. ... View more

I'm not able to turn it off, which is really bad for some games. ... View more

Think of the last four digits as something akin to the router bank and port that you're connecting through at the ground station. That's how I look at it. ... View more

The page I directed the OP to was to the modem's built-in interface, which was being reported as 'unreachable'. That means the OP doesn't even have a proper connection to the modem.   A certificate error something completely different from the OP's issue and can mean several things. Addressing it here would over-complicate the issue that the OP is having. ... View more

You could try disabling Web Acceleration: 1. Using a computer connected to the modem via ethernet or wifi, open this page. 2. Under Advanced Menu on the left, click on Web Acceleration, then Control. 3. On the right, click the green Web Acceleration Enabled button. 4. It will then turn yellow and change to Web Acceleration Disabled. 5. You can optionally click the Reset MBX button and retry enabling Web Acceleration, but I'm not sure what that adds.   If that doesn't work, you could try rebooting your modem to make sure its' internal DNS cache wasn't corrupt to begin with. You reboot it by unplugging the power cable from the wall socket, waiting 60 seconds, then plugging it back in. ... View more