David Whitney wrote:
> Gentlemen,
>
> Thank you for your replies. Since the the URL I posted in my original
> email apparently is not working, I will recap what I have done for my
> system.
>
> 1) Completed a successful build of CLFS for the 586 architecture
> using this guide:
> http://cross-lfs.org/files/BOOK/1.0.0/CLFS-1.0.0-x86.html
>
> 2) Applied certain BLFS extensions to my CLFS build. The one that is
> relevant to DHCP issue can be referenced here:
> http://www.linuxfromscratch.org/blfs/view/stable/connect/dhcp.html
>
> 3) Thanks to some wonderful help I received a couple days ago, I
> installed net-tools-1.60:
> http://www.linuxfromscratch.org/blfs/view/stable/basicnet/net-tools.html
>
> I have installed DHCP-3.05 so that I could have access to 'dhclient'.
> On a separate incarnation of my CLFS system, I tried using
> DHCPCD-2.0.8. In both cases, I was unable to obtain a DHCP IP lease
> from my router.
>
> My router is working fine, I have tested it with other systems, and I
> have tested the CAT-5 cable I am using to connect my CLFS system.
>
> I have verified that NIC chip-set on CLFS system is functioning
> properly (I tested previously with Fedora Core 5).
>
> Here are the outputs I received when issuing various commands under
> the CLFS:
>
> When I run "lspci | grep -i ethernet":
> 00:12.0 Ethernet controller: Intel Corporation 8255xER/82551IT Fast
> Ethernet Controller (rev 10)
>
> When I run "dmesg | grep eth0":
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:59:02:42:EA, IRQ 5.
>
> When I run "lsmod":
> Module Size Used by
> eepro100 23824 0
> mii 4224 1 eepro100
> evdev 6912 0
> apm 15468 0
> rtc 8628 0
>
> I have tried to configure the eth0 interface manually, issuing the
> following command:
> ifconfig eth0 192.168.1.104 <http://192.168.1.104> netmask
> 255.255.255.0 <http://255.255.255.0> broadcast 192.168.1.255
> <http://192.168.1.255> up
>
> However, when I attempt to ping my router (at 192.168.1.1
> <http://192.168.1.1>), I receive messages that the "Destination Host
> (is) Unreachable".
>
> Ultimately, my system requires DHCP support. I cannot use/depend on a
> static IP setup. Similar systems to which I am building will be
> shipped across the World to various clients who are running their own
> networks (or maybe none at all), and for which I have no control
> over. If they do not support DHCP, well then I will have to cross
> that bridge when the time comes.
>
> I can testify that I am not a networking guru, but I do know enough to
> configure my router and setup my own little LAN in my home. There is
> nothing wrong with a h/w. For the s/w, I followed the instructions
> in the CLFS guide and the instructions within the BLFS guide. I have
> enabled or "moduled" the ying-yang of pretty much every network option
> in the Kernel configuration (which is overkill, but...). My network
> device is detected, the appropriate kernel module is loaded, ifconfig
> (from net-tools) seems to be able to configure the eth0 interface,
> however I cannot even ping my router at 192.168.1.1 <http://192.168.1.1>.
>
> I do have a question about /etc/resolv.conf with DHCP. The CLFS guide
> mentions about setting it up as appropriate for one's local area
> network. In my case, I have the file empty because I knew I was going
> to use DHCP. Was this a bad choice? Or should I insert "search
> localdomain"?
>
> As for iptables, firewalls, etc, if it is something that is not
> discussed in the CLFS or BLFS sections I followed, then I probably do
> not have it setup/configured/installed on my system. If you have any
> advice, concerning these items, please be explicit with your
> instructions.
>
> Anyhow, here's the correct URL at LinuxQuestions.org:
> http://www.linuxquestions.org/questions/linux-newbie-8/cannot-acquire-dhcp-ip-address-from-router-596148/#post2945582
>
> <http://www.linuxquestions.org/questions/linux-newbie-8/cannot-acquire-dhcp-ip-address-from-router-596148/#post2945582>
>
> Dave
>
>
>
>
>
> On Nov 1, 2007 4:42 PM, Joe Ciccone <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
> > David Whitney wrote:
> > >
> > >
> > > P.S . I have tried using a static-IP configuration as documented in
> > > CLFS, however that does not function either.
> >
> > For starters, assuming that you setup the static IP properly, correct
> > ip/netmask/gateway/dns. I'd check your network cable / hardware. I've
> > seen nics completely refuse to communicate after a power surge.
> >
> > _______________________________________________
> > Clfs-support mailing list
> > [email protected]
> <mailto:[email protected]>
> > http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
> >
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Clfs-support mailing list
> [email protected]
> http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
>
Dave,
Did you follow BLFS or CBLFS?? http://cblfs.cross-lfs.org??
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
