Forum Discussion
I understand the static IP part, which you mean that you have set, defined IPs for each device within your local LAN.
I will also assume that your system does not require any kind of port mapping or port triggering for things coming from outside the HughesNet network. That would be problematic because although you have what appears to be a public IP at the modem it is not accessible from outside HughesNet. What this means is: If the software uses arbitrating/intermediary clouds to interface between the computer and the collection devices instead of talking directly to them within the LAN, the system might not operate properly - anything external to HughesNet can't reach in and see the computer, nor the devices to do anything with them.
I realize that may have worked under a terrestrial DSL, however HughesNet uses double-NATing/IP translation between the modem, beam and groundstation, that may cause such a thing to be inoperable.
Hey Mark,
Thanks for your reply. I was just getting ready to reply when David came up with a direction of sorts for me to take. Both the IP address for the camera and the Davis console end in .1.4 or .1.1 respectfully. He mentioned that the range for IP in hughes is .42.xxx
So now I'm looking to see if I have to change them in the camera/Davis or just find a work around thru the Hughesnet modem, possibly using the Mac address.
Any thoughts?
Brad
- MarkJFine3 years agoProfessor
He did bring up a good point that I hadn't thought of.
I would change them at the devices just to be sure. I thought the MAC address thing is really for reserving pseudo-static addressing within DHCP (automatic), but only for those connected by wifi - not ethernet.
Related Content
- 2 years ago
- 8 months ago
- 3 years ago
- 4 years ago