I don't see a wireless device in the the PCI or USB lists. I do see a PCI Intel Gigabit Ethernet controller. So does that reading of those utilities match the physical hardware layout?...Ethernet device only?...And it is connected by cable to the router? If so, then forget about wlan0 for this system at this particular time (use that some other time to connect wirelessly). If I guessed rightly that your computer is connected by Ethernet cable to the router, then I would either delete the ifconfig.wlan0 file or edit it to say ONBOOT=no. There. That gets rid of two of the problems listed in post #17.
Next, the eth0 interface doesn't exist probably because its driver is missing. That Intel 82579V Gigabit Ethernet controller requires the e1000e driver (Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support, aka CONFIG_E1000E in the kernel configuration).
See it in the device list for e1000e at cateee.net. It's easy to confirm whether or not that driver was built by searching or "grep"-ing for CONFIG_E1000E in your kernel config file in /boot. It should be set to y or m. Example...
Code:
$ grep CONFIG_E1000E /boot/config-4.6.3-2-CORE2
CONFIG_E1000E=m
CONFIG_E1000E_HWTS=y
If yours is not so, then rebuild the kernel and make it so. If you built the driver as a module, then it will be listed in the output of lsmod as e1000e.
When you reboot that new kernel, look at /etc/udev/rules.d/70-persistent-net.rules. Confirm that your Ethernet device is listed there. Another example...
Code:
$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# net device tg3
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:c0:cc:d1:72", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"
If your Ethernet device is not there, then try running /lib/udev/init-net-rules.sh and check again. If it is there but not named eth0, then either change NAME in the udev rule to eth0 (like in the example) or change the name of the ifconfig.xxxx file in /etc/sysconfig to match NAME in the udev rule. Either way. All of this should get rid of another of the problems listed in post #17.
Lastly, for the dhcp issue, I urge you to use static IP addressing for now. Mostly because it is simple, and simple is what you need now during trouble. Also because DHCP is a BLFS package, and a simple basic LFS system doesn't really require it to connect at this time. To use static IP addressing edit the ifconfig.eth0 file in /etc/sysconfig to say SERVICE=ipv4-static. Also change the IP, GATEWAY, and BROADCAST variables to values compatible with your router. The IP address you choose must be in the range set in the router (open its setup utility and look for the IP range for clients in there). The GATEWAY is the IP address of the router which can be discovered somewhere in the router's setup utility. The BROADCAST is usually the router's IP address with the last octet being 255. Another example...
Code:
$ cat /etc/sysconfig/ifconfig.eth0
ONBOOT=yes
IFACE=eth0
SERVICE=ipv4-static
IP=192.168.0.110
GATEWAY=192.168.0.1
PREFIX=24
BROADCAST=192.168.0.255
That should get rid of the last problem in post #17.
I hope this stuff made sense and worked. Later, after you've established a simple wired static connection, you can install a wireless device and advance to learn about wireless connections and/or dynamic IP addressing. That's more complex and requires some BLFS packages.
