Re: Foscam Not Working Outside Home Network
Antipas Zorn
TL;DR: foscam cameras work great on other routers outside the wifi network, but do not work reliably with two Netgear routers now. On the latest R6900 router, cameras work well on Cricket (AT&T) network, but do not work well on Verizon LTE network. Same setup with ASUS / Linksys worked great for years, why?
Then we switched to Cox Gigablast (fiber optic network), and Cox gave us a brand new R6300 AC router in January of 2016. I set up the static IP addresses of the cameras (outside the DHCP address range), set up port forwarding for each, just like how they worked on my Linksys WRT54GL.
Thinking that Cox network was the issue, I debugged with Cox and didn't get a resolution. I then tried putting my old WRT54GL on the Cox gigablast and the cameras instantly came on outside my network, voila!!
So a VERY ODD problem!! The problem is I can't reliably access my Foscam cameras outside my network, very sporadic initial access on my Verizon iPhone 6 on LTE (and this exact set up worked perfecly with the ASUS router before it died), and it works reliably with the Cricket / AT&T network.
The foscam cameras disconnecting when not on home network is because of a known issue with Netgear's firmware. It is because it is thinking the cameras being accessed from the outside network is a DoS attack. If you go into the router settings and go to Advanced, Wan Setup, and then CHECKMARKDisable Port Scan and DoS Protection. This will disable the DoS protection and fix your issue. It is enabled by default. Sadly this is the only way to resolve this. I have the R8500 and Netgear just released 1.0.2.64 firmware for it that fixes this issue so you don't have to disable the protection for it to work properly. in the R8500s new firmware release notes it states:
I just got 2 foscam cameras set up this weekend with a Belkin Router. I set them up through dyndns.org so I can view my rental property from my house. They are working in a pitch dark room at 10pm and you would think all the lights are on in the room, truly amazing!!!!
i would ask that, are you had with the camere such Problem that after 19-20:00 Cet until 6:00 the Camera is not working?
i use ddns on the router and on the camera, the cameras have fix ip configured and they are not reachable via ping. but after 06:00am they are working, i have 4 foscam FI8904W and 1 Apexis pan tilt outdoor camera. and from the foscam is 2 affacted with this issue.
i hope you can understand me and you can help.
Thanks a Lot.
Zoltan
Hey! Bought a Foscam 8910w and have it hooked up to my router wirelessly, attached to synology 214play and I've given the cam a static IP. It works, but it keeps dropping connection. No real reason it seems. Thoughts? I'm on quickconnect and accessing it outside my home network. Do I need to port forward? I'm little nervous about that. Thx!!
I have never tried to contact support. Sorry. Might be they are working from home during the pandemic and operating at diminished capacity. When I was setting up I had to contact my ISP to help me get into bridge mode on my modem. But probably a different issue for you.
When outside your home network, your DDNS address will direct outside web traffic to your router, but we need to get the outside traffic to your specific camera on the network. We do this with a port number. Your DDNS address is similar to a street address. Your remote port number will act similar to a specific numbered address on that street.
On local network can you see webcam at :456? Great. Can you not connect to webcam from the outside world (that is :456 is firewalled off)? Great. If not reconfigure your webcam and port forwarding/firewall rules on your router.
Now you need to add a SSL certificate and the associated private key. You can generate one signed by a certificate authority (e.g., from startssl.com for free) or generate one yourself that is self-signed (and will not be initially trusted by web browsers). Setting up a CA-signed certificate will be more complicated for a home network where you'll have to get a domain name (that you can prove to the CA you own), set up dynamic DNS to that domain name, etc. (If you are trying to get started with Dynamic DNS - is a great place to start).
The final step is to configure your router to do port forwarding. That is when you connect to (port 443) from the outside world, set it up to port-forward to 192.168.0.101 (port 443). Possibly set up dynamic DNS so if your home IP address changes it still points to the right place. Some ISPs do block port 80 and 443, so you may have to change it to some other port.
Ah, now it makes more sense; seems like your app is trying to reach the camera from inside your own network but it's trying to access it from the outside public IP-address. This will require a Full-NAT rule:
I didn't think of that but now that you mentioned it, when the device is already connected to my home network through the VPN, there should be no need to point the phone's camera app to a dyn dns account?
My goal is to use the camera as a baby monitor and I don't necessarily need/want to be able to access it from an outside line (3G) but that feature might also be nice. I tried a few of the instructions with the port forwarding, etc but without even having the camera working correctly I'm holding off on that for now.
Ready to enhance your home security? Learn how to seamlessly add Foscam to your wireless network for easy monitoring. This comprehensive guide provides step-by-step instructions, troubleshooting tips, and app integration, empowering you to take control of your Foscam camera remotely. Get ready to revolutionize your security setup!
You can get rid of wires and embrace wireless technology simply by eliminating them. Obtaining the connection between your Foscam camera and your wireless network is a significant step toward safeguarding and maintaining your home.
Now tell us about their security! IoT devices are notorious for their myriad problems here. Common issues include firmware updating authentication, encryption of images over network/to cloud/to portable devices, default/fixed admin passwords, hackability into home network, ad nauseam. Home DVRs w/security cam packages add another layer of similar issues. These have been widely reported. Basically: cheap & plug 'n play = insecure
With an insecure camera system not only do you have to worry about that system being vulnerable to hacking but other devices on the network that can become vulnerable as well. According to this story in the Register, CCTV systems with backdoors can be used to attack other devices on your home or business computer network and steal sensitive information.
Using the P2P or Peer-2-Peer method for remote connection is the easiest to set up and is becoming increasingly popular. The P2P method does not require any complex networking like port forwarding, or VPN. Primarily, home consumer oriented devices use P2P as the way to remotely view because it is easy to setup with a smartphone by non-technical users.
Port Forwarding is the process of allowing certain types of internet traffic to flow through the firewall that is built into your internet router and get into your camera recorder. This process is difficult for people who have little or no IT networking knowledge as it requires logging into the internet router and making changes. We offer paid networking services which are available here on our website. This service allows one of our knowledgeable technicians to login to your computer remotely and set up port forwarding in your internet router.
VPN is relatively easy to setup on most home consumer routers and can be used on either a PC or Mac computer, or even an iPhone or Android Phone. While you are out and about and using cellular data on your phone, you can establish a VPN tunnel to your home network to securely access your camera system.
Hello, i have a Revo security camera system and have never been able to get it passed the T-Mobile internet. I have it wired to my router and have even gone direct to one of the ports on the back of the gateway and nothing. I had Xfinity/Comcast prior and did not have to do anything special like port forwarding to view my cameras from outside my home network. Any help/advice is appreciated.
There are plenty of security cams on Amazon at bargain price, Looks they want to kill any competition. Every one of this cams will open a backdoor in your home LAN. I needed some support and I emailed them. One hour after I got an answer to my email containing two pics from my house taken with my camera! I believe it is mandatory to warn the user if the equipment connects to an outside server. No warning given. Everything happens in stealth mode. Here is one:
One of the many hosts that Foscam users reported seeing in their firewall logs was iotcplatform.com, a domain registered to Chinese communications firm ThroughTek Co., Ltd. Turns out, this domain has shown up in firewall logs for a number of other curious tinkerers who cared to take a closer look at what their network attached storage and home automation toys were doing on their network.
I am trying to get an IP camera connected to my Ubuntu Linux (16.04) machine. At work I am responsible for a camera network of more than 60 cameras, however there I use some window tools to determine IP addresses etc. for Axis cameras. At home now, trying to use my Ubuntu Linux machine to see 1 camera plugged into my ethernet port.
If you like the flexibility to get into the code and address what isn't working, this can be a good solution, although you might need to add your own IR illumination for nighttime. I'd do my homework to see if, by the time you add up the power supply, outdoor case, wipi, raspberry pi, camera, and illuminator, will you have a solution that is superior to a comparably priced commercial surveillance camera?.
CCTV: A small environment with three foscam PTZ cameras (one on front-door, one on garden entrance and one in the baby room) which are managed from a laptop which is doing movement detection during night and when we are not at home. For my initial redesign this environment is not yet included. Currently alerts include 30 seconds of footage that is send through a gmail account to have it directly off-site.
aa06259810