Can't connect at all (DHCP)

Valok · 2009-08-08 21:12:01

So I've been stuck for about 3-4 hours now trying to connect to the internet so I can finish setting up my first ever Arch install. When trying to ping sites like google.com, I get an error saying "unkown host".

I've checked over rc.conf and /etc/hosts a number of times, and can't find anything wrong with them. The thing that I did notice however is that whether or not my computer is plugged into my router, it behaves the same. So it would seem that, for some reason, my computer isn't recognizing the fact that it is plugged into the router, and this being my first Arch install I have no idea what to do next.

I've also looked over all the wiki and forum information I could find without any leads.

I'm really looking forward to trying arch, just need to get past this roadblock!

*Edit*

If this helps, my router is setup for DHCP, and to give out IP adresses starting with 192.168.1.x

However, when I run ifconfig, I get a very different inet address (which I think is the same as IP address). I have no idea where its getting this number from, because I didn't put it in anywhere and its not communicating with the router.

I really think this is the problem, how do I get the DHCP to get an IP from my router (which should start with the above nomenclature) instead of this bogus one I have now?

Last edited by Valok (2009-08-08 22:28:19)

Valok · 2009-08-08 23:12:24

Here is some more information on my problem. This thread http://bbs.archlinux.org/viewtopic.php?id=44649&p=2 seems like he was having the exact same problem I am, the only difference is that he using wireless internet, while I am not.

After doing pkill dhcpcd and dhcpcd -d eth0 I get

Info, wlan0: dhcpcd 3.2.1 starting
Info, eth0: hardware address = 00:1b:fc:db:43:c2                                 
Info, eth0: broadcasting for a lease
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503                        
Debug, eth0: waiting on select for 20 seconds
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Debug, eth0: sending DHCP_DISCOVER with xid 0xf869503
Error, eth0: timed out
Info, eth0: trying to use old lease in '/var/lib/dhcpcd/dhcpcd-eth0.info'
Info, eth0: checking 169.254.23.216 is available on attatched networks        
Debug, eth0: sending ARP probe #1
Debug, eth0: sending ARP probe #2
Debug, eth0: sending ARP probe #3
Debug, eth0: sending ARP claim #1
Debug, eth0: sending ARP claim #2
warn, eth0: using IPV4LL address 169.254.23.216
Info, eth0: adding IP address 169.254.23.216/16                               
Debug, eth0: no dns information to write
Debug, eth0: forking to background

The solution the person on the other thread found involved a command "iwconfig wlan0 essid linksys" and I'm not sure what the wired equivalent of this would be.

I'd love some advice if anyone has some!

Valok · 2009-08-08 23:24:12

And even when I go into /var/lib/dhcpcd...... listed in the output I posted above and change the IP, it still doesn't work and for some reason still defaults back to the bogus IP address.

djszapi · 2009-08-09 05:16:17

Did you try it with dhclient too?

"iwconfig wlan0 essid linksys" -> You don't have to deal with it in case of wired network.

Valok · 2009-08-09 12:46:48

I have not tried dhclient, how do I give that a shot without being able to download it via pacman?

Last edited by Valok (2009-08-09 12:48:03)

Valok · 2009-08-11 00:12:03

I just got done DLing the latest arch .iso and reinstalled that. Still having no luck!

I really want to try arch out, but I just don't know how to get around this problem, please help.

Valok · 2009-08-11 00:20:07

Now when running dhcpcd -d eth0 I get the following

eth0: dhcpcd 4.1.10 starting
eth0: hardware address = 00:1b:fc:db:43:c2
eth0: executing '/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
eth0: waiting for carrier                       (It pauses here for a few seconds)
eth0: timed out
eth0: executing 'usr/lib/dhcpcd/dhcpcd-run-hooks', reason FAIL

Not being the biggest network or linux buff, I'm not sure what this really means, or what the possible reason for this error could be.

Valok · 2009-08-11 00:24:05

As it turns out, the light on the back of the ethernet card is not on. I'm assuming it should be because it has been in the past, and it seems this might be the root of the problem. But the weird thing is that eth0 DOES show up in ifconfig. But somehow the card itself isn't getting the signal from arch to turn itself on.

So why would my computer not talk with my ethernet card and tell it to turn on? And how do I get it to turn on?

If it helps, the output of lspci | grep -i net is.....

00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)

Last edited by Valok (2009-08-11 00:39:43)

Valok · 2009-08-11 02:03:33

Update:

I just typed in the command

[u][/u]ifconfig dev0 inet 192.168.1.2 netmask 255.255.255.0

This is where my router starts assigning DHCP IPs, so this should be correct.

After doing that, ifconfig outputs 102.168.1.2

And I might be getting a step closer, when pinging an address on my router (192.168.1.X) I get some results. However, those results include 100% packet loss, and I still cannot connect to www.google.com

Still lost as to what the next step is, please advise.

AdrenalineJunky · 2009-08-11 02:09:59

i'm not a networking expert either - but it looks to me like you may need to set your DNS sever manually, which should go in the /etc/resolv.conf.

i'd recomend using open DNS,

208.67.222.222
208.67.220.220

Valok · 2009-08-11 02:17:44

AdrenalineJunky wrote:

i'm not a networking expert either - but it looks to me like you may need to set your DNS sever manually, which should go in the /etc/resolv.conf.
i'd recomend using open DNS,
208.67.222.222
208.67.220.220

putting that into resolv.conf didn't seem to change anything. Also, when I ping my router, its actually returning the message "Destination Host Unreachable" and I get 100% packet loss. So it looks like I might not actually be able to ping my router after all. And the light in the back of the ethernet card is still not on, I think this is the root of the problem.

By the way, in the beginner's guide, it says that resolv.conf should have....

"nameserver 192.168.1.1"

But when I type that in, the text has a red background, and isn't saved into the file. I'm assuming nameserver is a placeholder, but what is a resolv.conf file supposed to look like?

Last edited by Valok (2009-08-11 02:21:28)

rson451 · 2009-08-11 02:24:35

If the light on your nic is not on, then you don't have a connection from your router. Try another port on the router or another cable.

Valok · 2009-08-11 11:57:05

rson451 wrote:

If the light on your nic is not on, then you don't have a connection from your router. Try another port on the router or another cable.

But I know that this exact setup was working on windows a couple days ago. Is there anything that would cause the light not to turn on?

I also just put "nameserver 192.168.1.1" in resolv.conf to point my computer towards the router and it still seems to have the same problem.

Another thing I noticed is that when I edit the resolv.conf file, and then restart my network, the file goes back to the default and the information that I put in there is erased for some reason.

Last edited by Valok (2009-08-11 12:04:34)

Valok · 2009-08-11 16:59:21

Any other thoughts and or reasons for this?

I also tried plugging my wife's laptop into the router using the same chord that I'm attempting to use on my computer, and that worked just fine. So its not the cable, or the router having an issue. Somehow, arch isn't communicating with my card properly.

Is there some sort of driver that I need to download with a different computer and then somehow install onto arch?

Last edited by Valok (2009-08-11 17:55:25)

tomd123 · 2009-08-11 18:38:08

dhcpcd sometimes has issues. I remember having a similar problem.

Type route. Do you see anything?

add

nameserver 208.67.222.222
nameserver 208.67.220.220

to the end of your /etc/resolv.conf

Valok · 2009-08-11 18:45:50

Do you mean just typing in "route" as a command? I'll try that when I get home.

I'll try adding those to resolv.conf also.

Should I take my router address out of resolv.conf?

Valok · 2009-08-13 12:23:38

tomd123 wrote:

dhcpcd sometimes has issues. I remember having a similar problem.
Type route. Do you see anything?
add
nameserver 208.67.222.222
nameserver 208.67.220.220
to the end of your /etc/resolv.conf

Sadly adding all that info the resolv.conf didn't change anything. I'm still unable to ping any site or my router.

When I type in "route" I get

Destination  Gateway  Genmask  Flags Metric rest  Use Iface

And thats all the output I get.

tomd123 · 2009-08-13 12:45:13

Ok, let's got some info. First of all, are you trying to get wireless or wired working? The reason I ask is because you're using iwconfig with wlan0 and then trying to get an ip from eth0, wlan0, and then you do something wierd like "ifconfig dev0 inet 192.168.1.2 netmask 255.255.255.0" (btw, pinging with 100% packet loss is not being connected).

Next, paste the output of "ifconfig", "ifconfig -a", and "sudo lspci -vv".

Last edited by tomd123 (2009-08-13 12:50:21)

Valok · 2009-08-13 14:15:45

tomd123 wrote:

Ok, let's got some info. First of all, are you trying to get wireless or wired working? The reason I ask is because you're using iwconfig with wlan0 and then trying to get an ip from eth0, wlan0, and then you do something wierd like "ifconfig dev0 inet 192.168.1.2 netmask 255.255.255.0" (btw, pinging with 100% packet loss is not being connected).
Next, paste the output of "ifconfig", "ifconfig -a", and "sudo lspci -vv".

I'm trying to work with a wired network. The iwconfig I posted earlier was from a person having a similar problem, but with a wired network. I figured out pretty quick that the iwconfig command didn't work

The output of ifconfig and ifconfig -a are the same

eth             link encap:Ethernet HWaddr: 00:1B:FC:DB:43:C2
                UP BROADCAST MULTICAST MTU: 1500 METRIC: 1
                RX Packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
                TX packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelan: 0
                RX Bytes: 0(0.0 b) TX Bytes: 0(0.0 b)
                interrupt: 21 Base address: 0xe000

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: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
                TX packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelan: 0
                RX Bytes: 0(0.0 b) TX Bytes: 0(0.0 b)

As for lspci -vv. When I do that command, the output doesn't fit entirely on one screen. How do I scroll up through the output so I can post all that info here?

Last edited by Valok (2009-08-13 14:16:22)

tomd123 · 2009-08-13 15:04:03

Install wgetpaste with "sudo pacman -S wgetpaste"
Then do the following:
"ifconfig -a | wgetpaste"
"sudo lspci -vv | wgetpaste"

Paste both of the links you get from running those commands.

tomd123 · 2009-08-13 15:14:19

I also noticed "eth0: dhcpcd 4.1.10 starting" which you pasted earlier... dhcpcd is currently at 5.0.6
When was the last time you updated? If recently, you might want to switch mirrors.

Valok · 2009-08-13 15:16:32

The problem with that is because of the fact that I can't connect to the internet, I also can't connect to pacman to download things as far as I know. But if that's not the case (let me know) , I'll be glad to give it a shot.

I actually just got done installing my first Arch base system, and that is where I'm stuck at now. So I've got literally nothing installed but the very base system. And as far as I know, I used the latest .iso to install it, but I could be wrong. Is there a command to check which version I'm using so I can compare it against the most recent .iso?

Last edited by Valok (2009-08-13 15:18:03)

tomd123 · 2009-08-13 15:21:38

Then do this:

"ifconfig -a > ifout"
"sudo lspci -vv > lsout"

Transfer the files to a computer with a working connection and paste them.

tomd123 · 2009-08-13 15:23:00

I'm guessing this is a fresh install.. Download the new 2009.08 image and try that one since you're using an old installer.

Last edited by tomd123 (2009-08-13 15:23:35)

Valok · 2009-08-13 15:27:04

I'll try doing those commands and posting the results once I get back home. I'll also give a new installer a try and see how that works out.

Arch Linux

#1 2009-08-08 21:12:01

Can't connect at all (DHCP)

#2 2009-08-08 23:12:24

Re: Can't connect at all (DHCP)

#3 2009-08-08 23:24:12

Re: Can't connect at all (DHCP)

#4 2009-08-09 05:16:17

Re: Can't connect at all (DHCP)

#5 2009-08-09 12:46:48

Re: Can't connect at all (DHCP)

#6 2009-08-11 00:12:03

Re: Can't connect at all (DHCP)

#7 2009-08-11 00:20:07

Re: Can't connect at all (DHCP)

#8 2009-08-11 00:24:05

Re: Can't connect at all (DHCP)

#9 2009-08-11 02:03:33

Re: Can't connect at all (DHCP)

#10 2009-08-11 02:09:59

Re: Can't connect at all (DHCP)

#11 2009-08-11 02:17:44

Re: Can't connect at all (DHCP)

#12 2009-08-11 02:24:35

Re: Can't connect at all (DHCP)

#13 2009-08-11 11:57:05

Re: Can't connect at all (DHCP)

#14 2009-08-11 16:59:21

Re: Can't connect at all (DHCP)

#15 2009-08-11 18:38:08

Re: Can't connect at all (DHCP)

#16 2009-08-11 18:45:50

Re: Can't connect at all (DHCP)

#17 2009-08-13 12:23:38

Re: Can't connect at all (DHCP)

#18 2009-08-13 12:45:13

Re: Can't connect at all (DHCP)

#19 2009-08-13 14:15:45

Re: Can't connect at all (DHCP)

#20 2009-08-13 15:04:03

Re: Can't connect at all (DHCP)

#21 2009-08-13 15:14:19

Re: Can't connect at all (DHCP)

#22 2009-08-13 15:16:32

Re: Can't connect at all (DHCP)

#23 2009-08-13 15:21:38

Re: Can't connect at all (DHCP)

#24 2009-08-13 15:23:00

Re: Can't connect at all (DHCP)

#25 2009-08-13 15:27:04

Re: Can't connect at all (DHCP)

Board footer