Slackware 8.1 rc.inet1 shell script problems

matruschka · 07-19-2002, 03:14 AM

Hi again! In my "Slackware 8.1 DHCP trouble"-thread,I posted this message,as I at the time due to some problem with dhcp server response was unable to connect to my ISP through eth0:

Quote:

Hi!Recently installed Slackware 8.1 and I can't get my internet connection to work properly.I connect to my ISP Bredbandsbolaget through eth0 using the module 3c59x.o and I've configured my network to use DHCP to obtain an dynamic IP address.
However,when the kernel is loaded at boot,I get this message:

dhcpcd[63] broadcasting DHCP_DISCOVER
dhcpcd[63] timed out waiting for a valid DHCP server response

Using lsmod,I get the loaded modules list and the 3c59x.o module is on it.And network card probing within netconfig finds my card right away,so the card is working properly.

3Com EtherLink XL PCI TPC NIC (3C900B-TPC) with
3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)

Anyone got any suggestion on how to fix this?

Later on,since I never manage to get the eth0 connection to work in Slackware 8.1 and knew it worked in 8.0,I re-installed that earlier version.Making a long story short,I later on installed Slackware 8.1 again and replaced its' default rc.inet1 shell script with the one from 8.0 and then the eth0 ISP connection worked!

For now this works just fine,but the rc.inet1 script I use now only supports a one network-card hardware configuration and since I perhaps I later on wants to take advantage of the dual network-card support in Slackware 8.1's default rc.inet1 script,I post this message hoping to get some help on what might be malfunctioning in the 8.1 default script.

The two rc.inet1 scripts are available here:
http://hem.spray.se/matruschka/subfils/rc.inet1.80org
http://hem.spray.se/matruschka/subfils/rc.inet1.81org

Mik · 07-19-2002, 05:03 AM

Well the way they added support for another interface in the second script is just to copy everything and do the same thing for the second interface. Kinda primitive because if you keep adding an interface it will get bigger and bigger.
You could just do the same for the 8.0 script to add a second interface. Just copy paste the code and change the variables to make them unique for each interface.

Well I don't know where in the script it is failing but they have set the -d flag when they call dhcpcd so it should contain info in the log files on why it's going wrong there.
They also add -t 10 and an optional hostname. But that all looks pretty normal.

Maybe you could just run the script and then post the output you get. And the errors you get in the log files.

matruschka · 07-20-2002, 02:40 AM

Quote:

Well the way they added support for another interface in the second script is just to copy everything and do the same thing for the second interface. Kinda primitive because if you keep adding an interface it will get bigger and bigger.
You could just do the same for the 8.0 script to add a second interface. Just copy paste the code and change the variables to make them unique for each interface.

Well I don't know where in the script it is failing but they have set the -d flag when they call dhcpcd so it should contain info in the log files on why it's going wrong there.
They also add -t 10 and an optional hostname. But that all looks pretty normal.

Maybe you could just run the script and then post the output you get. And the errors you get in the log files.

I'll be happy to run the script and post it's output and also to post the events logged in the logfiles,but I'm still a very unexperienced Linux user.Maybe you can tell me how to run the script (can it be done inside Linux?) and which logfiles to fetch?

Mik · 07-22-2002, 02:37 AM

Just get yourself to a command prompt and type the full name of the script with the path to run it. Or go to the directory and type the name of the script with a leading ./

Well it depends where it's going wrong and how your system is configured for which log files to check. But you could always run a 'ls -lt /var/log' to find out which log files have been modified since you ran the script. Should probably be some info in /var/log/messages.