Networking :: Trouble connecting to network via DHCP



Sorry for the delay, I haven't been able to test it out until today. Here is the info requested.

Which version of DSL: I don't know exactly, my iso just says 'current'. It is using a 2.4.26 Kernel, and I downloaded the most up to date DSL version in December 2006.

I am running on a 'frugal' hard drive install

I am fairly certain the jack I am using works. I will test it again this afternoon with a jack that I am SURE works. I'll make another post with those results.

Running Sudo ifconfig -a

before
Quote

eth0      Link encap:Ethernet  HWaddr 00:50:DA:FE:D1:A3  
         BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5 errors:0 dropped:0 overruns:0 carrier:5
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:174 (174.0 B)
         Interrupt:3 Base address:0x300

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:2 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:100 (100.0 B)  TX bytes:100 (100.0 B)


after running the netcardconfig

Quote

eth0      Link encap:Ethernet  HWaddr 00:50:DA:FE:D1:A3  
         BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:10 errors:0 dropped:0 overruns:0 frame:0
         TX packets:11 errors:0 dropped:0 overruns:0 carrier:6
         collisions:0 txqueuelen:1000
         RX bytes:1362 (1.3 KiB)  TX bytes:690 (690.0 B)
         Interrupt:3 Base address:0x300

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:10 errors:0 dropped:0 overruns:0 frame:0
         TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:533 (533.0 B)  TX bytes:533 (533.0 B)



The error returned when running netcardconfig is:
Quote

Error: Sending DHCP broadcast from device eth0Operation failed.
Failed.
Hit return to exit


Hopefully this helps.
Ok, this time from an ethernet jack that was confirmed to work 10 seconds before I plugged in.

sudo ifconfig -a

before attempting connection
Quote

eth0    Link encap:Ethernet  HWaddr 00:50:DA:FE:D1:A3  
         BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5 errors:0 dropped:0 overruns:0 carrier:5
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:174 (174.0 B)
         Interrupt:3 Base address:0x300

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:2 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:100 (100.0 B)  TX bytes:100 (100.0 B)


After attempting connection

Quote

eth0    Link encap:Ethernet  HWaddr 00:50:DA:FE:D1:A3  
         BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:5 errors:0 dropped:0 overruns:0 frame:0
         TX packets:11 errors:0 dropped:0 overruns:0 carrier:6
         collisions:0 txqueuelen:1000
         RX bytes:300 (300.0 B)  TX bytes:690 (690.0 B)
         Interrupt:3 Base address:0x300

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:10 errors:0 dropped:0 overruns:0 frame:0
         TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:533 (533.0 B)  TX bytes:533 (533.0 B)



Error message was the same as before.
University networks I have been on won't just let you connect any old laptop anywhere on the network - you have to get the Windows Monkeys to register the MAC address of your laptop in order to be able to get assigned an IP.  Where I was this meant the laptop got blueplated with an id code, and even then I could only use it on a certain part of the network - my department.

Machines with unrecognized MAC addresses simply could not connect via ethernet.

This sounds like your problem.  Do the Windows monkeys know about your laptop?  if you are dual booting Windows, get them to set it up on the network running Windows.  After that, booting dsl while hooked up will probably connect you.  If not, you can run ipconfig in a Windows command prompt and write down the settings, then manually set these up in dsl with ifconfig.  Put the name servers in /etc/resolv.conf if these are not already there.
I'll ask about the mac address, but last time I went in and asked about this, they seemed to think that it should just work without doing anything in particular.

I am not on a dual boot with windows, and they will only provide support to windows.
It sounds like it should just work, so something odd is happening.

My "carrier:0" from ifconfig stays at zero while yours is nonzero.

Could it be a 10/100/1000Mbps missmatch?  

dmesg | grep eth

If you still have the live CD (sounds like it is 3.1), try booting from that,
in case something has messed up your frugal install.

If that doesn't work, then try booting with some special cheatcodes.
You can see what you normally use with:

cat /proc/cmdline

add on any cheatcodes that you need to this:

boot:  dsl dma base norestore syslog nodhcp

edit:  oops, maybe you don't want the "dma" cheatcode.

Then, you can start a root shell and watch /var/log/messages to see what pump is doing with:

[/home/dsl]# less /var/log/messages

at another root shell:

[/home/dsl]# pump

or

/home/dsl]# pump -v

for more details.
Next Page...
original here.