At 12/28/05 06:37, you wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2005-12-27 at 21:21 -0600, Eric Hines wrote:
Added both NICs to the one (which was the NIC facing the Internet) already in DHCPD_INTERFACE and restarted dhcpd. rc.dhcpd.log confirms that the daemon now is listening on all three NICs. That works like a champ.
But... do you really need a dhcpd _server_ in the interface on the internet side?
I think so. What I'm doing is teaching myself Linux and Samba, and getting this setup to work is an exercise along that path, and teaching me a bit about DHCP and DNS, also (I've still not got name resolution working correctly within the LAN, but that's another problem for me to work). If my dhcpd.conf file came through in this thread, you were able to see that I have my printer right up there with the one NIC facing the Net--that's a terrible place to stick a printer. However, until I get around to figuring out how to put the printer on one subnet and have it available to the other subnet, this is where it needs to be. I can get away with this arrangement, for a bit, because the whole shebang sits behind a separate router/switch that's my firewall. The ultimate configuration, though, after I've learned enough to get really dangerous, is to have just the one NIC (and server) facing the NET and handling the various services--mail, browsing, etc--for the two subnets, one of which will be for my wife and the other for me, with the server also being a Samba server for print handling, data back ups, etc. And for the sake of this (probably unnecessarily, but it's an exercise for the student), I want the server to do the DHCP and DNS stuff for the LAN, also. This is overkill for a dinky little LAN, but I'm also hoping this will give me enough skills that I can leave my current job and go do something interesting. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell