[SOLVED] Archlinux and connectivity problem during instalation

Dueperdue · 2014-04-25 18:36:53

Hello all,

I downloaded the latest ISO image from the Arch Linux website and burned the .iso file on an USB drive with some of the many tools you can find on the web.

Once I get on the shell screen I try to test my connectivity to the internet but it doesn't work. My Ethernet card is correctly detected (I can see it if I do ifconfig) and is also in an "up" state.

I already tried to manually set the configuration using *ethtool* but with no luck. Also, I already tried re-activating the dhcp service but still no luck. I tried to bring the interface up/down and manually configure an IP address but it still doesn't work.

I searched in dmesg and as far as I can tell the r8xxx module of the kernel for my realtek card is loaded correctly.

I am really running out of options. The most frustrating thing is that only with Archlinux I have this problem. ALL the other distros run just fine, getting ip address from dhcp with no intervention from myself what-so-ever... So it's not a compatibility problem here but a configuration one.

I also noted that the dropped packets count increases as time goes by...

Here is some output from the commands:

    
    ping 8.8.8.8
    connect: Network is unreachable
    
    ethtool enp7s1
    Settings for enp7s1:
    	Supported ports: [ TP MII ]
    	Supported link modes:   10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	                        1000baseT/Half 1000baseT/Full 
    	Supported pause frame use: No
    	Supports auto-negotiation: Yes
    	Advertised link modes:  10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	                        1000baseT/Half 1000baseT/Full 
    	Advertised pause frame use: Symmetric Receive-only
    	Advertised auto-negotiation: Yes
    	Link partner advertised link modes:  10baseT/Half 10baseT/Full 
    	                                     100baseT/Half 100baseT/Full 
    	                                     1000baseT/Full 
    	Link partner advertised pause frame use: No
    	Link partner advertised auto-negotiation: Yes
    	Speed: 1000Mb/s
    	Duplex: Full
    	Port: MII
    	PHYAD: 0
    	Transceiver: internal
    	Auto-negotiation: on
    	Supports Wake-on: pumbg
    	Wake-on: g
    	Current message level: 0x00000033 (51)
    			       drv probe ifdown ifup
    	Link detected: yes
    	
    ifconfig
    enp7s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet6 fe80::16da:e9ff:fe21:fdbf  prefixlen 64  scopeid 0x20<link>
            ether 14:da:e9:21:fd:bf  txqueuelen 1000  (Ethernet)
            RX packets 943  bytes 64724 (63.2 KiB)
            RX errors 0  dropped 117  overruns 0  frame 0
            TX packets 17  bytes 2933 (2.8 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 0  (Local Loopback)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: enp7s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
        link/ether 14:da:e9:21:fd:bf brd ff:ff:ff:ff:ff:ff
    
    dmesg | grep r8169
    
    [    2.742091] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    [    2.742154] r8169 0000:07:01.0 (unregistered net_device): not PCI Express
    [    2.742666] r8169 0000:07:01.0 eth0: RTL8169sc/8110sc at 0xffffc9000181e000, 14:da:e9:21:fd:bf, XID 18000000 IRQ 19
    [    2.742668] r8169 0000:07:01.0 eth0: jumbo features [frames: 7152 bytes, tx checksumming: ok]
    [    9.037449] r8169 0000:07:01.0 enp7s1: link down
    [    9.037502] r8169 0000:07:01.0 enp7s1: link down
    [   11.874477] r8169 0000:07:01.0 enp7s1: link up
    
    route 
    
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface


    sudo systemctl status dhcpcd
    ● dhcpcd.service - dhcpcd on all interfaces
       Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled)
       Active: inactive (dead)

I also tried running simply "dhcpd" and it seemed to work (he saw my router and leased me an IP address) but at some point it timed out and didn't got an IP.

Thank you for your time.

Last edited by Dueperdue (2014-04-26 16:06:39)

jasonwryan · 2014-04-25 19:47:56

What happens if you start the service for your device: `systemctl start enp7s1@dhcpcd.service` - does that work? If not what is reported in the journal?

WonderWoofy · 2014-04-25 20:22:34

Yeah, you don't have an IP address in the output above. Not sure why dhcpcd@enp7s1.service isn't being run, or if maybe it is just failing.

I would guess that the timeout is probably due to IPv6 not being set up or leased. You could just use dhcpcd -t 0 enp7s1 to set the timeout to zero (which makes it wait indefinitely) and see if that works.

Dueperdue · 2014-04-25 20:30:33

jasonwryan wrote:

What happens if you start the service for your device: `systemctl start enp7s1@dhcpcd.service` - does that work? If not what is reported in the journal?

It doesn't do anything. But I don't know what do you mean by "journal". How do I check it?

WonderWoofy wrote:

I would guess that the timeout is probably due to IPv6 not being set up or leased. You could just use dhcpcd -t 0 enp7s1 to set the timeout to zero (which makes it wait indefinitely) and see if that works.

I'll try and see, but don't really love it as a long term solution though...

I wonder why I always had problems with Arch. Every time I have the good intention to try it something is f***ed up. Do I really have to surrender to Debian & Stuff ?

Head_on_a_Stick · 2014-04-25 21:50:44

Dueperdue wrote:

I downloaded the latest ISO image from the Arch Linux website and burned the .iso file on an USB drive with some of the many tools you can find on the web.

I don't know if its relevant to your problem, but the tool you're advised to use is good ol' dd

Dueperdue · 2014-04-26 06:04:37

@Head_on_a_Stick

I am on Windows. Unless I get Cygwin, I don't have dd. Furthermore, I used like 4 different tolls before finding one that works because of different syslinux versions & stuff.

However, don't think that's the problem...

WonderWoofy · 2014-04-26 06:26:55

There is a wiki page for how to properly use windows to make the live USB.

https://wiki.archlinux.org/index.php/US … In_Windows

Dueperdue · 2014-04-26 06:41:27

WonderWoofy wrote:

There is a wiki page for how to properly use windows to make the live USB.
https://wiki.archlinux.org/index.php/US … In_Windows

Yeah, First thing I checked. I used USBwriter

Spider.007 · 2014-04-26 10:15:44

Dueperdue wrote:

I also tried running simply "dhcpd" and it seemed to work (he saw my router and leased me an IP address) but at some point it timed out and didn't got an IP.

This seems to be the most important issue; but I don't understand what you mean here. First your router gives you an IP over dhcpcd; and then it .... takes the IP back? What exactly is happening; when do you get an IP and when do you lose it?

Dueperdue · 2014-04-26 10:22:08

Spider.007 wrote:

Dueperdue wrote:
I also tried running simply "dhcpd" and it seemed to work (he saw my router and leased me an IP address) but at some point it timed out and didn't got an IP.
This seems to be the most important issue; but I don't understand what you mean here. First your router gives you an IP over dhcpcd; and then it .... takes the IP back? What exactly is happening; when do you get an IP and when do you lose it?

In the terminal I typed "dhcpd".

Then in the following lines it says that my gateway (192.168.178.1) leased me with ip 192.168.178.41. Then it searches for IPv6 routers and it doesn't find any. After 20 seconds it says "timeout" and I get my prompt back. I check if I have an IP but I don't... don't know why it doesn't work.

I also tried using Archbang and it works perfectly. My only option now seems getting an older ISO of Arch and try to install that... It's kinda disappointing though... how come I have so many problems only with Arch?

Lone_Wolf · 2014-04-26 11:30:49

dueperdue,

To verify if IPv6 is the problem try :

dhcpcd --ipv4only

If things work with that, then your router doesn't handle ipv6 correctly.

Spider.007 · 2014-04-26 12:09:05

Dueperdue wrote:

Spider.007 wrote:
Dueperdue wrote:
I also tried running simply "dhcpd" and it seemed to work (he saw my router and leased me an IP address) but at some point it timed out and didn't got an IP.
This seems to be the most important issue; but I don't understand what you mean here. First your router gives you an IP over dhcpcd; and then it .... takes the IP back? What exactly is happening; when do you get an IP and when do you lose it?
In the terminal I typed "dhcpd".
Then in the following lines it says that my gateway (192.168.178.1) leased me with ip 192.168.178.41. Then it searches for IPv6 routers and it doesn't find any. After 20 seconds it says "timeout" and I get my prompt back. I check if I have an IP but I don't... don't know why it doesn't work.

This doesn't indicate a problem; you have a router that handles ipv4 and not ipv6; that is no problem. What do ifconfig or `ip link` say after dhcpcd exits? You should have a working setup after this. Can you ping 192.168.178.1?

Dueperdue wrote:

I also tried using Archbang and it works perfectly. My only option now seems getting an older ISO of Arch and try to install that... It's kinda disappointing though... how come I have so many problems only with Arch?

That won't help; the older version would still install new packages which are very likely to lead to the same issue

Dueperdue · 2014-04-26 16:06:06

I solved the problem.

Apparently there is a problem between my router (Fritz Box) and the dhcp version on Archlinux. They don't interact correctly.

To make it possible to have an internet connection, go into your Fritz Box settings and delete the IP related to your machine. Once you do this the router will give out IP's like it should.

The problems lies with the "Assign the same IP to this machine" option in the FritzBox settings. Apparently, when you select this option the DHCP on Arch goes crazy. Simply disable it, go back to your PC and get an address and the you can re-enable it without problems.

Thank you anyways for your help.

Lone_Wolf · 2014-04-27 20:58:40

Glad you solved it, dueperdue.

I can confirm that with some routers 'Assign the same IP to this machine' for IPv4 gives trouble with dhcpcd / archlinux and it has been that way for a long time.

It happened to me with 2 out of 4 fritzbox router models, and 3 out of 4 speedtouch/thomson models (different providers) .
On the problem routers it failed more then half the time, but i've never found a common cause for it.

Arch Linux

#1 2014-04-25 18:36:53

[SOLVED] Archlinux and connectivity problem during instalation

#2 2014-04-25 19:47:56

Re: [SOLVED] Archlinux and connectivity problem during instalation

#3 2014-04-25 20:22:34

Re: [SOLVED] Archlinux and connectivity problem during instalation

#4 2014-04-25 20:30:33

Re: [SOLVED] Archlinux and connectivity problem during instalation

#5 2014-04-25 21:50:44

Re: [SOLVED] Archlinux and connectivity problem during instalation

#6 2014-04-26 06:04:37

Re: [SOLVED] Archlinux and connectivity problem during instalation

#7 2014-04-26 06:26:55

Re: [SOLVED] Archlinux and connectivity problem during instalation

#8 2014-04-26 06:41:27

Re: [SOLVED] Archlinux and connectivity problem during instalation

#9 2014-04-26 10:15:44

Re: [SOLVED] Archlinux and connectivity problem during instalation

#10 2014-04-26 10:22:08

Re: [SOLVED] Archlinux and connectivity problem during instalation

#11 2014-04-26 11:30:49

Re: [SOLVED] Archlinux and connectivity problem during instalation

#12 2014-04-26 12:09:05

Re: [SOLVED] Archlinux and connectivity problem during instalation

#13 2014-04-26 16:06:06

Re: [SOLVED] Archlinux and connectivity problem during instalation

#14 2014-04-27 20:58:40

Re: [SOLVED] Archlinux and connectivity problem during instalation

Board footer