I began configuring a 320gb PIII server for personal webhosting and later awas given a 30gb AMD 900mhz box w/2 eth NICs. I would prefer to put the 30gb box up front as the server that connects directly to internet instead of the PIII.
1) Do i turn off all the server settings on PIII to make it machine2?
2) Can machine1 30gb box - share machine2's hdd space resources? How?
Goals is to turn machine-1 into gateway, router, firewall, web server and have machine2 be dns server that stores web pages for machine1 to serve up?
Another ques. slackware gateway/router/firewall box has to run all the time so that computers in its network can have access to internet - right?

3) I have 4 more computers that will be connected to one another and the internet thru machine1. Machine3 and 4 are also slackware, Machine5 is windowsXP, Machine6 wireless mac laptop.
4) ISP is Dhcp Dsl with 4 port 2wire gateway 1800HG which is complicated to configure.
5) I need a hub, can you please suggest an inexpensive one?
6) I need a linux compatible printer - mostly for b&w text.. suggestions please cto (cost to own) is a concern - budget is non-existent

Appreciate any and all input... i have already done alot of research and would like to post, the progress of this effort. BTW this is a personal lab project. Thanks

Hi,

A lot to handle with one thread!

The 'AMD' would work as a server with no problems. With that many machines on the LAN you really don't need a dedicated 'DNS'. You could setup the '/etc/hosts' files to reflect the needs. If your LAN is <10 then a 'hosts' based system is easier.
I use static IP assignments except for quests which are predefined by a table.

As for sharing the space between systems then I suggest that you setup 'NFS'. Since you want to service M$ machines then 'samba' would be necessary. As for the MAC, will you need 'atalk'?

You do not need to setup a machine as a router. Since you will be using 'NAT' on the server along with masquerading you will find the firewall on your server along with the 'modem' you will in effect will have a 'DMZ'. The cheapness of a wireless ap will enhance your network and provide routing if indeed you feel that is necessary.

If you are going to have 24/7 for machines then of course the server would be up for Internet access.

Why a hub? A switch would be better if all you want is to common service. Cheaper! Just do a search on 'NewEgg', 'TigerDirect' or even 'Cosco' to find a switch. I like the 3com units, cheap and reliable. You can get them in the 4/8/16 port units at a fair price.

If you have the spare $$, then look at getting UPS for the server. It will save you some headaches if your power is not reliable.

I like the 'Brother' HL-2xxx series B/W laser printers. I don't use MTF units because if one function fails then the peripheral is useless. I've purchased the HL-2040 <$60 and the networked unit for <$80. Depending on your printer loads then a networked unit could be located local to your users rather than at the server or a workstation.

1. It depends on what you call server settings. Any app which will run exclusively by the PII server can be removed from the PIII. From the looks of it the PIII server will now be your dns and nas so you primarily need dns, nfs and samba (assuming you want to share files with you win/mac pcs as well).

2. The PIII server will be your nas so setup nfs. You can then mount the shared directory as a local file system on the PII server.

2b. Right. Any gateway has to run all the time for other machines to access. You will need both machines running all the time. One to route your traffic and one for your dns request.

5. Any old hub will do. I picked up a 24 port dlink on ebay for $20 and it works like a charm. If you want 1Gig prepare to spend a bit more.

6. I have great experience with HP. IMO they have the best linux support (unofficially). Shop around for a printer with the features you need and within your budget. The check their compatability site for linux support. I got LaserJet M1522nf for a very low price, which is a network printer and fully supported on linux.

Thanks so much for your responsive guidance. Have to love ebay

onebuck, *Noticed 1 of 4 ports on 2wire gateway went bad, will i need to replace it too? i have dhcp isp that is y i was setting up the dhcpd ddns. Good learning exercise, once i learn then i can go the easier way. Give me a chance to use your firewall generator.

tux_dude these are the server settings i had initially activated on PIII,320gb startup: ATalk, Apache, msqld, perl, php, dhcpd, bind and ddns,sshd

The AMD 900 only has 30gb. I want to put the AMD upfront for guest access. How will AMD access and use PIII's hdd. I want to put a slackware mirror and web pages on PIII.


So I add NFS to Pentium III Machine only? Then i can put the slackware mirror and other websites on PIII NFS?

Can I please, get partition scheme suggestion specific to the proposed usage? I am so excited. Thanks

Here's how I would set it up:
AMD box:
dhcpd, apache

PIII box
ATalk, mysql(IMO this should stay on the faster box), nfsd, samba, bind, ddns

Both
Perl and php (for running local scripts), sshd

Personally I would leave the web on the faster box and have the slower one just as a gateway. Then again, I am not a fan of using full blown PCs as gateways. That's what routers are for.

NFS allows you to mount a share directory as a local file system. I would be as if you have another drive to the AMD box. Add the mirror and websites to the PIII box and mount it on /var/www on the AMD box. Do for details.

I run a small home LAN. I have 5 machines. Two are modern 1 gigabit machines, one is a 350 MHz PII, one is a 400 MHz K6-III+, and the fifth is a seldom used 486. I use several virtual machines, which are networked into the system. I have a Linksys WRT54GL 1.1 router running DD-WRT firmware with a built-in 4-port 10/100 Mbps switch, and a D-Link DGS-2205 5-port gigabit switch.

I do not use DHCP with my LAN. I use an /etc/hosts file. As my network grew slowly through the years, a static IP approach made sense in the early days. I found no compelling reason to change when a simple text file edit sufficed. I run a script through my rc.local that keeps the hosts file in sync with my primary production box.

I do not mess with DNS server software and you probably do not want that either. I think what you actually want is DNS caching, which I use here. For DNS caching I use dnsmasq, which is provided with the stock Slackware. I use the second hosts file feature of dnsmasq to create a simple but effective ad blocker. I use this site to create a basic ad blocking list for dnsmasq.

With respect to swapping your server/gateway machines, the important element is that all other machines know the IP address of the server/gateway machine. In Slackware that is accomplished in the rc.inet1.conf file.

You can share hard drive space. I find NFS much easier to configure than Samba and works great between Linux-based machines. I use Samba for my Windows (real and virtual) machines. Both network systems run fine concurrently.

With respect to firewalls, I run an iptables firewall on all of my Linux-based systems. I use a firewall in the router. I use DD-WRT in my router. To build some firewall scripts for your Slackware computers, consider using Eric Hameleer's Easy Firewall Generator.

You don't need to run your server/gateway 24/7. If the server/gateway supports wake-on-lan, you could configure the box to awaken when needed. If you have little control when other family members use their computers then you probably want to keep the box running 24/7. Expect to pay more with the monthly electric bill.

For your wireless Mac you will want a wireless router. If you use one of your machines as a router then you'll need a wireless network card.

Most set-top routers these days come with a built-in 4-port switch, which by your description will be insufficient. Recently I bought a D-Link switch. I'm happy with the switch. Like me, you could use the switch for your faster machines and use the older 10/100 Mbps ports on the router for the older computers.

You could configure your server/gateway as a router/NAT server, but you at least need a switch. You mentioned a hub, but for the low prices these days adding a touch of hardware intelligence with a switch will provide a nice return on investment.

Oh, remember too that if you are going to connect all of these machines with CAT-5, you'll need to string cable. You can buy pre-made cables in any office store or make your own, but if the machines are in different rooms then you'll need to fish cable through the walls as well as add connector plates.

Hi,

Your LAN will use the Class 'C' assignments unless you have a domain. Most common use is '192.168.xxx.xxx' but you also have the '10.10..'. Your ISP provides a IP to the modem and you can then setup the local in the class c range. KISS!

If you have failures on 1 of the 4 then future failures are very possible. You can use static IP assignments for your LAN. I agree with woodsman about using the 'hosts' files for name resolving. A lot easier.

I suggest that you use 'Easy Firewall Generator - Alien_Bob's Slackware® Adaptation' as it's simple yet reliable.

As for partition schemes, you can do a search here on LQ as this subject has been covered often in the past.

If you are short on budget then the wake on LAN would suffice (your standby power is lower but there) but the amount for a 24/7 server is not that much more. Plus there would be some latency for any users with WOL.

The above link and others can be found at 'Slackware-Links'. More than just Slackware® links!

Roswell 8 port 10/100 switch arrived.
Connected PC 1 server Eth0 192.168.1.101 to 2wire Gateway
Connected Eth1 192.168.1.1 to Switch

I do have Domanin Names I am iching to build on. MY ISP provides PPoE dynamic ip. Reasoning behind setting up DHCPD/DDNS to update dynamic IP challenge. I know about noip and others but i can't afford to pay more and want to learn howto setup just using software available with slackware.

Have been trying to setup the host files:
#domain.name is the same as workgroup? So i just use the same one with all machines to identify the network each machine belongs to. Right?

/etc/hosts
127.0.0.1 localhost
192.168.1.101 pc1.domain.net pc1 (pc1 has eth0 192.168.1.101 eth1 192.168.1.1)
192.168.1.69 pc2.samedomain.net pc2
192.168.1.70 pc3.samedomain.net pc3
192.168.1.65 pc4.samedomain.net pc4 (windows XP)
192.168.1.64 Wireless Laptop

*( PC 1 has internet access only if i connect switch to 2wire Gateway. Masquerading can't not establish a listening socket the address is already in use.)
I can access web server using 192.168.1.101 from all local Computers only. So this i am stuck at this point.

/etc/HOSTNAME (for ea. machine follows this syntax):
pc1.domainname.net

/etc/host.conf
order hosts, bind
multi on (same thing for all the machines. is this right? But i think this is for DNS setup? I am still reading folks And it takes me quite a few reads before i get the picture. Its an old Slackware unleashed + online slackbook)

Right now ALL pc have internet connection thru switch connected to 2wire 1800HG Router that provides Static Lan IPs that i don't understand howto change. I have to connect Switch to 2wire gateway. Masquerade can't establish a socket to listen on because the address is already in use.
I don't understand how masquerade will update my dynamic address to webserver? I am stuck at this point. The more i read the more confused i get by all the the different options.

tux_dude what would be the alternative to using PC as a gateway? Given I have a 2wire 1800HG. Right now when i try to setup /etc/resolv.conf for dnsmasq the file gets over written. As of yet i can only access index.html using the machine add locally. You state preference for using the 2wire modem/router, so what would be the setup for this option?