D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-880L => Topic started by: dr_pepper on December 19, 2017, 02:41:22 PM
-
forwarding to my internal dlink camera. meaning, i have no port forwarding or firewall rules set up. Both are blank. But when I put in my external IP addres to a browser - the 880 is autmatically forwarding it to my ip camera.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your router? Look at sticker under the router case.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- What region are you located?
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
What Mfr and model camera do you have?
Where are you trying to access the external IP address from, from home or from remote WAN side location?
Be sure to clear all browser caches before trying to enter the IP address.
Do you have remote router UI access enabled on the router?
Do you have upnp and upnp port forwarding enabled on the camera?
How many cameras do you have connected?
-
I have two separate locations. Both as follows DIR-880L HW:A1 FW:1.08WW.
The cameras behind the routers are both Dlinks. One location has 5 cameras and the other only has 1. The location with 5 cameras - the 880 will randomly forward to one of the cameras there.
For both DIR 880's if I type their external IP address into a remote browser that is what happens. It automatically forwards to the login for the internal camera. I have no port forwarding or virtual server rules set up on the 880's. WTF??
Shaw cable ISP. Both my cable modems are in bridged mode.
-
Do you have remote management enabled on your 880s?
Try changing the HTTP ports on each camera to something other than 80. Seems like the camera is hijacking port 80 for some weird reason.
-
Interesting...
What model are these cameras?
Do you have uPnP and uPnp Port Forward enabled on these cameras? If you have more than one camera, both should be enabled on ALL cameras.
Give GreenBays suggestion a try as well.
-
No. I have disabled remote admin. Sure - I can "break it" from the cameras perspective by changing ports or turning off upnp..........but why is the 880L forwarding/passing any traffic to my internal network at all when I've not set up/enabled anything. I will try a complete reset on the one tonite. All I've done to them is configured internal network (DHCP block and wireless). The rest is pretty much stock. These things shouldn't be responding to anything........at least thats how every router I've had in the past works.
-
What model are these cameras?
-
It definitely should not be doing that. Can you downgrade the firmware on one of the routers for testing?
Why are you entering your WAN IP address? (just curious).
-
Furry can you test that on your 880? ;D
I notified a tech and he will test tomorrow. We haven't seen this issue before.
-
Haven't either. Would like to know the model numbers.
I'll have a test with mine and see what I find out. I'll test with just one camera. I presume anything more than 1, wouldn't work to reproduce.
-
Ok, heres what I found with my 880L online and a 960L camera.
Using HTTP for remote logging into the router enabled and 8080 for the port. Using http://WAN IP address:8080 I get the routers log in page from the WAN side.
If I use http://WAN IP address:80 I get the cameras log in page and I can log into the router with credentials. Looking at my cameras networking settings, DHCP is being used however uPnP and uPnP Port Forwarding is enabled. HTTP Port settings for local an WAN site and upnp are defaulted to 80. I presume this is why I'm getting to the camera using this port number with the WAN IP address. Using any other port I don't get the cameras web page.
Enabling HTTPS on the router, using default port of 8081 causes login page of the router to be displayed. Trying WAN IP address with :443 causes the cameras web log in page to be displayed. ???
V1.08WW on router. v1.06 beta on 960L camera.
-
I thought I had disabled UPNP on the router - but I hadn't. Disabling UPNP on the router prevents the pass through happening. But I'm still not sure that's an appropriate design. While my cameras are password protected - they were weak passwords as I "assumed" my router would not be forwarding any traffic to them as I don't have any port forwarding, firewall rules, virtual server rules enabled. Also remote admin does not need to be enabled for this event to occur. ie you can have remote admin disabled, but with UPNP enabled, and UPNP on your internal cams then the router will pass traffic through. I don't know that enabling UPNP as the default on the router by Dlink should be the default setting given this.
As to previous questions on cameras - all are Dlink. A few 7010ls, a 5222l, and a 936l
-
it is most likely one of the cameras causing the issue. mydlink cameras do communicate with the mydlink servers using (by default) port 80 and 443. If you change the ports on the camera, or disable upnp on the camera or router, it will fix it.
I will ask techs to test with other routers.
Furry you said the 960L login is coming up (Thanks for testing).
dr_pepper which camera login is showing up? Maybe it is a particular camera/vendor causing this.
-
I tested with a DIR-890L and could not duplicate the issue (with 936L).
-
I can confirm I can't reproduce this issue with my 936L and the 880L. Using both HTTP or HTTPS.
I tested with a DIR-890L and could not duplicate the issue (with 936L).
-
dr_pepper which camera login is showing up? Maybe it is a particular camera/vendor causing this.
It would be all dlink cameras. I have two locations. One location has a 5222l and 4 of the 7010l's. At that location it is random, meaning the first camera to respond is the one I end up connecting to. At the second location I have a 936L.
-
Techs are still testing this and will submit a ticket to the engineers. In the meantime, I would either disable UPnP on the router or go in each camera and change the HTTP and HTTPS ports to something other than 80 / 443 until they can figure out the issue.