On 20.10.2014 13:05, Googlemail wrote:
On Mon, 20 Oct 2014 12:37:52 +0300
Andrei Banu <[email protected]> wrote:
On 20.10.2014 12:32, Armin K. wrote:
On 10/20/2014 11:28 AM, Andrei Banu wrote:
On 20.10.2014 11:49, Pierre Labastie wrote:
Le 20/10/2014 10:09, Andrei Banu a écrit :
[...]
As for eth0, I believe I should start a new thread.
Maybe not:
What does "ip link list" return? For me, it does something like:
----------------
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
mode DEFAULT group default qlen 1000
link/ether 00:10:18:97:be:62 brd ff:ff:ff:ff:ff:ff
----------------
After the "2:", there is the name of the card as found by the kernel.
If it is something like eth126, it means the
70-persistent-net.rules file in /etc/udev/rules.d should be removed
(the network card is consistently named eth0 in the initramfs phase,
and then you get to real boot, the name is already taken, so that the
system uses another one).
If it is anything else, I suggest you use this name in
/etc/sysconfig/ifconfig.<interface name>. You could also write udev
rules, but it is not worth the trouble...
Pierre
Hi,
Besides the 1. loopback, it shows this:
2. sit0: <NOARP> MTU 1480 qdisc nop state DOWN mode DEFAULT group DEFAULT
link/sit 0.0.0.0 brd 0.0.0.0
Although it didn't look right, I tried to "raise" it with IP
192.168.0.110 to see what
happens. ifconfig shows this:
sit0
Link encap: IPv6-in-IPv4
inet addr: 192.168.0.110 netmask...
NOARP MTU: 1480 Metric: 1
So from what I read this is just a pseudo interface for tunneling IPv6
through IPv4.
I obviously can't ping anything ("Network is unreachable").
Thanks,
Andrei Banu
I believe that sit0 is just an IPv6 tunnel, not an actual interface. You
are most likely missing a driver for your network card in the kernel.
Yes, that's true regarding sit0. So I guess I need to recompile the
kernel. But what should I do differently?
Kind regards!
Use dmesg to check on your build host which driver your network card uses.
Write it down. Then configure it into your LFS kernel. Some card drivers have
very similar names; I had exactly the same experience as you when I
accidentally specified the wrong driver.
Well, the problem is that I have not specified ANY driver. Where should
I specify it? In the menuconfig?
Thanks!
--
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
