On 9/23/18 6:34 PM, John Le Brasseur wrote: > Hi Pierre. > I don't know if attachments are allowed on this forum but I have attached > three screenshots: > startup screen, > ls-l_sys_class_net and > ip_link_list > > I am not sure of the answers to your other questions but i did not use systemd > and there is no /etc/udev/rules.d/70-persistent-net.rules file at all. Only > 55- ..., 81- ... and 83- ... > I checked in my LFS 8.2 build and found > a /etc/udev/rules.d/70-persistent-net.rules file. > I typed it identically into my LFS 8.3 build, with no visible success. > Copy of net-rules also attached. > Iv'e just got this feeling it is the kernel build but do not know how to > tackle the problem itself.(or Iv'e forgotten) >
This is not a kernel problem, since the NIC's are recognized (but see below). They are given names of the form enp0sx, with x=3, 8, 10. But it seems that your startup files bring them up, although only messages concerning IPV6 are shown. Maybe IPV4 is not configured? Is IPV4 enabled in the kernel? If IPV4 is configured, the only things that can be wrong are the IP addresses. To see the IP addresses, the command is "ip addr list". The NIC connected to NAT should have an address starting with 10.0.2. Then to test what you have as a gateway (normally 10.0.2.2), the command is "ip route list". It should return something like "default via 10.0.2.2 blah" Test that you can reach it with "ping 10.0.2.2" (I hope it works with virtualbox, it does with qemu). Then verify that /etc/resolv.conf has "nameserver 10.0.2.3" That's all I can think of Pierre -- 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
