If you can find an old machine, or have one thats always on, you can setup a DHCP server on any machine on your network providing its in the same subnet. I'm running a Linux router /w with dhcp client to telus, the router then serves out 10.0.0.x ip's on my home network.
I'm going to run a trimed down linux soon, to see how it works on a 386 and a 486. heh its nice to ssh the router by typing "ssh 10.1" hmm a 386 might be fast enough...I'm not sure, I've used it as a dailup router back in the *shiver* 56k days. I recomend people try the Linux From Scratch approach to learning Linux. From there you can get an idea as to what makes up Linux and how to customize it to do what you want. I figure a router can be built on less than 4MB hd space /w DHCP daemon and client. Maybe on one floppy. I don't know. If you're interested I could help you set something like that up. There's so much to learn, like puting Linux on this old laptop... ----- Original Message ----- From: "Shane&Lisa" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 19, 2002 10:51 PM Subject: Re: (clug-talk) Me loves cable... > Well this is the thing... > Because of attaching the box to the router's dhcp i won't know what local > address it'll get (I think...) > Perhaps the router hands them out the same way all the time. > > Every time I tinker so far I get locked out of the router... > > Networking is fun... > > Shane > > > Cameron Nikitiuk wrote: > > > Most of the retail (linksys, d-stink, smc, etc.) routers out there do allow > > port forwarding as well as DHC, firewall, NAT, etc. You could set it up to > > pass port 80 requests to the machine (192.186.2.?) that you are hosting your > > site on. This is commonly referred to a DMZ as well. Important thing to > > remember is to lock down that machine, especially if it is on your LAN, > > behind the firewall. Lock it up tight so no one can use that machine to > > attack your LAN. > > > > -----Original Message----- > > From: Shane Clements [mailto:[EMAIL PROTECTED]] > > Sent: August 19, 2002 12:55 PM > > To: [EMAIL PROTECTED] > > Subject: (clug-talk) Me loves cable... > > > > >>If you want to manually setup each > > >>computers ip address (why?) you can still use dhcp, but setup your > > >>dhcp.conf file to only request dns from the dhcp server. > > > > >>Just curious why you aren't using DHCP though? > > > > Well the short answer is 'cause I'm not sure what I'm doing...:^) > > > > Actually (perhaps I'm not going about it the right way...) I want to > > eventually > > run a DNS server and Apache to host my own site. I have a site hosted by > > l33t.ca. But to learn more I thought I'd try it my own self. > > > > What I thought might work was to have the SMC box port forward requests > > from 'mysite.com' to one of the boxes behind it. > > > > I thought that for stuff like that (ftp, http, openshell etc...) there would > > have to be fixed addresses at each machine. > > > > Perhaps no... > > > > Shane >
