Static IP addy

mr.maroonsalty

New member
I'm trying to set up a camera that we can access, but we are stuck using Hughesnet :headwally: Even though its a very easy option that they should offer any subscriber, they want extra$. Anyone have other solutions?
 
dyndns.com They give you a free address like reefwebcam.dyndns.com then you can put the small utility on your computer which goes out and updates the domain name to the ip.
 
Your router may support automatically updating dyndns so you can skip the computer application. Afraid.org is also another option to dyndns.
 
Before you go through the trouble of setting up a dynamic DNS forwarder, you will want to ensure that you in fact have a routable address to begin with. Many providers go to great lengths to firewall their dynamic IP customers to prevent them running servers (web, camera, mail, game, etc).

Secondly, hughesnet (as I remember) does NOT offer a true unlimited service and will terminate your account or bill you for using more bandwidth than they deem acceptable, especially upstream bandwith.

Thirdly, most of the sat internet feeds have an upstream bandwith that is in the dialup range, not broadband.

In any case you should test the camera server with your existing dynamic IP before you go through the trouble of setting up dynamic DNS.
 
Thanks Bean, Hughes stinks, and they apparently do block upstream servers by limiting having a static IP address without paying them for the ability to have one. I'm not the main person working on this, my other is, as she first wants to get the camera set up in the barn, so I'm only working through her week long frustrations. I should have put "hughes" in the title maybe it be better spotted by someone using our same system. Uploads are apparently unlimited unlike mobile data plans, but hughes does restrict download to 200mb per any previous 24hrs, go over and speeds really slowwwww
 
Even though they say unlimited upstream they have been known monitor it and take action when they consider the usage inaapropriate for "web browsing".

A dynamic IP is not the same as blocking ports. Even with a dynamic IP, traffic to specific (or all) ports may be open. Best to just setup your application and try with whatever IP address you are currently pulling from their service. If it works, then dyndns or any of the other DNS forwarders will work. If the traffic is blocked, then your SOL no matter what you do unless you pay the extra money for a static IP, in which case they remove the firewall restrictions (or at least should).

I have not had to deal with hughesnet in 3-4 years so am not sure what their current policies are.
 
Thanks again. dyndns problems led back to hughes and the IP. I don't have my head too far into the project; its hers, but I want to run it by the techies here in case someone had the same problems. I can't trust the hughes and their quecard support; they know their customers have no where else to go. The tests from here said everything should be operational, but at home she was always kicked to the modem, and outside the network a "program error" would come up.
 
I am not sure I understand what you are explaining but I will try to answer from what I perceive.

If you are able to see the webcam from a remote location (using whatever IP addresss you are assigned for the time being) then things are good. In the same fashion, if using that same IP address from within your own LAN (home network) and it does not work, then don't fret! That simply indicates that their "router" has a stateful firewall that does not allow packets to return on the same interface they leave on. That is fancy for saying that you can't use your own public IP address from the LAN (firewalled) side of the router and only the public can. Oddly, that would indicate that the router firmware is likely CISCO based...

In any case from the outside world you will connect to the camera server via the public IP and the firewall will NAT the connection over to the camera servers local IP. From INSIDE the network you will simply use the local IP address of the camera server.

Make sense?
 
It does. I wasn't sure if being directed back to the router was expected, but from the outside we get a "program error" message. I think an unlimited data plan might have a chance. Our att cell has no reliable home service, but verison claims we're suppose to have 3G, so we might be able to ditch the medium speed satellite in the Pacific.
 
I'm not sure what you are asking. The camera talks to the airport, and the airport the hn7000 (hughes router). We have no problem viewing/operating the camera inside the network.
 
I wonder it could be possible to have a script take a picture from the webcam (have a really slow frame rate), automatically upload it to a webpage outside your domain and view from there.

However I'm not qualified to say whether or not that'd be something easy to do.

In-laws living on a farm wanted a security camera that's viewable from any location due to dirty stinking thieves.. but I'm not technical enough to make that happen.
 
It is called motion jpeg... and how most older generation cameras streamed to begin with. The mode of transfer is usually FTP and you need a "viewer" on the other end to put the pictures back together.

Modern codecs are MUCH more efficient and the software is fairly easy to setup. The hardest part is getting the firewall ports open and forwarded properly.
 
we are stuck using Hughesnet

You probably shouldn't be on RC because you will violate the FAP. :D I made the same mistake and was under a two year contract. I can't think of anything worse than Hughesnet. I think dial up is a better option. If you're not under contract call them to cancel and they will give you the service you want for almost free. They begged me to stay with them and I wouldn't do it. I wouldn't recommend Hughes to anyone, but you already know! :headwalls:
 
Back
Top