c69454 said:
]For dumb people like me, routable ip means it has to be a 2nd ip from my isp other then the ip my router is using?
A routable IP# is an IP# that is routable over the Internet, as opposed to one (for example, 129.168.0.1) which can only be used on a local area network.
putting the machine in the hardware DMZ is not good enough?
It is if you're only using one IP# or if your router can route more than one IP# through to the DMZ, and if you know enough about what ports to open to make sure your server can work from a DMZ.
Or I would have to plug the linux right into my cable modem so that the router doesn't take the ip?
Many of us would do that. It's going to be that way at the data center; might as well get it ready now. But we don't (see below).
I'm sure to you guys that know what you are doing it makes sense to have a box 100 miles away and then set it up, but for someone like me just learning it makes alot more sense to have it here infront of me and working before I mail it to my colo to have installed.
But you're going to have to install the data center's IP#s before you ship it and if you make any mistakes it's not going to work.
Unless the data center people will do that part for you, and even then you're going to have to have the DA license changed for the new IP# and then make some changes (search these forums) so DA will work with the new IP#.
Here's how we do it:
We have two networks here; we have a switch between our network bridge (for you that's probably either the DSL modem or the cable modem) and our router. Everything we set up outside the router is our office public network, on routable IP#s we get from our connectivity provider.
Inside the router we have our LAN, on private IP#s, provided by DHCP.
We don't use the router's DMZ; it's too limited.
We build our servers inside the LAN, on private IP#s, using DHCP to assign an IP#.
When the box is installed (in our case CentOS, latest version, server install, almost no extra packages [search these forums for our configuration]) we harden it (sorry but our scripts are proprietary
) and then install network scripts so the next time it's booted it'll work from our Data Center on the IP#s there we've already assigned for it (that takes a bit of experience; we used to occasionally get it wrong but by now we've gotten used to doing it right).
Then we take it to the Data Center, plug it in, and go home.
The next day we install DA from the office.
Jeff
