On 14.9.2014 20:20, Alan Feuerbacher wrote:
Howdy,Having gotten my systemd booted up, I found that networking is not working. It looks to me like it sort of starts, with these messages: [ OK ] Started Network Service. Starting Network Name Resolution... [ OK ] Started Network Name Resolution. But testing with ping 8.8.8.8 yields the message: PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sending packet: Network is unreachable
The two lines above state that networkd and resolved are running, but that gives nothing about interfaces being up.
Then I tried this: systemctl start dhclient@eth0 Eventually this came back with: A dependency job for [email protected] failed. See 'journalctl -xn' for details.
This means that your interface isn't called eth0. Under systemd, it has a rather odd name and that's mentioned under LFS's Configuring Network page. Examine "ip l" to see what your interface name is as I highly doubt that it's eth0. That needs to be run from a booted system.
Doing the latter command basically just confirmed that networking is not coming up. When I compiled dhcp and executed "systemctl start dhclient@eth0" per the LFS book's instructions for DHCP-4.3.1, I got this (error?) message: Running in chroot, ignoring request. So apparently something is not right even in the compilation stage of dhcp. When I installed the non-systemd LFS last week, I had no issues with networking. For this new systemd LFS I used the same configuration parameters as last week. In particular, "eth0" worked for the name of the network card. Any suggestions will be appreciated. Alan
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
