We got ViaSat business satellite internet for our company. We got a modem with 4 ports on the back that connects to a satellite dish. If we plug any networked device into the ViaSat modem, we can browse the internet fine by getting a DHCP address assigned. This was tested by plugging in 3 laptops to the modem switch ports. For wireless access within the office, we opted for the Cisco RV340W. We figured it would be plug and play, but it's not routing clients that connect to it out to the internet.
The RV340W initial setup process went fine. We connected the WAN port on the RV340W to an open switch port on the modem. We set the RV340W for DHCP, created a wireless access point name, saved the config and rebooted the router. We selected all defaults. When the router came back up, there was no issue with clients seeing the newly-created WAP and connecting to it. They just couldn't get out on the internet. It was like the router was not routing them out.
What we have tried in debugging:
- giving the RV340W the MAC address of one of our connecting clients - FAIL
- hardcoding the route into the route table using both the IP address of the router (192.168.1.1) and the ViaSat modem (72.x.x.x) - FAILS
- changing nameservers on the router from the ones ViaSat gives it when connecting via DHCP to google's DNSs - FAIL
- disabling the fireweall completely - FAIL
- turning off all security on the WAP (no password required, etc.) - knew this wasn't the problem, but still didn't work
What does work:
in diagnostic mode, the router can do nslookups on "yahoo.com" and any other domain name, so we know it's getting out onto the internet through the modem. It's just not passing that capability onto clients.
Any suggestions or help?
