Print

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

[haraldinho]

I have a fixed external ip address.

I have port forwarding setup for accessing a NAS inside my LAN, lets say port 12345

Now when I use my laptop outside my own LAN, e.g. 99.99.99.99:12345 resolves nicely to my NAS. But when I use the same 99.99.99.99:12345 inside my LAN, it does not resolve. Instead, it gives me a 'server takes too long to answer' error

I have also setup a virtual host to an ip cam inside my network. That one resolves just fine. I tried enabling remote management on the DIR-655 and also that works fine using 99.99.99.99:8888.

When I replace the external ip address with the internal ip address of my NAS, thus bypassing port forwarding, it obviously also works ok.

Does anybody understand why the forwarded ports are not accessible when I use my own external fixed IP address? Does the DIR-655 treat it different than other external IP addresses?

Thanks!

[FurryNutz]

Your trying to go from the LAN side client out thru the WAN side of the router and back in I believe? I don't think this process works unless some form of loop back is used maybe. If your resolving from WAN to LAN and LAN to LAN then it's working as expected. Going from LAN to WAN then back to LAN from the LAN side probably won't work. Theres no real reason to use that forum of traffic flow when you can go from LAN to LAN. Only WAN to LAN should work if PF is properly configured. For LAN to LAN you would use the LAN side IP addresses only, not the WAN public IP address. My 2 cents.

[haraldinho]

Hi FurryNutz,

I indeed try to do LAN-WAN-LAN. It works perfectly for virtual servers and DIR-655 remote admin. But for some reason not for pf addresses.

The problem is that I have apps on my iPhone for accessing my NAS. I have configured the WAN address. That works perfectly fine when I am at work or on the road over 3G. But as soon as I get home, I have to configure the internal IP address to keep using it. Not nice...

Personally, I see no fundamental reason why it should not work. I think I have some misconfiguration in my router, but I can't figure out what it is...

[haraldinho]

Problem solved by another post in this forum: http://forums.dlink.com/index.php?topic=50150.0

Solution: set pf up by using virtual servers.

[FurryNutz]

Awesome, I forgot about that. 

Enjoy.