Print

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

[nicknml]

I'm using it as a backup server. So lots of writing by a couple of people. I also have an HTTP server on that computer, setup in the router a VS and works just fine.

If it's just being used by a couple of people how about something such as SSH

A VPS is another solution as you don't have to worry about any NAT issues, such as this one that I have:

http://www.host1free.com/free-vps/

Note that with their free tier you only get 1Mbps up/down.

[FurryNutz]

Had one idea, why not set the PC that you want directly connected to the ISP modem for ease of set up and then connect everything else to the DIR-655? Kind of a last resort plan of action if you can seem to get the configuration set up with the DIR-655:

ATT Uverse - >< FTP/BACKUP PC
               | - ><DIR-655<>All other devices connected to 655.

[coderforlife]

I really wish I could just do this:

Can I tell the router to map "files.example.com" to a specific IP (like I would with the hosts file on computer)? This way when the computers are trying to resolve my domain name they could be given the local address and all would be fine. It should not map the rest of the subdomains (*.example.com) since these could all be hosted elsewhere.

[nicknml]

I really wish I could just do this:

Can I tell the router to map "files.example.com" to a specific IP (like I would with the hosts file on computer)? This way when the computers are trying to resolve my domain name they could be given the local address and all would be fine. It should not map the rest of the subdomains (*.example.com) since these could all be hosted elsewhere.

Perhaps you could via DHCP reservation on the network settings page.

[nicknml]

If that doesn't work you can set up a separate DNS server (you could do it on the same host as your ftp server).

[coderforlife]

Update: tried plugging the client side into the AT&T modem with the server inside the router. This worked, presumably since I was using the WAN IP of the router outside of its network.

VPS: I have a VPS, but that won't really work since they are "limited" in size (the one you have is 2GB, the one I already have is 50GB). Many backups being "local" make it not so bad to be backing up 200GB of data per machine. This is why a local solution fits better, with ony a few remote backups being performed.

Running a custom DNS server is an interesting idea. The reserved name in the router did not work. I still have a few other ideas. Then I will try the custom DNS server.

Placing the FTP server on the modem and everything else on the router is also not probably going to work due to the wiring in my house (I could add another Ethernet wire to the wall, but that's a bit more effort than I want right now). Other computers share the current wire through a switch.

It seems silly for all these workarounds when the router seems to be able to work properly (when using VS). Just wish VS would accept ranges.

Thanks for all your inputs! I will update with any more information as I try other things.

[FurryNutz]

Been able to configure FZ, DIR-655 RevB1, PF and getting connections using the following:

[nicknml]

Throwing out another idea, does the host that you are running the ftp server on have multiple NIC's? if so, you could use that as the router and the DIR-655 as simply an access point.

[coderforlife]

@nicknml - No multiple NICs. Also I tried setting up a DNS on that machine but things did not work out. The DNS works: if on another machine on the network I set the DNS servers to 192.168.34.150 (the custom DNS) and 192.168.1.254 (the AT&T modem) it works great (the Internet is accessible and the FTP server is accessible via the domain name). However setting those same exact values on the DIR-655 router itself (for primary and secondary DNS) causes no domain name resolution. It seems as though the DIR-655 does not use the secondary DNS at all (or at least becomes confused when the first one is on it's own network). If the computer hosting the custom DNS was disconnected there was still no domain name resolution. I am quite confused by where the problem is actually happening with this custom DNS. I know it works at the computer level, but apparently not at the router level.

@FurryNutz - This is essentially my setup. I have it all as one rule, include 989/990 (for implicit SSL), and without the UDP ports.

The problem I see is if the WAN IP of the router is the same as the external IP and you use the external IP (or a domain name that resolves to it) port forwarding won't work. However, if your WAN IP is not the external IP or you don't use the external IP (or a domain name that resolves ot it), than it does work.

So, is your router's WAN IP the same as your external IP? And are you using the external IP / domain name to access the FTP server?

On this note, I am going to see if the AT&T modem will assign a private IP to the router while still doing DMZ, or just forward the necessary ports to the router. These setups should resolve the issues. Quick question though, when the router reports to the dyndns server, does it use it's WAN IP or the external IP?


Thanks again for your inputs!

[FurryNutz]

My router receives a public external WAN IP address and i use this address to access the FTP server from external based clients.

List of NAT Loopback Supporting Routers

[coderforlife]

Yes, accessing through external clients is fine and always has been for my setup. It is internal clients that don't work. And the reason just switching from the external name to the internal IP isn't acceptable is the backup software sees that as switching backup destination, resulting in a re-scan which takes a whole heap of time (checking every files' file times in the backup).

So the problem (if you have any power to "escalate" issues to D-link) is that port-forwarding rules do not work when using the external IP address internally, however VS rules do work along with external/external and internal/internal IP address setups.

Will to see if I can get the modem to not set the router WAN IP to the external IP. Also, how does this effect dyndns?

[coderforlife]

Well, using selective port forwarding on the modem worked - mostly. It won't allow me forward any ports over 50000 (but everything from 1 to 50000 inclusive). So the passive data ports I am using are 49152-50000. However upon activating the rule with that range I can no longer access the modem service pages at all... Even with that problem it is still the best solution so far... the BEST solution would be for D-Link to fix the problem with port forwarding.

Funny how the cheapo, free, modem from AT&T can port-forward internal requests using the external IP but the D-Link router cannot. They already have the "technology" to do it (in Virtual Server setups), so it would be GREAT if they could get it working for port-forwarding.

Thanks for your time, and if you have any more ideas that would be great.

[davevt31]

Sounds like your running into a loopback situation with the internal clients.

[FurryNutz]

Speaking of loopback, has anyone tried turning OFF SPI? Lycan mentioned that SPI filters lookback traffic.