Hi, me again. Hopefully a quick question. I have a new 1U server that i just built with Debian. It's going to Virginia to a colo facility, where it will soon get a block of public IP's starting with 65.15.208.220. Currently, I have the server on my private subnet at 192.168.0.50. I'm wondering if there is a way to set this up with it's public IP block and test that it actually works so when they plug it in at the colo facility, I can guaruntee that I can talk to it here in Minnesota instead of paying some support person if something doesn't work. My firewall box has 3 NICs, only two are used as I never setup my DMZ. One is my public interface at 24.106.16.242 (eth0), the other is my private network gateway at 192.168.0.1 (eth1). What I'm wondering, is can I use the 3rd NIC (eth2) and give it and address of 65.15.208.219 to act as the 65.15.208 gateway and set up a route so that the firewall box routes to nic 3 for 65.15.208.xxx instead of the public interface default gateway (eth0)? Setting up the NIC is easy (ifconfig), but I'm always a little confused about the routing part. Does this sound right? ifconfig eth2 65.15.208.219 netmask 255.255.255.0 up route add -net 65.15.208.0 netmask 255.255.255.0 -gw 65.15.208.219 dev eth2 Of course, this would then route ALL 65.15.208.x IPs and not just the 10 IPs I want to test. I suppose I could just try this and see what happens, but anytime I start hosing around with the network interfaces on my gateway box, bad things happen... Any thoughts/suggestions? Josh _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list