[SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

trusktr · 2010-06-30 05:43:10

Hey Ralvez, the md5 checksum was identical to the one listed at archlinux.org/download so that is all good.

karol · 2010-06-30 06:05:14

Try a livecd and maybe reinstall - I've run out of ideas really.

trusktr · 2010-06-30 06:19:15

lol, ok. thanks for all the ideas though.

hokasch · 2010-06-30 06:34:11

Did you ever try to configure a static IP from commandline, after boot? That would be the thirst thing on my list, since it bypasses other possible sources of error (boor configs/dhcpd...) and may fail in a more informative way.

trusktr · 2010-06-30 15:02:33

Hey, i tried using a static IP but i'm not sure if i did correctly. I think i used the correct gateway for my router.

This is what i get when i use "netstat -nr" on my desktop:

[root@rocketship ~]# netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth0

So from that i can tell that my gateway address should be 192.168.1.1 right (I have a router)?

So my rc.conf for the troublesome laptop contains this:

eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

and in /etc/resolv.conf i have

nameserver 192.168.1.1

With that configuration it didn't work. Pinging google.com gives "unknown host" error.

Also, when i try "/etc/rc.d/network restart" is gives two messages:

:: Stopping Network                              [BUSY]
SIOCDELRT: No such process
                                                 [FAIL]
:: Starting Network                              [BUSY]
SIOCADDRT: No such process
                                                 [FAIL]

Last edited by trusktr (2010-06-30 15:10:09)

ataraxia · 2010-06-30 15:08:22

trusktr wrote:

So my rc.conf for the troublesome laptop contains this:

eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

You put yourself in 192.168.0.x and the router in 192.168.1.x . Typo? That's not going to work.

trusktr · 2010-06-30 15:18:11

Hey ataraxia, i tried changing my ip to 192.168.24.8 and the gateway at 192.168.1.1 but that didn't work.

trusktr · 2010-06-30 15:19:57

Oh my goodness, i fixed it!!!

I added root to the "network" group and dhcp worked.

I think perhaps Arch should include root in the network group by default.

karol · 2010-06-30 15:22:23

Can you post your /etc/group and the output of visudo?

trusktr · 2010-06-30 15:31:57

Yeah, i'll do it when i get my laptop online with google chrome

trusktr · 2010-06-30 15:38:08

Well interestingly, the system automatically changed the network group user from "root" to "network" after rebooting. SO the network daemon has to be in the network group to work i guess.

karol · 2010-06-30 15:49:30

> Yeah, i'll do it when i get my laptop online with google chrome
Just be sure to follow the wiki. Read it once or twice and you should be fine.

hokasch · 2010-06-30 17:09:22

[netstat -nr output...]
So from that i can tell that my gateway address should be 192.168.1.1 right (I have a router)?

no. you have to check you router config, or look where a correctly working client connects to. The netstat command showed what you configured in rc.conf, but that must not necessarily be the right adress. For example, my router uses 192.168.0.1.

i tried changing my ip to 192.168.24.8 and the gateway at 192.168.1.1 but that didn't work.

you have to asssign an IP inside the router's subnet, so if the router/gateway is 192.168.1.1, use 192.168.1.XX (where XX is between 2 and 254).

trusktr · 2010-06-30 22:39:42

Cool, good info to know hokasch. I officially know now.

Karol, here's my /etc/group and visudo output as promised:

/etc/group:

root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon,artluvr
mem:x:8:
kmem:x:9:
wheel:x:10:root,artluvr
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
network:x:90:
video:x:91:artluvr
audio:x:92:artluvr
optical:x:93:artluvr,hal
floppy:x:94:artluvr,hal
storage:x:95:artluvr,hal
scanner:x:96:
power:x:98:artluvr
nobody:x:99:
users:x:100:
dbus:x:81:
ntp:x:87:
avahi:x:84:
hal:x:82:
gdm:x:120:
nopasswdogin:x:1000:artluvr

visudo:

# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
#
# See the sudoers man page for the details on how to write a sudoers file.
#

# Host alias specification

# User alias specification

# Cmnd alias specification

# Defaults specification

# Runas alias specification

# User privilege specification
root    ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands
%wheel    ALL=(ALL) ALL

# Same thing without a password
# %wheel    ALL=(ALL) NOPASSWD: ALL

# Samples
# %users  ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users  localhost=/sbin/shutdown -h now

Now, for the wireless...

Last edited by trusktr (2010-06-30 22:48:56)

karol · 2010-06-30 22:48:43

> Karol, here's my /etc/group and visudo output as promised:
Sorry, but there's nothing posted.

BTW, are you sure you have to add root to _any_ group? You should create a user and add *the user* to the groups you need.
Maybe you should reinstall and start anew.

http://wiki.archlinux.org/index.php/Beginners'_Guide#Step_1:_Configuring_the_network_.28if_necessary.29

Also, make sure that you add root to the "network" group if not already added

trusktr · 2010-06-30 22:53:45

hehe youre too quick.. i was copying and pasting. There it is above.

Also, that tid bit in the wiki, I added that

Anyways, imsure about the group thing. It started wrking after that and also on my desktop root is already part of the network group as well... the wierd thing is how it turned into "network" instead of "root" by itself. Perhaps this is only for the network daemon (not networkmanager) because on my desktop with networkmanager it shows root, not network as the user of the "network" group (aside from normal users).

trusktr · 2010-06-30 23:04:26

Whoa! I just noticed that the network group has no users!... wierd. perhaps because i enabled wlan0 and also added my wireless drivers and firmware dhcpcd deleted the entries during boot.

So after removing wlan0 (that wasn't working) and setting root and artluvr (my normal user) in the network group and restarting, this is the resulting /etc/group:

(pasting after restart)

Last edited by trusktr (2010-06-30 23:05:52)

hokasch · 2010-06-30 23:04:40

That doesn't sound right to me. AFAIK the network group is meant for users to access network configuration, root does not need to be in it. Also your groups file says "network:x:90:", so root is not actually part of it.

BTW, google search with your error message from above...

karol · 2010-06-30 23:05:34

> Also, that tid bit in the wiki, I added that
I know that http://wiki.archlinux.org/index.php?title=Beginners'_Guide&action=history

> Anyways, imsure about the group thing.
Quite a few people are using Arch and none seems to have similar issues.

You can / should add your user to the group, cause it's empty atm:

network:x:90:

hokasch · 2010-06-30 23:09:06

Hey, why do you even have this line

eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"

instead of

eth0="dhcp"

in your rc.conf, if you want to use dhcpd??

http://wiki.archlinux.org/index.php/Con … nfigure_IP

ah well sorry, that was when you tried static IP... anyway, it did not work because you put yourself in another subnet than the router, as ataraxia pointed out

Last edited by hokasch (2010-06-30 23:21:11)

trusktr · 2010-06-30 23:17:25

ok, so the network group remains untouched after reboot. I believe when i installed gnome, one of the packages changed the network group. Then when i turned on wlan0 and eth0 at the same time and also listed the correct module in /etc/rc.conf and restarted, something (dhcpcd?) erased the users from the network group.

So wierd. I can't reproduce this.

Oh yeah, and those error messages above , hokasch, disappeared after adding root to the "network" group.

Anywho, wired network is working right now with normal setting and root in the network group. Now let me see what happenes if I remove root and leave only my user... i'll be back

trusktr · 2010-06-30 23:19:04

hokasch, i do have

eth0="dhcp"

After setting that line (after attempting static ip, but deciding to return to dhcp, then casually adding root to "network" group, viola: it worked!

So let me verify if it stops working after removing root...

karol · 2010-06-30 23:22:21

> So let me verify if it stops working after removing root...
Is *your user* in the network group? Are you logged in as your user? Can you ping, surf the web etc.?

hokasch · 2010-06-30 23:24:52

Not sure how you go on about removing root from network group, when it is not in it per your group file Having your user in the network group should not make a difference if you use the network daemon anyway.

trusktr · 2010-06-30 23:34:49

That's the thing hokasch, it is so wierd. Karol, when i first had this problem, i only had one user: root. I don't see any differenced now that i've added a user except that now network works no matter what regardless of who/what is in the "network" group.

So here's a brief summary of what i went through:
First i set everythig up for dhcp as per the Beginner's Guide, and it would not work at all, hence i started this thread.

Then i tried using static ip (eth0="eth0 192.168...."), but that didn't work.

Next, i returned the settings to work with dhcp (eth0="dhcp") and again, it would not work. I proceeded to add root to the "network" group ("network:x:90:root") and I'll be darned, it suddenly began to work after that!

Then i installed gnome and root disappeared from the "network" group.

Now, with the network group empty, or with any users in it, the network works no matter what!

I simply don't understand why it's working right now now with the same exact settings as i had at first when it didn't work. I'm guessing Gnome, Hal, and Dbus have something to do with this, but who knows what/how.

I think once i install networkmanager, and remove rc.conf settings, all will work perfectly, including wireless... lets see!

Last edited by trusktr (2010-06-30 23:39:37)

Arch Linux

#26 2010-06-30 05:43:10

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#27 2010-06-30 06:05:14

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#28 2010-06-30 06:19:15

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#29 2010-06-30 06:34:11

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#30 2010-06-30 15:02:33

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#31 2010-06-30 15:08:22

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#32 2010-06-30 15:18:11

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#33 2010-06-30 15:19:57

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#34 2010-06-30 15:22:23

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#35 2010-06-30 15:31:57

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#36 2010-06-30 15:38:08

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#37 2010-06-30 15:49:30

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#38 2010-06-30 17:09:22

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#39 2010-06-30 22:39:42

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#40 2010-06-30 22:48:43

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#41 2010-06-30 22:53:45

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#42 2010-06-30 23:04:26

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#43 2010-06-30 23:04:40

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#44 2010-06-30 23:05:34

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#45 2010-06-30 23:09:06

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#46 2010-06-30 23:17:25

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#47 2010-06-30 23:19:04

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#48 2010-06-30 23:22:21

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#49 2010-06-30 23:24:52

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#50 2010-06-30 23:34:49

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

Board footer