Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

I NEED SOME ADVICE...

Status
Not open for further replies.

linuxtricks

IS-IT--Management
May 24, 2000
111
US
I am looking to set up the following servers from my home:<br><br>-----------------------<br>Firewall<br>Internal DHCP Server<br>Gateway<br>Internal DNS Server<br><br>External DNS Server<br>Web Server (running Apache,MySQL,PHP4)<br>qmail E-Mail Server<br>Secure FTP Server (using ssh2)<br>and Quake 3 Game Server<br>------------------------<br>I currently have 2 machines to split the server up on:<br><br>400Mhz Celeron, 256Megs Ram, 10Gig HD<br><br>233Mhz Pentium, 128Megs Ram, 2Gig HD.<br><br>I would like to use OpenBSD for the Firewall, etc., and Redhat Linux 6.2 for the Web, Quake 3, etc. servers.<br><br>Would anyone have any helpful (experienced) advice as to how I can break the services up between the two machines?&nbsp;&nbsp;And, more or less, which machine would be best to use with what particular service?<br><br>I am just a bit confused as to what direction I should persue.<br><br>Thanks in advance for any help! <p> <br><a href=mailto: > </a><br><a href= > </a><br><i>try not!</i><br>
<i>do... or do not. there is no try!</i>
 
I'd say put the internal DNS, internal DHCP, and Q3 game server on the &quot;internal&quot; RH6.1 box.&nbsp;&nbsp;Put everything else on the outward facing OpenBSD box.&nbsp;&nbsp;This way, the common targets for abuse are on the internet facing firewall box.&nbsp;&nbsp;If any vandals run a DOS attack on a box, it will be the one running WWW, FTP, etc.&nbsp;&nbsp;If the box goes down, you lose your net connection, but keep your internal &quot;mission critical&quot; stuff safe and sound.<br><br>As you want to run a Q3 server, use the 400Mhz/10Gb disk box for the internal box, as I'm guessing Q3 will eat up those CPU cycles...&nbsp;&nbsp;Also, don't run any network servers such as web, FTP, telnet, email, etc on the internal box.&nbsp;&nbsp;That way, if the &quot;firewall&quot; box is compromised by a cracker, you haven't got anything they can attack on your internal box.<br><br>You should think about copying essential configuration files from the external box to the internal box for backup purposes.&nbsp;&nbsp;Use something like Tripwire to get checksums of these files and save the checksums to a secure medium.&nbsp;&nbsp;(CD-R, floppy disk, anything you can take out of the box and keep somewhere safe.)<br><br>Hope this helps. <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits
 
Oops - I forgot to mention performance...&nbsp;&nbsp;The 233 box, as it stands, should be able to handle all the various network services that it will be running.&nbsp;&nbsp;If you start running into performance issues, see where the bottleneck is and upgrade it.&nbsp;&nbsp;Memory may be the first casualty, with your network interface (10Mb/100Mb/ISDN/something else) being next.&nbsp;&nbsp;Unless you're expecting to receive several thousand web page hits, emails, or FTP request each day, you should be fine. <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits
 
Thanks AndyBo.<br><br>Are you saying that the following should run on the OpenBSD/233Mhz machine with no problem?<br><br>1. Firewall<br>2. DNS Server<br>3. Web Server (apache,mySQL,php4,etc.)<br>4. qmail Server<br>5. FTP Server<br><br>And, I should be able to patch holes in the Firewall to get to the 400Mhz Redhat Linux 6.2 machine located on my 192.168.0.1 LAN to run the following?<br><br>1. Q3 Server<br>2. DHCP Server<br><br>Currently, <b><font color=red>all</b></font> of the above is now running on the 400Mhz machine.&nbsp;&nbsp;I have a spare 233Mhz machine that I'd like install OpenBSD on because I heard its the most secure OS in the universe.&nbsp;&nbsp;I'm sure it can be a good replacement Firewall compared to the minimally configured scripts I use now.<br><br>I <i>am</i> familiar with building the DNS and WEB Servers from scratch on the LINUX machine... but <b>never</b> attempted to install/configure it on OpenBSD.&nbsp;&nbsp;Is there a difference?<br><br>Am I getting closer to actually figuring out what the heck is going on yet?&nbsp;&nbsp;=)<br><br>Thanks for the help.&nbsp;&nbsp;I really appreciate it!<br> <p> <br><a href=mailto: > </a><br><a href= > </a><br><i>try not!</i><br>
<i>do... or do not. there is no try!</i>
 
Yep - I think the 233 machine should be able to handle the services listed without any problems.&nbsp;&nbsp;However, it does, of course, all depend upon how much each service is going to be accessed.&nbsp;&nbsp;For example, if you are expecting thousands of accesses a day to the FTP server, you should be looking at a bigger box.<br><br>Just one thing - make sure X isn't running on the OpenBSD box.&nbsp;&nbsp;X can eat system resources that are needed elsewhere.<br><br>As to OpenBSD being the most secure...&nbsp;&nbsp;Well, any box is only secure as you can make it.&nbsp;&nbsp;I've not got much experience with any of the BSD (Open, Net, or Free), so I can't really comment too much on that.&nbsp;&nbsp;However, I have heard similar things about the security of *BSD releases.&nbsp;&nbsp;I think it's related to an exercise that the maintainers carried out a few years ago to go through the kernel code line by line to identify potential problem areas.&nbsp;&nbsp;ie, parts of the kernel that might be subjected to buffer overflows, for example.<br><br>As far as building the binaries from source on OpenBSD goes, there should be little difference.&nbsp;&nbsp;At the end of the day, OpenBSD is, after all, just another version of Unix.<br><br>When you're setting up the firewall side of things, you might want to take a look at Mason (<A HREF=" TARGET="_new"> you do with Mason is install it onto the box you want to run the firewall on, and run it.&nbsp;&nbsp;You then connect to the server network services you want to run on the firewall box.&nbsp;&nbsp;When you've finished, you stop Mason and it generates a set of firewall rules for you.&nbsp;&nbsp;Obviously, you still need to go over the rules manually to make sure they are OK, but it's a big help when setting up your firewall.<br><br>Just one question - why do you want to run a DHCP server?&nbsp;&nbsp;For two machines, one of which (the DHCP server) will have to have a static IP anyway, it doesn't seem to be worth the effort of setting it up and maintaining it...<br><br>Anyway, glad to be of help :) <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits
 
AndyBo:<br><br>The <i>DHCP</i> server helps me a great deal.<br>Besides the (2)server machines, I have 3 more client machines.&nbsp;&nbsp;(2) that I use, and (1) my girlfriend uses.&nbsp;&nbsp;I find it a lot easier to configure (1) machine to hand out information... than to reconfigure all machines on my network each time I peform upgrades to the OS (or whatever type of system reconfiguration that goes on behind closed doors).<br><br>Not only that... but an average of 5 to 6 friends bring their machines over for the Friday - Poker night (which now-a-days means... Quake 3 Lan party)... so it helps to have my network act as *plug and play* for all.<br>-------------------------------------------<br><br>So... as you can probably tell... my little home network connected on cable... is pretty important to me.<br>Thats why I want to have it protected as secure as possible... without limiting access to the external world.&nbsp;&nbsp;OpenBSD has great functionality for this.&nbsp;&nbsp;While I want to be invisible to the external world... I want my users to have carte blanc access out.<br><br>Thanks. <p> <br><a href=mailto: > </a><br><a href= > </a><br><i>try not!</i><br>
<i>do... or do not. there is no try!</i>
 
Ah - OK - that makes sense, now, and it was kind of what I suspected when you said you wanted to set up a Q3 server.<br><br>In that case, everything detailed above should be OK.&nbsp;&nbsp;If the 233 box starts to groan a little under the strain, then you might want to move things onto the 400 box.&nbsp;&nbsp;Email first, then www, then DNS (making sure you set up ACL entries for DNS), until the 233 box starts to cope a little better.<br><br>Good luck with everything! :) <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits
 
AndyBo, I have a guick question for you concerning the above recomendation, wouldn't he be able to move some of the services to the &quot;big&quot; box and just disable them while Q3 is running? I am assuming that the Q3 will not be running all the time. I am not sure how the email is setup, but could it be turned off for a few hours, then when it is turned back on, wouldn't it go and retrieve the waiting mail?<br><br> <p> fenris<br><a href=mailto:fenris@hotmail.com>fenris@hotmail.com</a><br><a href= > </a><br> I am interested in Mining Software, as well as Genetic Algorithms.
 
Yep.&nbsp;&nbsp;That would definitely be possible.&nbsp;&nbsp;However, I was thinking from a security angle.&nbsp;&nbsp;The services that are likely to be attacked will be on the exposed Internet facing server.&nbsp;&nbsp;If anything nasty happens, then it will (hopefully) happen on the smaller server, leaving the internal boxes still secure.&nbsp;&nbsp;(Assuming that the firewall is set up correctly, and the nastiness on the internet server doesn't include the phrase &quot;root account compromised&quot;...)<br><br>What I was thinking was that the less ports that were open to the internal network, the better.&nbsp;&nbsp;ie, could you really trust the fact that you had FTP ports 20 and 21 leading in to your internal network?&nbsp;&nbsp;What happens when someone discovers yet another buffer overflow root compromise in the FTP server?&nbsp;&nbsp;Your internal network could be left wide open...&nbsp;&nbsp;If you keep exposure to the outside world to a minimum, there's less things to go wrong.<br><br>So, with the servers set up as above, the &quot;mission critical&quot; apps will be secure behind the firewall.&nbsp;&nbsp;The network services will be running on a more exposed server that, if it goes down in a denial of service attack, won't leave the internal servers open to abuse.<br><br>Hope this explains my thinking a little :) <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits
 
Thanks for the info, it will certainly make me think about what is important when I set my system up onto the internet.<br><br> <p> fenris<br><a href=mailto:fenris@hotmail.com>fenris@hotmail.com</a><br><a href= > </a><br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top