etc/rc.d/ or make bzImage look unfamiliar, I highly recommend going the Easy Way. Not to say that you won't be able to do the Sometimes Cheap way, but time is money and you'll probably end up saving both.
This isn't a generalized guide (check Resources for that), but I think it'll help for (former) Excite@Home and AT&T@Home customers. A little. I hope.
The One Requirement for Either Method:
You'll probably have to add another NIC ($10+), but not much else. If you got the equipment, the time, and most importantly the patience, read on. For those lacking two out of three, but still want to feel vagely
I didn't exactly start from scratch. The box functioned as a SETI@Home cruncher, and everything ran smoothly. The only thing I did was toss in another NIC and enable/change some software.
In a fearsome display of drawing prowess, here's my actual setup:
Slacker) contains two NICs, one running to the cable modem, and the other to a hub which the other computers are connected. Thus the Linux box straddles two networks, the Internet, and the private network. The Internet side requires a real IP address, while the internal network can use any private network address. I use the 192.168.1.X address space for unknown reasons. The other computers are (left to right) Win98, Win98, Win2000.
My config files (with some privacy edits):
alias lines for eth0 and eth1.
If you've just been switched to AT&T Broadband, here's what you'll need to do to get back online. Plug the cable modem into one of your Windows computers, clear out all the networking settings (setting IP to "obtain automatically"), then reboot. Run winipcfg then hit the "more info" button. Write down the new IP address, DNS address, netmask, and gateway. Plug these numbers into the Linux box, the broadcast address is just the IP address with the last three digits as 255 |
Most addresses go into rc.inet1, while the DNS addresses go into resolv.conf.
For specific kernel compilation options, read this section of the IP Masquerade HOW-TO. Really. It won't work if you don't. Ignore the sections about creating a rc.firewall file, we'll let PMFirewall do that.
TIP: Compile the driver for the NICs into the kernel (*) not as a module (M).
Compile, make modules, etc, reboot. Confused? Read the Kernel How-To.
Connect the cable modem to the Linux box if you haven't already.
Everything ok? Try using lynx or ftp on the Linux box, you should be able to get out to The World.
Download PMFirewall and install (very simple), it'll turn on the various IP Masq options you created in the kernel. At this point your box is ready to serve! (After another reboot).
Quick text rundowns from the IP Masq HOW-TO; contains instructions for almost every OS under the sun.
Head for the Network Control Panel. Open up TCP/IP -> NIC properties. Only two changes to make:
Create a hostname (I use the computer name), add the domain (for AT&T customers: attbi.com), then the primary DNS address.
That's it! Reboot the computer and you're done. Most services (FTP, WWW, ICQ, etc) will function normally without any configuration changes. If something pukes, check the IP Masq Apps page.
Follow the first four boxes of the Win2K Networking Page to arrive at the correct dialog box, only two changes to make:
c-123456a.sttln1.wa.home.com, so my POP3/SMTP host is set as mail.sttln1.wa.home.com and my NNTP server is news.sttln1.wa.home.com. Again, look at the yellow sheet of paper for the proper city/state code.
AT&T customers: The POP3/SMTP address is simple, mail.attbi.com