Here's what I've got in my small office:
- a static public IP address - 8 IP subnet configured like this xx.xx.xx.16 - network xx.xx.xx.17 - gateway xx.xx.xx.18 - 22 usable xx.xx.xx.23 - broadcast /29 - CIDR number - an ASUS RT-N16 running DD-WRT v24-sp2 (08/12/10) mini - build 14929 - internet server1 xx.xx.xx.18 - internet server2 xx.xx.xx.19 - various printers, computers, tablets, etc on 192.168.xx.xx
I need to route internet traffic to the two servers and NAT all of the other devices. I've searched high and low on the DD-WRT site and found nothing on how to do this. It doesn't seem like it should be hard, but I am stumped.
11/12/12 - 10:30 am
Here are the answers to your questions:
What internet traffic do you need to forward to the two servers? Are you talking HTTP, SMTP, etc.?
The two servers support different web development environments. They both need to have the usual internet ports open, HTTP, HTTPS, SMTP, etc. The two servers are actually virtual machines running in a VMmare ESXi environment. My current clients have different server environments, Linux vs Windows, hence the need for different servers.
could you clarify your ip address block/scheme.
My ISP has given me a total of 9 IP addresses. The static public IP I speak of is from a completely different IP range than the block of 8. If you were to ping the static IP the reply would come from my DD-WRT router. My ISP is routing traffic destined for the xx.xx.xx.18 through xx.xx.xx.22 range to that address. My router has to be configured to send it on to the correct network in my office. When things are working as they should a ping to xx.xx.xx.18 would be replied to by the server configured with that address.
The 192.168.xx.xx NATed network is for all of the other devices in the office that do not need routable IP addresses. Those are the printers, computers, etc, etc used in the office.
Please provide more detail; presumably "xx.xx.xx" refers to public IP addresses, not RFC1918 space.
xx.xx.xx.xx is referring to public IP addresses. I am also using RFC1918 space as well because, honestly, my printer doesn't need to connect to the internet ;-) but my laptop does. I should have put the CIDR number /29 in the original config info above, that's fixed now.
Pretty sure I'd just say "no" if someone asked me to set up a piece of SOHO gear running DD-WRT in a professional capacity.
What I'm doing is the very definition of SOHO and I couldn't agree more and maybe someday there will be a budget for nicer network equipment, but for now it's what the business can afford.
Lastly, I know some of the things I've said are not best practice, for example replying to a ping from the internet, running Windows on anything but I don't want those things to be a distraction.