Installing NIC & setting DHCP?

[RyanA]

I've been able to locate my driver "tulip" and run modprobe on it with no problems. ifconfig -a lists it as eth0..

Now there are two problems:

1) How do I make it obtain an IP address? -netcfg is not an option.
2) How do I make this perminate? -the mod isn't active after rebooting.. modprobe & insmod seem to do the exact same thing.

[DMR]

"ifconfig -a" gives stats for all network interfaces, active or not. Run ifconfig without the -a option and see if info for your NIC (eth0) shows up there. Post the results here.


You also need to give us more information; at the least:

1. Distro and version of Linux that you are running.
2. Make and model of your NIC.

[RyanA]

I guess I forgot to state that I'm running Trustix which has a 2.2.22 kernel. NIC is the DEC 21041 ..I already know what driver to use.

Running lsmod and ifconfig -a was done just to make sure that it was there and working correctly. Once the module is loaded I must run ifconfig eth0 up before it will show in ifconfig without any arguments.

Once done It gives me the MAC address & such. No IP address.. which like I said needs to be handled through DHCP.



For the second question I've added alias eth0 tulip to /etc/modules.conf, but it doesn't start the module during boot.

[teeitup]

Do you have a DHCP client installed?
pump & dhcp-client are the two I know about.

If you have...do you have a /etc/network/interfaces file?

if so it should look something like this:
teeitup@diablo:~$ more /etc/network/interfaces
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# The first network card
auto eth0
iface eth0 inet dhcp

Of course I know nothing about Trustix.

Good Luck,

[RyanA]

pump is installed but there is no /etc/network

[mdwatts]

First ensure PnP OS is disabled in the bios as that alone can prevent pci devices from being detected correctly and the modules from being loaded.

If that fails, add

/sbin/modprobe tulip

to /etc/rc.d/rc.local

or else add

alias eth0 tulip

to /etc/modules.conf.

Try /etc/sysconfig/network instead.

[RyanA]

ifup & ifdown are seperate files located in /etc/sysconfig/network-scripts/

ifup and ifdown appear to be perl? programs that take variables from other files prefixed with ifcfg-. ifcfg-lo is the only example:
DEVICE=lo
IPADDR=127.0.0.0
NETMASK=255.0.0.0
NETWORK=127.0.0.0
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback


I created ifcfg-eth0, set chmod to 755 and added:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
NAME=ethernet


BOOTPROTO is a variable in the ifup script tied to dhcp.

It fails to initialize during boot.. It actually trys now, so that's a start. After booting I can bring it up by typing ifconfig eth0 up then pump.

This is starting to hurt my head. I have never used perl and I hate reading code I didn't write. Thanks for the advice, it's been getting closer and closer to functioning as it should. Is there anything else I should try?

[mdwatts]

Originally posted by mdwatts
First ensure PnP OS is disabled in the bios as that alone can prevent pci devices from being detected correctly and the modules from being loaded.

If that fails, add

/sbin/modprobe tulip

to /etc/rc.d/rc.local

or else add

alias eth0 tulip

to /etc/modules.conf.

Try /etc/sysconfig/network instead.

You didn't say whether you tried any of the previous suggestions I posted.

[RyanA]

First ensure PnP OS is disabled in the bios as that alone can prevent pci devices from being detected correctly and the modules from being loaded.

Didn't change anything.


If that fails, add

/sbin/modprobe tulip

to /etc/rc.d/rc.local

Result was the tulip module loaded at boot.. eth0 fails to initialize.


or else add

alias eth0 tulip

to /etc/modules.conf.

Mentioned this in my second post. It did nothing for me.


Try /etc/sysconfig/network instead. [/B]

Mentioned in my last post that /etc/sysconfig/ exists but network doesn't. In it's place there is a directory called network-scripts which contains ifup & ifdown as well as a few other scripts which appear to be written in perl.

[mdwatts]

'network' is a file in /etc/sysconfig and the ifcfg scripts etc. are in /etc/sysconfig/network-scripts.

So tulip loads ok, but eth0 will not come up.

It probably cannot get a ip address.

Is dhcpd running?

ps ax | grep dhcp

[RyanA]

dhcpd wasn't running. I set it to run at boot and rebooted the system. eth0 still failed to initialize.

ps ax | grep dhcp reports: 387 tty1 S 0:00 grep dhcp


There is no /etc/network/interfaces file on the system and no interface section inside the /etc/sysconfig/network file.


Here are the current results:

dhcpd is set to start at every boot.

Adding /sbin/modprobe tulip to /etc/rc.d/rc.local resulted in the tulip module being loaded at boot. However, I must still type ifconfig eth0 up to get it to list in ifconfig and be able to pump an IP address for it.

Creating ifcfg-eth0 in /etc/sysconfig/network-scripts/ resulted in the OS attempting to initialize eth0 at boot. Intitalization fails.

After boot typing ifconfig eth0 up then pump will successfully bring up the network.

[DMR]

Originally posted by RyanA
dhcpd wasn't running. I set it to run at boot and rebooted the system. eth0 still failed to initialize.

ps ax | grep dhcp reports: 387 tty1 S 0:00 grep dhcpThe daemon you would be looking for is the dhcpcd client daemon; dhcpd is the DHCP server daemon.

However, dhcpcd shouldn't be running, as you said you're using pump instead. You can use one or the other, but trying to activate both will cause a conflict.

I think pump uses the pumpd daemon; try the above grep using "pump" instead of "dhcp". If pumpd is running, you should get two results: one for the grep process itself, and one for pumpd.

What is the exact error you get for eth0 when the system boots? If you get something similar to "determining IP information for eth0- FAILED", then its probably a DHCP issue, but if the error is something like "bringing up interface eth0- FAILED" you could have hardware/resource conflicts.

Sorry I can't be of more help, as I"ve never used Trustix and am not familiar with the structure of its network-related files.

[RyanA]

I get nothing with ps ax | grep pump.

Exact error: Bringing up interface eth0 Delaying eth0 initialization. [FAILED]

I think I might be better off seeking an alternative to Trustix.

[DMR]

Originally posted by RyanA
I think I might be better off seeking an alternative to Trustix. Perhaps; I can't really recall anyone posting to this board with Trustix-related questions so you might, at least support-wise, be better off trying a more mainstream distro.

:)