tlarkin
VIP Member
No, you setup static ip on the server, and it uses that ip everytime, along with gateway, dns, etc. You can use "static dhcp" on router #1 so that way router #2 gets the same ip address everytime, or you can do it from router #2 and use static ip so it uses the same ip everytime.
actually, this is how you set it up, I have done it before many times for clients in small offices with multiple routers
(examples)
Primary router:
IP - 192.168.1.1
DNS - resolved by DHCP from ISP
DHCP server - enabled, IP range 192.168.1.10 ~ 254
Gateway - resolved by DHCP from ISP
mode - ospf
SSID - your network name
Encryption - WPA
Channel - 7
NAT - enabled
SPI firewall - enabled
Secondary Router:
IP - 192.168.1.2
DNS - 192.168.1.1
Gateway - 192.168.1.1
DHCP service = off
mode = gateway
SSID - your network name
Channel = 9
NAT - disabled
SPI Fierwall - disabled
teritory Router:
IP - 192.168.1.3
DNS - 192.168.1.1
DHCP service = off
Gateway - 192.168.1.1
mode = gateway
SSID - your network name
Channel = 11
NAT - disabled
SPI Fierwall - disabled
Your server, set to static DHCP in the main router to an IP address you want, so 192.168.1.100. Then, to that IP/Mac address you set up all your port forwarding from the primary router's control panel. I can ssh tunnel into my router and then run a vnc client through it remotely. I won't bother setting up any kind of SFTP because of the limited upload speeds of cable broadband, which mine cap at about 40k/s where my download is over 1MB/s. If I need to take anything with me it goes an external HD.
Now when anyone comes over to use wifi they will be assigned an IP via DHCP, every time you add a computer (or network device) to your network they will resolve everything via DHCP. Each router has to be wired together and it repeats the wifi signal on different channels through out the site to reduce interference. I set this up for many larger warehouse type offices that required a cheap and secure solution for their small network.