Control Center Page Not Loading - HughesNet Community

mountain-man · ‎05-08-2018

This is a new problem... we recently restored our seasonal service, didn't work, and a tech came out and replaced both the radio on the dish and the modem with the new version. I guess it's a 2000W and the old one was a 1000 (?), I'm not on site now.

I'm not using the built in wifi. Our setup uses a LAN able from the modem to our router (a PC running Zeroshell, which is a Linux router software), which is in turn connected to a long range Ubiquiti outdoor AP with two repeaters. Zeroshell uses 192.168.0.75 as the IP for its internal configuration page, the Hughes modem assigns it an IP of 192.168.42.100, and the other network card (going to the outdoor AP) is 192.168.2.1. Devices on the outdoor wifi network are assigned DHCP IPs between 192.168.2.50-255. Zeroshell is set to use 192.168.0.1 as the gateway.

Anyway, I now have internet connectivity but I'm unable to get to the system control center at 192.168.0.1 from any device on our network (I was using two different Android devices with Dolphin browser). I can, however, get to the wifi settings page at 192.168.42.1. If I do connect to the built in wifi I can access the control center. WIth the old modem, I never had this problem, but of course it didn't have a built in router... I see no way to disable the routing functions in the new modem.

I'm thinking it must be a gateway or netmask problem, but everything I've tried not only doesn't fix it but also kills internet access.

C0RR0SIVE · ‎05-08-2018

@mountain-manwrote:
Zeroshell uses 192.168.0.75 as the IP for its internal configuration page, the Hughes modem assigns it an IP of 192.168.42.100, and the other network card (going to the outdoor AP) is 192.168.2.1. Devices on the outdoor wifi network are assigned DHCP IPs between 192.168.2.50-255. Zeroshell is set to use 192.168.0.1 as the gateway.

Anyway, I now have internet connectivity but I'm unable to get to the system control center at 192.168.0.1 from any device on our network (I was using two different Android devices with Dolphin browser). I can, however, get to the wifi settings page at 192.168.42.1. If I do connect to the built in wifi I can access the control center. WIth the old modem, I never had this problem, but of course it didn't have a built in router... I see no way to disable the routing functions in the new modem.

I'm thinking it must be a gateway or netmask problem, but everything I've tried not only doesn't fix it but also kills internet access.

You will need to reconfigure Zeroshell to use something outside of 192.168.0.0/24, you might want to configure it to use 192.168.1.0/24 instead... That's most likely where your conflict is coming from if it's listening for the 192.168.0.0/24 subnet on the LAN side instead of just passing it through to WAN.

mountain-man · ‎05-08-2018

Makes sense. I did try changing Zeroshell to use 1.75 instead of 0.75 but lost communication with the zs interface.

Or maybe I can set a static route to 0.1?

C0RR0SIVE · ‎05-09-2018

You might be able to set a static route up in your router/firewall, but I would have no idea how as I am not familiar with it. No promise that would work though. It kind of bothers me that if you change the management IP that you can no longer access the WebGUI...

Are you sure your lan subnetting is correct so that you can access it?
Are you using vlans?

What is the WAN IP of your Firewall?
On the LAN side of your firewall, how many NIC's are you using?
What is your LAN side IP address scheme, as well as subnet?
Can any device access the current management network? Wired, as well as wireless?
Could you potentially provide a logical and physical network map for us to take a look at?

mountain-man · ‎05-16-2018

What the WAN IP is isn't clear... by default ETH00 is 192.168.0.75 (which is also the management GUI address) and that was fine with the old modem that was at 192.168.0.1 and didn't assign DHCP IPs to connected devices. The new modem now assigns 192.168.42.100 to Zeroshell's ETH00.

Zeroshell's ETH01 is 192.168.2.1. That's wired to the Ubiquiti AP which is 192.168.2.2. Clients connect to that AP, and ZS assigns them IPs from 192.168.2.100 to 2.255. There are two more Ubiquiti devices configured as wireless bridge/repeaters at 192.168.2.6 and 2.11, which more distant clients connect to.

No VLAN. The subnet mask everywhere is 255.255.255.0. As it stands, clients can access the internet, the ZS interface at 192.168.0.75 (192.168.2.1 also works), and the wireless config page at 192.168.42.1, but not the satellite information page at 192.168.0.1.