Recommend a good OS/software for a server...

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Which variation of *nix would be good for a server that I wanted to act as a router/firewall, file server, web server. Also what programs are good for the routing/firewall aspect?

Also will a wireless nic in this server show up to other wireless nics as an access point and not 'ad-hoc'?
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
Whichever one you're the most comfortable with since you have to maintain and secure it. If you're just starting out I would suggest Debian, the main repository should have just about any package you could want.

Also what programs are good for the routing/firewall aspect?

As few as possible, you want to keep the ways into the box as minimal as possible.
 

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Originally posted by: SleepWalkerX
Check out m0n0wall. Its usually the most referred firewall/router solution. Its FreeBSD based, haven't personally used it though.


m0nowall looks good for a just a router/firewall, but it doesnt appear that it can be used to do other tasks as well. I'd like a linux OS that I can setup the following:
- Router/firewall
- Print server
- File server
- Web server (apache/php/mysql)
- Possibly a PVR

Can anyone recommend a good distro and/or guides for setting this up? (for someone who has little experience with linux).
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
Any of them will do fine, you'll probably end up installing and configuring the same software on any distribution.
 

BurnItDwn

Lifer
Oct 10, 1999
26,353
1,862
126
I can't answer anything about the wireless, as I have never used wireless before. (I have no need for it)

I personally use Slackware Linux on my server.
I have used Mandrake and Redhad in the past for the same purpose.
I have played with OpenBSD and FreeBSD, but my knowledge is VERY limmited with them.

My server is my router/firewall
I also use it as my ftp server (proftpd), web server (apache), local file server (samba),
I used to use it as a DB server, but I no longer need that functionality, so I don't have PostrgreSQL on it (since I switched distros)

I also use it for some non-server type things
-- I use it to connect to IRC (I run BitchX on it for that, I connect to it from my other PC in a putty ssh window. Been using BitchX for a long time now, maybe 5 years or so, and don't have any desire to switch to any other IRC client)
-- I run X.org on it with fluxbox ... it's sometimes handy just to have as a websurfing box.

I'm running a 1.8ghz Celeron with 384MB of ram. It's more than enough for what I use it for now.
If I didn't care about getting X to work, I would probably be OK with a P133 and 64MB of ram (well, except maybe not due to possible issues with drives > 137GB)


Some will say Linux Distro "?????" is the best, others will say FreeBSD, others NetBSD, and yet others OpenBSD.

You should first decide,
Do you want to use "iptables", "netfilter" or "pf" for your firewalling and nat?

for Web Server, apache runs on everything
For File Server, Samba works great in Linux (easy as pie to set up with SWAT), I hear it works equally well on *BSD
For Print Server, Samba does that too ..
For PVR, look up "mythPC" It was designed for Linux, but there may be ports to BSD's ... I don't know


You're gonna have to just pick something and stick with it ... or you're going to really need to reseach quite a bit.
There are many good options here, and everyone seems to think theirs is the best.

OpenBSD is kinda picky when it comes to hardware, but it runs with most stuff out there. (Linux is the least picky about hardware, but the quality of the drivers is not always top notch)

Personally, I would avoid redhat (or Fedora as they call it now), I find they bloat things up a bit too much. They try to make everything too "idiot friendly" and they generally leave lots of things "open" that generally, you don't want to leave open.

I'd go with Slackware, ohh wait, I already did :) (Otherwise Gentoo, Debian and, Ubuntu seem to be pretty popular these days, so support would likely be plentifull)
My second choice would be OpenBSD, it really appeals to me a lot, I'll eventually toss together a BSD box just for kicks ... (assuming you don't need the PVR, or you find something that works in OpenBSD for that purpose)

 

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Thanks for all the info BurnItDwn. I'm thinking of using Ubuntu as I've used it in the past before on Desktops and Laptops and really liked it. Whats the difference between iptables, netfilter, and pf? Do they all basically do the same thing? Can they do bandwidth limiting?
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
iptables and netfilter can be used interchangably but technically they are different things, netfilter is the name of the packet filtering system in the Linux kernel and iptables is the userland interface for it's administration.

pf is the packet filter for OpenBSD and I think ported to NetBSD. They do the same things but they work and are setup differently.

bandwidth limiting on Linux was a PITA the last time I looked at it, it's possible but it's not fun.
 

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Originally posted by: Nothinman
iptables and netfilter can be used interchangably but technically they are different things, netfilter is the name of the packet filtering system in the Linux kernel and iptables is the userland interface for it's administration.

pf is the packet filter for OpenBSD and I think ported to NetBSD. They do the same things but they work and are setup differently.

bandwidth limiting on Linux was a PITA the last time I looked at it, it's possible but it's not fun.

What makes it so much harder to do BW limiting in linux? Is it a lot easier in BSD?
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: Nothinman
iptables and netfilter can be used interchangably but technically they are different things, netfilter is the name of the packet filtering system in the Linux kernel and iptables is the userland interface for it's administration.

pf is the packet filter for OpenBSD and I think ported to NetBSD. They do the same things but they work and are setup differently.

bandwidth limiting on Linux was a PITA the last time I looked at it, it's possible but it's not fun.

All 4 major BSDs use PF as at least one option.

Bandwidth limitting in OpenBSD shouldn't be too difficult, but I haven't read that section of the manual in a while and I've never played with it.

OpenBSD has the best wireless support out there next to Windows, and even works as an access point with most of the supported hardware.

Samba works just fine

A patched apache comes installed with a full OpenBSD install. A number of smaller web servers are available as ports. Just don't allow access to these from the interweb (no matter which system you choose). :p

If you need BGP or OSPF it's there.
 

BurnItDwn

Lifer
Oct 10, 1999
26,353
1,862
126
Originally posted by: n0cmonkey
Originally posted by: BurnItDwn
OpenBSD is kinda picky when it comes to hardware, but it runs with most stuff out there.

Picky how?

I said "kinda picky." :)

I should have specified that this applies to i386 only.

It doesn't like to enable the second CPU in a decent number of SMP systems. (Though I know that isn't nearly as true as it used to be)

No ACPI support, and no Firewire (or is my info out of date?)

various sound cards unsupported (not that it matters for a server though ... hehehe)


I will agree that in general, the hardware support is good, but it's not quite perfect.

:wq
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: BurnItDwn
I said "kinda picky." :)

I should have specified that this applies to i386 only.

It doesn't like to enable the second CPU in a decent number of SMP systems. (Though I know that isn't nearly as true as it used to be)

Just about any system with a proper MPBIOS should work, although I'm sure there are exceptions. ;)

No ACPI support, and no Firewire (or is my info out of date?)

It's correct. ACPI is an ongoing project though, and firewire's generally on one or two developers' lists of things to do.

:)