Click to See Complete Forum and Search --> : DSL, tuilp and DHCP.


Ulixes
03-01-2003, 10:51 PM
I installed my Linksys NIC and everything appeared to go fine meaning that netconfig detected the card and I uncommented the tulip line in rc.modules. Upon rebooting the messages said something about contacting the DHCP server and that the operation timed out. I can't provide that information exactly as it's not available in dmesg. I ran ifconfig and eth0 was not there.

I downloaded and installed roaring penguin's pppoe software thinking that the card may be set up dynamically. Even though the software compiled and installed without error it doesn't work. After trying adsl-start though, eth0 is now available.

My provider doesn't provide any information relating to a DHCP server. Dial-Up Networking in Windows has a "VPN Server" at 1.1.1.1 and everything else is server-assigned.

In my searches I haven't found anyone with a problem beyond getting the NIC set up properly. Am I in the same place? I just don't know...

Ulixes
03-03-2003, 05:40 PM
Linksys provides directions for Slackware v.3.x but I decided to try them anyway. I downloaded the latest version of the source code for tulip and tried following the compile options from Linksys. I also tried the compile options provided in tulip.c.

Using the Linksys directions:

gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet
-Wall -Wstrict -prototypes -O6 -c tulip.c
'[ -f /usr/include/linux/modversions.h ] && echo
-DMODVERSIONS`

I get an error telling me that [ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS is not a file or directory. And I also get the following errors using both sets of options; namely that pci-scan.h and...ugh, I forgot the other header file, but they don't exist. And indeed, they don't. They're not on my system.

As I said before I commented out the line "/sbin/modprobe tulip" from my rc.modules. I ran netconfig configuring as a DHCP server: no luck. I also tried using the static IP option providing the same ip address as in Windows (1.1.1.1), but that doesn't work as well. (There's also a netmask option that I don't know if I need.)

I've gone through these forums and google and haven't come up with anything. My ethernet card isn't even detected, but strangely enough, if I start PPPoE and kill the process I can see an eth0 device with ifconfig but not otherwise.

Anyway, when I don't get a response from this forum I assume that it's something stupid that no one can bother with. Maybe I'll try reinstalling Slackware...

bandwidth_pig
03-03-2003, 07:37 PM
I don't think you asked a stupid question at all. Can't say I know the answer to your problem for sure. But I'll give it a shot. I can tell you that it sounds like you are close. You say you uncommented the line for tulip. You also tried compiling the driver from source (which you shouldn't have to do). If you:

insmod tulip

What happens? You should get some sort of message saying the module was loaded or failed. It sounds to me like the module is not getting loaded. Try to insert the module directly. Prior to doing that though, as root you may want to do a:

lsmod

That will list all modules loaded. If tulip is loaded, then you should be good to go. You should be able to bring up eth0 via ifconfig. If you see eht0 and it does not have a IP then we can tackle that next.

Ulixes
03-04-2003, 01:12 AM
lsmod showed that tulip is loaded and insmod tulip said it was already there.

Still, when I boot up the eth0 device is not available according to ifconfig. It shows up after running adsl-connect. Is that the proper way for it to function? Is eth0 set up dynamically?

bandwidth_pig
03-04-2003, 08:40 PM
Hmm. The fact that it appears as though a DHCP client is trying to find a server suggests that you have a client running already. I am not sure if DHCP is your problem. You might take a look at :

http://en.tldp.org/HOWTO/mini/DHCP/x74.html

It has a dhcp client for slackware (link) that you can download and compile with instructions on how to do so. Since DHCP is dynamic (dynamic host configuration protocol), your ISP would only tell you that they use DHCP. That is unless they gave you a static IP. If they gave you a static IP, you don't need DHCP and you will have to hard code all the info in.

Ulixes
03-04-2003, 11:19 PM
I never for PPPoE to work however, my router came today and as I was setting it up it said that I should set the IP address to be detected by the DHCP server and voila! everything works.

I hate leaving problems unresolved but I hate using Windows even more. Thanks for the help.