Print

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

[Damjan]

Hi,

my connection is like this. ISP modem&router Innbox F60 (192.168.64.xx), then on WAN connected DIR 882 and on LAN (192.168.0.xx) of the router WD NAS.
Everything works when I am connected directly to my router.

The problem is when I want to connect to my cloud through cellular data. It doesnt work because of  double nat they say. Is there a way to virtualy put NAS to network from ISP. Or maybe some other option?

Thanks for any suggestion...

[me_iauras]

If you have the option from your ISP to switch your FTTH gateway to "bridge mode" without the router functions activated that would be your best option . You would then just create the PPPoE session on your router and you wouldn't have any other issues (I assume PPPoE connection since that is mostly what's used in conjunction with ONT FTTH service).
If however that is not possible there are 2 other workarounds :
1. make all necessary port forward from the ISP's router to your router's WAN IP ( 192.168.64.x not the LAN 192.168.0.x subnet ) ; after that make normal port forwarding rules in your DIR 882 config portal to you WD NAS's IP  as you would normally .
2. transform your DIR 882 router into a makeshift AP ( http://forums.dlink.com/index.php?topic=40856.0 ).After turning the router into an AP you must create all necessary port forwards in the Innbox modem/router to the new WD NAS IP ( now all clients within your home will be on the same 192.168.64.x subnet leased from the DHCP server of the Innbox modem ) . The benefit with this option is that you would gain not having a double NAT to worry with and would also possibly gain some switch ports ( now the active Eth ports on the Innbox modem/router and the new DIR 882 AP would be on the same logical network and you could use them all )

[Damjan]

Thanks for your answer.

I choosed option number 2 and it works for now.
I have some speed issues, it only goes to 37MB/s, before it went cca.100MB/s, but I think that is not D-Link Issue.

Regards, Damjan

[me_iauras]

If the 37 MB/s is the throughput measured with a client connected to Wifi then that's your answer ; if however you're doing the test between a client connected via ethernet to one of the switch ports in either the Innbox modem or the DOR 882 LAN ports then that is indeed an issue .
To be able to help you possibly troubleshoot I would however need more information ; it would be great if you could make a schematic of your network in which you should include for every link the following info ( physical port , IP of that network interface and if possible interface status/PHY rate as in 1 Gb/s full duplex , 100 Mb/s half duplex   ) .
Also include the relevant configuration pages screenshots ( Port Fw section on the Innbox modem , DHCP server & port Fw on the Dlink ).
And also make sure that QoS is not enabled on any of the devices as that is usually not powerfull enough on this type of devices to be able to handle gigabit links (it's really included there for when clients have limited Internet bandwidth , <100 Mb/s , to make sure certain clients do not saturate the link but with higher tiers of internet connectivity now like 300/500/1000 Mb/s QoS only creates bottlenecks and adds latency instead of helping)

[Damjan]

I tried download speed one more time when all other TVs and computers were turned OFF, and now works with a little more then 100MB/s.
Maybe that day there were too much off everything turned on.

Somethimes we need to wait a little and everything starts working like it should 

Thank for all your help.

Regards, Damjan

[FurryNutz]

For doing any speed testing, be sure to have most streaming devices turned off or no streaming before you speed test to be sure you get a accurate speed test result.