Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[id2]

comcast_ISP<--->SB6141<--->pfsense<--->DIR-855L

what i am having an issue with,

the DIR-855L is connected via access port (non-WAN) to pfsense, with DHCP disabled, pfsense is acting as DHCP for ipv4 and ipv6.

mydlink has no visibility into any dlink device on my network.

what are the ports or address space that should be allowed?

if I was to connect the WAN port I am able to manage the dlink, devices, however then the DIR-855L is not behaving as a "AP"

Ideas?

[FurryNutz]

Your PFSense maybe restricting too much for your Cloud devices to connect maybe. The only device that mydlink does not support would be the DIR router running in AP mode.

I have my 933L camera connected to a DIR series router running in AP mode that's connected to a non-D-Link router and can see the camera both LAN and WAN.
SB-6121>Router><DIR-890L AP<>DCS-933L

[id2]

Alright. Thanks for the reply. I will look into it. Will post if I find something of value.

[FurryNutz]

Let us know how it goes...

[Hard Harry]

mydlink has no visibility into any dlink device on my network.

I think the mydlink site uses port 80 but only via the WAN port, and only to their Dlink servers.  Is the DIR-855L doing NAT or is your pfsense? If your pfsense is, then forward your public IP to what ever private IPs your cameras has. You can use different ports for different cameras. For instance forward inbound 68.x.x.x:8080 to 192.168.1.10:80 for Camera A, then 68.x.x.x:8081 to 192.168.1.11:80 and so on. This will get around any port 80 inbound block your ISP may have. This won't make it work with mydlink, but it's at-least a work around.

:;Edit:: Shiat. Just noticed how old this thread is. Sorries.

[FurryNutz]