Hi Erin, I finally got a chance to get back .....
Health wise, thanks for your concern and input.
I agree we are just surrounded with .... toxic stuff, almost impossible to avoid.
In my case the "cat is out of the bag", the damage is done and the only course of action, and what is anticipated at this time is the removal of a section of colon.
If everything says that things have remained "local" then that will be the extent of it.
I'm hopeful that that remains the case.
Now, on to other things ......
I have no idea why anyone would have you go through so many routers.
It "doesn't work that way"
Bill asked "why do you want a router with just one computer"?
I always recommend that a user have a router, even if for only one computer.
That router has a "always on" hardware firewall .... not a real good one but it serves one very important function.
I will reject all connections from the "outside" except in response to requested actions from the "inside"
When you start up your computer its "hardware" will be initialized and have "connectivity" before all of your protective software such as A/V and software firewall are loaded and active.
That very "stupid" hardware firewall will protect your system from intrusion during this time.
I like Routers.
Almost any router will do the job.
Some routers may provide better wireless coverage if your house is shaped like "this" a different model may work better if your house is shaped like "that".
Some have more "Bells & Whistles" but on the whole almost any router will serve.
There are however some older types of routers that may "choke" a little when compared to the newest standards but even they will work if a user is careful of some settings.
Routers, depending on their "generation" fall into .... "speed grades" or standards.
These are going to be like "B", "G", "N" or "AC".
The current "everyday" standard is "N" and will be backward compatible with devices that use "G" or "B".
The thing is, the entire network will slow down to the "standard" of the slowest device connected to the network.
In addition to that, all routers have a QoS function ... that feature will be known by different names depending on the brand of router but its purpose is the same ... to "equalize" the "quality" of a connection that is ..... important word here ..... is SHARED.
A router is a "connection multiplier" and routers will attempt to "level off" performance to certain connection types ... VPN, FTP and so on.
This type of behavior works ..... if you have a GREAT BIG INTERNET PIPE ... something you don't have with a Hughes connection.
That setting as well as some possible IP address conflicts can kill the speed and performance of a "fragile" Hughes connection.
In addition, a router allows "sharing" and the more devices that are connected to that "fragile" connection the slower each becomes.
This is why Hughes asks that speed tests be performed with a single computer directly connected to the modem.
Being connected directly allows a system baseline performance level to be developed.
As to the Hughes connection itself, it is subject to "sharing" beamwide on a users connection , there are times where the weather is great a users location but is just terrible at the users Gateway location.
Example, I am located in west Michigan but my Gateway is in Flagstaff AZ. Weather can be great in one area but totally different in another.
Then we have the concept of "peak time" ... this occurs when more users within a beam/Gateway are all using the service at the same time and the entire system grinds to a halt.
Yup, you can read that as a localized "oversold".
Even at that, not all is lost ...
Once a "overload" is ..... proved by a series of speed tests that show congestion the issue can be escalated to Engineering and while they move a snalls pace they can spread "pixie dust" on the servers or whatever they do and the issue .... eventually .. gets resolved.
But it all starts by those series of speed tests performed while connected directly.
With a router in the mix there is simply too great a likelihood of concurrent connections, IP address conflicts and having things like remote access, WPS and QoS having been enabled in the router to develop an accurate baseline that would cause them to add servers or shift your server ... they won't do it on a "maybe".
You had asked how to disable the "radio" on your router ....
Post the Brand, Model and version of your router and as soon as time allows I'll download the manual and post a screenshot.
The Hughes Modem has "internal" pages known as the SCC, found at 192.168.0.1
Your Router also has "internal" pages and this is where we will find the :"switch" to enable/disable the radio.
You had mentioned getting a 13.1.1 LAN Disconnect error .....
A router can be set up in one of two "modes" ....
The usual is "DHCP" mode which is to say the router handles the task of handing out IP addressing to connected devices.
A router can also be setup in "switch" mode. This is when the Modem handles DHCP duties .... I thought much of the Hughes Modem as a router.
That 13.1.1 error is when the Hughes modem generates a new IP address and a new "lease" is negotiated.
Some routers and some NIC cards are a little slow on the "uptake"
Enough for now, post the routers Brand, model and version and I'll download the manual and find the "radio" switch.
If you have a router connected to the modem and you power off the router then it will cause a 13.1.1 error condition because there is nothing "live" connected to the modem.
As to DNS errors ....
DNS stands for Domain Name Server ....
When you enter an address into your browser you enter something like www.cnn.com
You computer really doesn't "understand" that addressing format, it has to be changed to a numerical IP address such as 184.108.40.206
To find that numerical address your data request is sent to a DNS database and the info is returned your request for data is then processed and the page content is loaded into your browser.
Hughes maintains its own DNS database and ,,,, it can get a little troublesome from time to time.
The good news is that you don't HAVE to use the Hughes DNS service ... there are many others ... I use Google's DNS service and seldom see any DNS errors.
"I just powered router off/on. went to system control center, page was FROZE. I exited out, tried to reload and I got "can't reach this page"message. Now I got page to load, there is another 13.1.1 transition added, but no new X's in LAN."
You have to remember the "communication leases" that have to exist.
Computer >>>>>> Router >>>>>> Modem
If you have a router connected and wish to see the modems SSC internal pages your computer has to go "through" the router to get to the Modem SCC.
Understand this the Hughes Modem has internal "hardware" that "sees" the next piece of "hardware" connected to it ... in this case the Router then your computer has internal "hardware" that has communicate a "communication lease" between itself and the Router.
Modem "talks" to Router, Router "talks" to computer.
If you power off one of the devices .... it will "break" the "communication lease" between those devices.
The leases will be reestablished automatically but is can take time ... some routers and NIC cards are slow on the "uptake" so certain modem/router/computer combinations MAY show more of these transient errors than other Modem/Router?Computer combinations.
As to red "x"'s , the duration of the event will may not make a red "X" but it will show the 13.1.1 code condition.
Nothing really to worry about.
Remember, if a communication lease is "broken" by a power-off or the lease just "expired" due to time, then there is going to be a "hiccup" while a new lease is put into effect all along the "network communication line" consisting of .......
Modem makes a communication lease with Router, Router makes ... communication leases with all connected devices.