Date: Thu, 12 Aug 2004 12:24:56 -0400 (GMT-04:00) From: "Hakim Z. Singhji" <hakim.singhji@earthlink.net> To: Bill Moran <wmoran@potentialtech.com> Cc: freebsd-questions@freebsd.org Subject: Re: DHCP and rc Questions For FreeBSD 4.10??? Message-ID: <23625943.1092327896715.JavaMail.root@skeeter.psp.pas.earthlink.net>
next in thread | raw e-mail | index | archive | help
>Who manages your DHCP server? The config I described has worked in >every configuration I've ever dealt with (and that's quite a few) so >there is definately something external causing the problem. I have an Earthlink Highspeed Cable account w/ DHCP Server >Did you install a packet filter when you set this box up? Yes, however I turned firewall to [firewall_enable="NO"] and commented all firewall entries in the rc.conf file. >If you don't have a DHCP _server_ on your network, then the DHCP _client_ >will not be able to to its job. Earthlink should provide a DHCP server, when I had my standalone redhat box it was configured and I was also receiving DNS as well through earthlink. What do you suggest I do? -----Original Message----- From: Bill Moran <wmoran@potentialtech.com> Sent: Aug 12, 2004 11:45 AM To: "Hakim Z. Singhji" <hakim.singhji@earthlink.net> Cc: freebsd-questions@freebsd.org Subject: Re: DHCP and rc Questions For FreeBSD 4.10??? "Hakim Z. Singhji" <hakim.singhji@earthlink.net> wrote: > Bill & FreeBSD-Questions, > > This configuration is not as intuitive as I thought it would be. > In /etc/rc.conf I added the following strings: > > ############################ > network_interfaces="lo0 dc0" > ifconfig_dc0="DHCP" > ############################ > > "Then I deleted the entries in dhclient.conf and relied on the > default. I started the daemon by [dhclient dc0] and it > seemed to be processing. However, that was all that > happened. When I [ifconfig dc0] I get this return:" > > ############################# > root@redgate% ifconfig dc0 > dc0 flags = 8843<UP, BROADCAST, RUNNING, SIMPLEX, > MULTICAST> MTU 1500 > inet6 fe:80::2c0:f0ff:fe79:4ab7%dc0 prefixlen 64 scopeid 0x1 > inet 0.0.0.0 net mask 0xff000000 broadcast 255.255.255.255 > ether 00:01:02:c3:40:1a > media Ethernet auto select (100base<full duplex>) > status: active > ############################### > > "Then I tried to ping a host..." You've gone too far ... there's not use trying to ping anything if you obviously didn't get a DHCP address. Who manages your DHCP server? The config I described has worked in every configuration I've ever dealt with (and that's quite a few) so there is definately something external causing the problem. Did you install a packet filter when you set this box up? Look through /etc/rc.conf for anything related to "firewall". Turn off all firewall rules while you're setting things up. Once it works, you can start turning security stuff like that back on. > I was reading Greg Lehey's book "The Complete > FreeBSD" which happens to have more information on > DHCP,DNS, BIND than "Absolute BSD" by Michael Lucas and > Greg says that in order for dhcp to work you must start dhcpd, > am I reading this correctly. I assumed that dhcpd would provide > DHCP for the private network (in my case), I did not think that > my default gateway would rely on dhcpd in order to function. DHCP only works if there is a DHCP server. DO NOT run more than 1 DHPC server on a single network or everything is likely to go to hell. Most cheesy "internet routers" that people buy include a DHCP server. If you provide more information about what your network setup is, we can tell you whether you need a DHCP server or not. But the simple answer is: DHCP won't work unless there is a DHCP server somewhere. > Now I have 2 questions: > *must I configure dhcpd now? Maybe not. Does the network you're plugging in to require DHCP? > *must I configure dns (resolv.conf, named, etc.)? No. If you don't mind using IP addresses for everything. If you want to be able to use hostnames (such as www.yahoo.com) then you need DNS. > *does DHCP rely on the two configurations list above to data? Huh? The two lines I provided are enough to configure FreeBSD to be a DHCP _client_. Any additional configuration is just tweaking its behaviour and and is almost never required. If you don't have a DHCP _server_ on your network, then the DHCP _client_ will not be able to to its job. If you have a very small network (how many computers are here anyway?) a DHCP server is probably more work than it's worth. If you are plugged into a larger network (such a the Internet through an ISP) then either a) your ISP's DHCP isn't working right or b) your ISP isn't using DHCP or c) your ISP is doing something to enforce security, such as registering MAC addresses, and you aren't registered correctly or d) something bizaar that I've never seen before. Again, if you could provide some information on how you're trying to set things up, we could provide less general answers. -- Bill Moran Potential Technologies http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23625943.1092327896715.JavaMail.root>