but they lack the ongoing support after a couple years they no longer offer any updates to firmware that a few other router makers do.
my connection with the viasat modem has continued to work just fine.
but as far as security? my current wn/1000 could do better if they had firmware updates.
I read the asus have a better record for firmware updates and may switch to that brand in the future.
* I look forward to reading what "old Labs" might have to say on this subject.
his posts are informative concerning routers.
At this time, the Exede WiFi Modem does not support completely disabling the internal router functions (aka, bridge mode). As such, please be aware that user-supplied routers in this configuration might require special router configuration changes, such as adjusting the DHCP scopes in use to avoid duplicate IP address assignments.
Please read this article on changing the SSID; http://viasat.force.com/kb/articles/General/How-to-change-your-WiFi-Modem-network-password
Going back to your original post (since we're spanning two separate threads with the inevitable drift) and consulting with my brother from another mother, you may want to double check the approach originally suggested by GWalk over there. We may have strayed a bit off-topic. This really should be no more difficult than connecting an Exede modem LAN port to your ASUS WAN port and resolving any router
At that point you need to enable DHCP on the ASUS router (if not already enabled), and simply ensure all access is through your router (disable WiFI on Exede's and only have the ASUS router attached to the Exede modem/router - i.e. the only access from the Exede device is to the ASUS device).
Perhaps you or someone else having that Exede modem can determine what it's default router
I have some graphics and screenshots worked up so lets begin.
Even though you may believe you have taken these steps before ... bear with me.
I believe that you did not have the proper "IP separation" before.
Those numbers can get a little slippery. There is a vast difference between .100 (point one hundred and .1 (point one)
Each place can hold a value of 256 numbers, numbered 0 (zero) through 255.
There are a number of "ports" among all the equipment ... LAN's (Local Area Network) and WAN (Wide Area Network) and its important that we be on the same page when defining them.
The Exede Modem:
Above are the Modems LAN Ports numbered 1 thru 4
These ports are used to connect to your devices if using the Modems "routing" function.
We will use only one LAN port, Port #1 to connect to our Router.
Next we have the rear the Asus AC3200. It has five ports in total. Four LAN's and a single WAN that is offset to one side.
The above ports are where we connect our wired devices rather than using the Modem's LAN ports.
The above depicts the Routers WAN port. It is used to connect the Router to the Modem.
Lets get started on our configuration.
Lets begin by connecting a single computer directly to LAN Port #1 of the Modem:
We need to disable all direct wireless connections through the Exede Modem and verify that fact.
After having done so, disconnect the Ethernet cable from the rear of the Modem and attempt a wireless connection on both 2.4 and 5 ghz frequencies. Include Guest Accounts as well.
After confirming no connections are possible power off the Exede Modem by removing AC power.
Due to the way the "leases" are negotiated between networked devices it is important that you follow the proper order on connecting and powering up the Modem, Router and other connected devices.
Next we need to connect to and configure the Router:
Connect a single wired computer directly to the Routers #1 LAN port.
No other connections ... wired, wireless
No Modem present .. it should be powered off at this point.
(Router is an Asus RT-AC3100 running the Asuswrt-Merlin firmware)
We need to set and verify the routers MODE:
Make sure that the Router is set to "Wireless Router Mode (default)" as depicted above
Doing so will set certain items such as DHCP as well as others:
Whenever changes are made, remember to hit the "Save" button while still in that category or page.
Next we need to set where or the way the Router expects to find an Internet connection.
We will first try "auto". Do this again even if it seemed to fail before. You did not have, in my opinion, the proper "IP separation".
Insure that your WAN is set to auto as outlined in red above and that the settings in the blue outlined areas are as above.
Remember to scroll down and hit the "save" button:
Next we need to perform a very important step:
Setting the Router's LAN IP.
IP addresses are important, they must not conflict, they must not overlap.
We are going to set the location of where the Router "Lives" to 192.168.2.1
Remember to click "save" after the change
Write this number down
Address 192.168.2.1 is where you will find the Routers GUI log-in screen.
That is where the Router "Lives"
The Router will start handing out IP addresses to devices starting with 192.168.2.2 and continue upwards for the next 255 devices
I believe, and we will verify this later that your Modem "lives" at either 192.168.100.1 or 192.168.1.1
We just need to insure that those IP's don't step on each other.
Once the above changes are made and the changes saved, power off the Router
With all devices off, connect as follows:
Connect an Ethernet cable from the Modems #1 LAN Port to the Routers WAN Port
Connect an Ethernet cable from a wire computer to one of the Routers LAN Ports
In the following order:
#1: Power up the Modem and let it boot up completely before proceeding
#2: Power up the Router and let it boot completely before proceeding.
#3: Power up the wired computer
Open a browser and enter 192.168.2.1
This should lead you to the Router GUI log in screen.
Log in, take screenshots of WAN, and LAN
Open a browser and enter 192.168.100.1 and see if it leads you to the Modems internal interface.
You may then secure the Routers GUI username and password as well as enable wireless encryption.
Set up a single device to test wireless connectivity.
Post back the results.
I think we can work this out.
All Hughes modems are hard wired to 192.168.0.1
That leads to the Modems SCC (System Control Center) that displays, among other things system status and web acceleration controls.
The new HT2000w WiFi modem has an addition IP address that leads to the Modem internal wireless config page.
I think that this is equal to the Exede modems :8080 port
Once we have this worked out I can repost as a topic my post above to give a "how to" on adding a user router to a Exede Wifi modem.
We just need to work out the proper IP addresses.
I have been using my own router for 13+ years with a "double NAT" without issue.
Now, just out of curiosity, if I need to forward ports, do I need to do it on both routers, or just the ASUS?
Thanks for the reply Stephen,
"Seems that the ASUS router was determined to set the DNS to exede router, so as soon as I changed it to the ASUS router, everything started working"
This doesn't really tell us much.
Can you provide screenshots of the Asus config pages so we can have definitive IP addresses?
Good Morning Stephen,
I'm glad you got things up and running.
Usually networking is a matter of resolving IP address conflicts.
I'm a big fan of connection to the Router with no connection to the modem present and pre-set the Routers LAN IP.
Question: May I have permission to use your screenshots posted above, if needed, in illustrating a "how-to" topic on adding a user router with the Exede WiFi Modem?
You have referred previously to adding subnets ... DMZ's and so forth.
I have to ask to what extent?
If you had a three story Townhouse plus basement and outdoor patio, that is one thing.
If you have a need for more than 4 Ethernet ports, I could see it.
For 95% of users a quality router is going to fulfill their wired and wireless networking needs while presenting the smallest WAN side exposure possible.
Every "exception", every "addition" increases the number of potential vulnerabilities.
When it comes to networking the KISS principle certainly applies.
I’m working thru it myself with an ASUS router.
I would recommend that you do not go the DMZ route, but rather use port forwarding.
It is tedious and not for the faint of heart.
I absolutely cannot get “AICloud to work anynore with the excede router but everything else is pretty much working even without a bridge mode on the #d€*&%’ excede “router”.
Is that because of Exede's bandwidth and streaming tricks?
I did the DMZ but either would probably work since I mainly torrent anime which is one of the reasons I wanted ipv6.
I did some poking around to find my root ip address and found out it seems to be static. So I manually updated my ipv6 tunnel and I am going to watch that address.
So I turned off DDNS in the Asus for now.