You are not logged in.

#1 2009-10-18 20:56:11

Wailer
Member
Registered: 2009-05-17
Posts: 30

network not working

I'm just configuring my new installation of Arch and I have problems with internet connection. When I boot network won't start (starting network ... [FAIL]) and after I login i have to run command dhcpcd and then restart network and it returns done. When I try ping google.com (or anything else) it says: unknown host and when I try to update anything with pacman it returns Transient resolver failure. I've been messing with /etc/resolv.conf, /etc/hosts, I added default gw 192.168.0.1 in rc.conf, but it's still not working. I'm sure it's not just problem with pacman because I tried different mirrors and it's always the same ... What should I do and where may the problem be? Internet connection works fine in Windows ...

P.S.:
command ifconfig also returns some error.
I also added dhcpcd -k eth0 dhcpcd -nd eth0 in /etc/rc.local so dhcp would start automatically at boot but it doesn't.

Last edited by Wailer (2009-10-18 20:57:49)

Offline

#2 2009-10-19 08:36:37

MadTux
Member
Registered: 2009-09-20
Posts: 553

Re: network not working

Its would probably be easier if you could show your /etc/rc.conf and /etc/hosts configuration files. How many network cards do you have in your system and are you sure that eth0 is the one that gets used by dhcpd, e.g. do you have a wlan card and does dhcpd try to use that instead of a wired card?

Offline

#3 2009-10-19 17:14:24

jey
Member
Registered: 2009-01-01
Posts: 20

Re: network not working

Sounds pretty similar to me, still havn't gotten it to work.

I get wrong xid errors when using dhcpcd.

Offline

#4 2009-10-20 16:18:17

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

relevant parts of my /etc/rc.conf:

eth0="dhcp"
INTERFACES=eth0

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

DAEMONS=(syslog-ng network netfs crond

/etc/hosts:

127.0.0.1 myname.domain.org localhost.localdomain localhost myname

I have only one network card.

Offline

#5 2009-10-20 16:24:52

neddie_seagoon
Member
Registered: 2009-08-23
Posts: 121

Re: network not working

What does your /etc/resolv.conf look like? Have you tried using OpenDNS nameservers?
http://wiki.archlinux.org/index.php/OpenDNS

Offline

#6 2009-10-20 17:19:32

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

I did, but with no luck.

Offline

#7 2009-10-20 17:30:57

dgregory46
Member
Registered: 2009-07-30
Posts: 11

Re: network not working

A few more details might be useful.

You say that internet works ok under Windows. What is your current setup?

1. Windows / Arch Dualboot
2. Windows is on a different machine
3. You removed Windows to install Arch
4. You installed Arch as a VM guest under Windows
5. ??

Are you getting your DHCP service from your own router or from your ISP?

Is the DHCP client actually installed? I'm almost certain it should be because it is in core, but malfunctions can happen.

Does your network card driver appear in an lsmod listing?

Can you post the specific error your get from ifconfig?

Offline

#8 2009-10-20 20:31:25

hagbard
Member
Registered: 2008-01-21
Posts: 2

Re: network not working

I also have lost my dhcp... after upgrading to
dhcpcd-5.1.1-1-x86_64.pkg.tar.gz and other packages (with Pacman -Su) on 10-16-09

It's difficult to post information since I can't get online until I reboot into windows (dual boot on HP laptop).

1) Everything worked fine before the upgrade.
2) dhcpcd keeps timing out and occassionally showing errors (when I run it with -ddd) that say "wrong xid" whatever the hell that is
3) the same errors occur trying to connect to a router at home and one at work
4) dhcpcd using -A or -I "" or combinations don't have any effect
5) dhclient (installed as a possible workaround) times out as well
6) downgrading to any of the previous four versions of dhcpcd (using pacman -Rd followed by pacman -U) that I have in /var/cache/pacman/pkg results in the same errors. i.e. doesn't fix it
7) wtf?

could it be from any of these other upgrades that were done with the evil pacman -Su that day?

mlocate
popt
dialog
gzip
glib2
openssh

Thanks for any light that anyone could shed on this.

Offline

#9 2009-10-20 21:33:55

Vladman
Member
Registered: 2009-01-28
Posts: 118

Re: network not working

eth0="dhcp"
INTERFACES=eth0

Should be

eth0="dhcp"
INTERFACES=(eth0)

Offline

#10 2009-10-21 09:20:18

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

My setup is 1.: Windows /Arch

I'm getting my DHCP from router - but I don't have access to router, because I'm in an foreign appartment.

DHCP is installed, because it runs if I type dhcpcd in console (if this is what you meant).

Specific error from ifconfig:

Link encap:Ethernet

sth sth sth

errors:4294967284

sth sth sth else

I can't post my lsmod list, because it's too long - just tell me what should I be looking for (or how to shorten the list).

Last edited by Wailer (2009-10-21 09:20:28)

Offline

#11 2009-10-27 13:08:06

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

Any ideas? Did I mess sth during the install, would it be good to try on different network ... anything?

Offline

#12 2009-10-27 14:02:48

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

It's still not clear that your network card is recognized by the kernel and that its driver is loaded. Could you try the following:
1. lspci |grep -i ethernet
2. dmesg |grep eth
and let us know what you get. Also if you know which kernel module contains the driver for you network card (google knows), you can check via lsmod if that driver is loaded. modinfo can also help if you are not sure which of your loaded modules is driving the network card.


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#13 2009-10-27 17:44:49

MadTux
Member
Registered: 2009-09-20
Posts: 553

Re: network not working

Did you correct that typo that Vladman pointed out?

eth0="dhcp"
INTERFACES=(eth0)

Offline

#14 2009-10-27 19:17:11

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

@MadTux: it was correct all the time; I made a typo.

@grey:

lspci |grep -i ethernet doesn't return anything but lspci returns (beside others):

Ethernet controller: Attansic Technology Corp. Device 1063 (rev ff)
Network controller: Intel Corporation Wireless WiFi Link 5100

dmesg |grep eth returns:

Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
atl1c 000:09:00.0:atl1c:eth0 NIC Link is Up<100 Mbps Full Duplex>

modinfo atl1c returns:

(random unimportant facts) /.../

depends:
vermagic: 2.6.30-ARCH SMP preempt mod_unload 686

lsmod returns atl1c but I think I modprobe this driver manually while I was trying to solve my problem so it may not mean anything.

Last edited by Wailer (2009-10-27 19:18:03)

Offline

#15 2009-10-27 20:10:01

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

lspci |grep -i ethernet doesn't return anything but lspci returns [line starting with the word Ethernet]

That is not possible. It isn't relevant to your problem, but pls. check again.

Next step is dmesg | grep atl1c. But it looks as if the module is loaded correctly by the kernel.
What kind of errors are you getting from ifconfig? from dhcpcd?


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#16 2009-10-28 09:10:39

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

Apparently I made a typo smile, lspci |grep -i ethernet returns:

Ethernet controller: Attansic Technology Corp. Device 1063 (rev ff)

lsmod |grep atl1c:

atl1c      32136   0

dhcpcd shows some error (unable to connect or sth like that) at boot, but when I start it manually it works just fine and if I restart network (/etc/rc.d/network restart) it works too (but network fails to start at boot too).

ifconfig returns:

eth0   Link encap: Ethernet HWaddr 00:26:9E:2B:FC:A8
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4294967294 errors:4294967284 dropped:4294967292 overruns:4294967294 frame:4294967286
TX packets:4294967294 errors:4294967288 dropped:0 overruns:4294967294 carrirer:4294967293
collisions:4294967286 fxqueuelen:1000
RX bytes:4294967294 (4095.9 Mb) Tx bytes:4294967294 (4095.9 Mb)
Interrupt:30

Is this maybe some problem with module? I tried module atl1e (since I google that this maybe be it with this network car) but it doesn't seem to work (some errors), so I switched back to atl1c.

Last edited by Wailer (2009-10-28 09:11:21)

Offline

#17 2009-10-28 09:16:21

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

Did you just not paste the output for lo that is reported by ifconfig, or is there really nothing but eth0?

Also: I asked for dmesg |grep atl1c, not lsmod | grep atl1c

Last edited by grey (2009-10-28 09:24:21)


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#18 2009-10-28 09:22:20

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

I didn't pasted it because I can't - I'm writing from Windows since I have no graphical environment in Arch (I can't install it without connection). But there is no errors in lo section.

Offline

#19 2009-10-28 09:28:26

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

I thought your network works when you start it manually? Then you can go and install the graphical environment.


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#20 2009-10-28 09:36:45

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

Well it starts without error but pacman still returns me "transient resolver failure" ...

Offline

#21 2009-10-28 09:57:22

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

Just use ping to check if you have connectivity. At the very least you should be able to ping your gateway:

# ping -c 1 192.168.0.1
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.696 ms

But this won't work until ifconfig eth0 tells you that you have an inet address. Something like

# ifconfig eth0
eth0    Link encap:Ethernet  HWaddr <...>  
          inet addr:192.168.1.65  Bcast:192.168.1.255  Mask:255.255.255.0

Are you sure that 192.168.0.1 is your gateway? That is often, but not always true. Mine, for example, is 192.168.1.254. If you're not sure and don't know how to find out, let me know - you can do it from windows.

Edit: might as well post is now: go the command line (yes, on windows) and type ipconfig. There should be a line

Default Gateway .............................. <ip address>

Last edited by grey (2009-10-28 10:02:33)


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#22 2009-10-29 10:44:32

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

ifconfig eth0 returns same error as I already wrote.

ipconfig in Windows shows that default gateway is 192.168.1.1

ping -c 192.168.1.1 (or 192.168.0.1) returns sth about command usage

ping 192.168.1.1 (or 192.168.1.1) returns:

connect: network is unreachable

I also changed default gateway in /etc/rc.cond to 192.168.1.1 but there is no difference.

Offline

#23 2009-10-29 11:09:20

Wailer
Member
Registered: 2009-05-17
Posts: 30

Re: network not working

so I found this topic with the same problem: http://bbs.archlinux.org/viewtopic.php?id=33435 and I changed /etc/rc.conf; ROUTES=(!gateway) to ROUTES=(gateway) and also changed eth0 to static IP settings (same as in Windows) but it still doesn't work.

ping 192.168.1.1 (or any other IP) returns:

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.5 icmp_seq=1 Destination host unreachable
From 192.168.1.5 icmp_seq=2 Destination host unreachable
From 192.168.1.5 icmp_seq=3 Destination host unreachable
From 192.168.1.5 icmp_seq=4 Destination host unreachable
...

It is the same with static IP setting or with eth0="dhcp" line in /etc/rc.conf.

Offline

#24 2009-10-29 11:31:18

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

It's

ping -c 1 <ip address>

. You forgot the '1'.
Just to be sure: changes in rc.conf only take effect after rebooting.
Also: could you tell me the output of dmesg |grep atl1? Just to make sure there's no problem there.

Another thing you could try is to get a lightweight live distribution, for example browserlinux (http://www.browserlinux.com/) and boot it. It has good network configuration scripts. See if it gets you online, then check with lsmod and dmesg what it is doing right, and compare that to what arch is doing.


Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

#25 2009-10-29 12:29:16

grey
Member
From: Europe
Registered: 2007-08-23
Posts: 679

Re: network not working

Here is what /etc/rc.d/network restart does in my case (and fails to do in yours).

Could you try each step and see where your results differ?

[root ~]# dhcpcd -dd -k eth0
dhcpcd: sending signal 1 to pid 1909
dhcpcd: waiting for pid 1909 to exit
[root ~]# ifconfig eth0 down
[root ~]# ifconfig eth0 up
[root ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr <...>  
          inet6 addr: f<...> Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:262 errors:0 dropped:0 overruns:0 frame:0
          TX packets:178 errors:0 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000
          RX bytes:43203 (42.1 Kb)  TX bytes:16504 (16.1 Kb)

[root ~]# dhcpcd -dd eth0
dhcpcd: version 5.1.1 starting
dhcpcd: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd: eth0: broadcasting for a lease
dhcpcd: eth0: sending DHCP_DISCOVER (xid 0x77bb2a25), next in 4.59 seconds
dhcpcd: eth0: offered 192.168.1.68 from 192.168.1.254
dhcpcd: eth0: sending DHCP_REQUEST (xid 0x77bb2a25), next in 3.83 seconds
dhcpcd: eth0: acknowledged 192.168.1.68 from 192.168.1.254
dhcpcd: eth0: checking for 192.168.1.68
dhcpcd: eth0: sending ARP probe (1 of 3), next in 1.31 seconds
dhcpcd: eth0: sending ARP probe (2 of 3), next in 1.93 seconds
dhcpcd: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
dhcpcd: eth0: leased 192.168.1.68 for 86400 seconds
dhcpcd: eth0: adding IP address 192.168.1.68/24
dhcpcd: eth0: adding route to 192.168.1.0/24
dhcpcd: eth0: adding default route via 192.168.1.254
dhcpcd: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
dhcpcd: forking to background

Good ideas do not need lots of lies told about them in order to gain public acceptance.

Offline

Board footer

Powered by FluxBB