Re: [SLE] RESOLVED Re: [SLE] dhcpd Doesn't Run

On Wed, 2005-12-28 at 08:17 -0600, Eric Hines wrote:
> 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,

Why do you think you need two separate subnets for you and your wife?

> with the server also being a Samba server for print handling, data
> back ups, etc.

If this server is going to be connected to the internet I highly suggest
-not- keeping important data on it.

> 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.

To be quite honest it will take more than a little tinkering in your
home lan to get the "interesting" jobs. It will require formal training
and practical experience. A CCNA cert from Cisco won't hurt either.

Better to buy a couple of books. O'Reilly has many good books to choose
from. DNS and BIND is very good for learning about DNS. I am sure they
have one for DHCP as well. Better to do a little reading before getting
the wife mad and upset as to why see can't reach the internet or print.

http://www.oreilly.com/

These are a couple of snippets that deal with DHCP and subnets.

http://www.onlamp.com/pub/a/bsd/2003/05/15/FreeBSD_Basics.html
http://www.onlamp.com/pub/a/bsd/2003/04/17/FreeBSD_Basics.html

--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: ConnectComputer Problem
    ... modem plugs into the linksys router and the router connects the internet to ... the server internal nic with a generic setting of 192.168.16.2. ... NICs ... Add the ConnectComputer server's IP address or FQDN to the ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS & NAT
    ... When I have both of the NIC cards active, I get no internet activity ... on the server or any of the clients. ... But this won't fix the main issue that AD will register both NICs as a GC ... After you set this value, you must manually register your publicly available IP addresses for your domain to appear as: Same as parent folder Host "publicIP" DO that by just rt-clicking, new host, leave the hostname blank, and enter the IP of the internal NIC. ...
    (microsoft.public.windows.server.dns)
  • Re: ConnectComputer Problem
    ... name (not one that you use to connect the server from a remote location, ... NICs ... Add the ConnectComputer server's IP address or FQDN to the ... Start Internet Explorer. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 NICs Configuration Problem
    ... the server as Paul envisaged it. ... gateway (to the Internet through the NIC connected to the Sonicwall DMZ ... NICs should not have default gateways configured for both. ... DMZ ports of any firewall, is an alternative path that cause great ...
    (microsoft.public.windows.server.networking)
  • Re: No internet access thru SBS
    ... ANY pc / server connected to the internet should have two NICS. ... Re running internet connection wizard, ...
    (microsoft.public.windows.server.sbs)