My shiny new lfs system boots up. Mmmmmm, nice. But what of eth0?

more /etc/sysconfig/network-devices/ifconfig.eth0
DEVICE=eth0
BOOTPROTO=yes
ONBOOT=yes
NETMASK=255.255.255.0
BROADCAST=192.168.1.255


I've compiled in the PCMCIA cardbus support (it's a Netgear FA411 for which a drivers included in the kernel). But when I boot into runlevel 3, it complains that the ifconfig.eth0 script is incomplete. Am I missing something in the ifconfig.eth0 file?

Anyone?

Bert

BOOTPROTO=yes

yes is not a valid protocol is it?!

Sorry, that's meant to read

BOOTPROTO=dhcp

Any ideas?

More details ...

It says there's a missing IP variable. I can't specify the IP address though because it uses DHCP to get the address from the server through the cable modem ...

Does anyone know where I can get a full list of the entries for this file?

Thanks

Bert

I seem to recall having this same problem when I made my LFS. I just copied the same file from my host distro and it worked fine. Sort of cheating, I know, but what you gonna do?

That's exactly what I did. I'm starting to think that maybe the problems elsewhere ... ?

do you need "DEVICE=eth0"? I mean, it's int the ifconfig.eth0 file, shouldn't that set what device it is for you?

what do you have in /tec/sysconfig/network?

you should set the default gateway there, which will point to your cabel router. here's mine:

HOSTNAME=lfs2
GATEWAY=192.168.1.1
GATEWAY_IF=eth0

My actual ifcfg-eth0 file on the redhat system has very litle - no IP address at all.
Either way I tried yours and mine but no luck.
When I try

ifconfig eth0 up

I get a no device found error

./network eth0 start

Does nothing!

Should I run the MAKEDEV scritp to (re)generate the /dev drectory?

Thanks for the help

Bert

have you installed the dhcp client on your box? there is a section in blfs if you haven't.

I don't know if i read your reply wrong... but I gave you the /etc/sysconfig/network file, NOT the /etc/sysconfig/network-devices/ifconfig.eth0 file.

I think that if you are getting "device not found" then you might not have the correct drivers enabled in the kernel. What card/driver are you using?

You should not need to use the MAKEDEV script, you did that when you built LFS, right?

EDIT:

here's what I had in /etc/sysconfig/network-devices/ifconfig.eth0 when I used dhcp:
ONBOOT=yes
DHCP_PROG=/usr/sbin/dhcpcd
DHCP_START="-t 15"
DHCP_STOP=-"-k"

#############################

although, I think that the "-k" option gave me some problems

That'll be it. No dhcp client installed. The lfs chapter gave the impression that it wasn't needed but i guess they were only talking about setting up machines with static IP addresses in that chapter. (Does anyone set up machines with static IPs any more?).

Thanks for your help.
Bert

hehe... sure, I try not to use dhcp AT ALL. I like just knowing the ip address, without it changing on me all the time..... really nice if you want to use the box as a server of some type.

I've also read that it's a little bit more unsecrure if you use dhcp...

anywase, have fun w/ your new LFS....

-Adam

Depending who your provider is, dhcp is kind of a misnomer. I use shaw cable in Canada and they give you an IP, and only change them once a month or so to shake things up.

Perhaps set up your IP as static, and run dhcp once to get your new IP if they change it on you.

The reason I said "Does anyone install with static IP" was talking about end-user machines, not servers of course (unless it's edonkey ). It comes back to the old IPv4 and IPv6 problem.

DHCP is the market's answer to IPv4. Just like we hoped solar-powered cars might be the answer to oil shortages. DHCP is good though - as an end user, I'd prefer it because I'm a moving target for wouldbe miscreants. It might not be secure for a determined attacker but there's usually a firewall of some description sitting between you and the cloud.

The length of the lease on cable IP addresses must depend on traffic. There's really no other way to do it. And if you think about it, not having a static IP always makes sense if you're not running a server.

I still think that static is better for your lan. Since you know the address of everything, you can easilly get to any machine.... you might need to access boxes that aren't servers. you can then easilly set up hosts so that you don't have to remember all of the ip's w/out needing a dns server.

Also, If you have a large network, it would be too easy for somebody to come along and plug their laptop into the network and start crack'n around... plus, it would make it a lot harder to determine where the intruder plugged in.

I don't know... It's just my preference I guess.