You are not logged in.

Pages: 1

#1 2014-10-27 16:29:38

n_t
Member
Registered: 2013-02-01
Posts: 48

Cannot Connect with IPv4 Through Wired Interface

I'm using NetworkManager and the gui nm-applet. Unfortunately wired connections will not work with IPv6.

I've tried disabling IPv6 in the gui (method = ignore) and specifying on the IPv4 tab "requires an IPv4 connection to complete". However, it still only gets an IPv6 address as shown below:

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::ab11:c257:f23b:38e1  prefixlen 64  scopeid 0x20<link>
        ether d4:be:d9:22:26:fb  txqueuelen 1000  (Ethernet)
        RX packets 214  bytes 20796 (20.3 KiB)
        RX errors 354  dropped 18  overruns 0  frame 196
        TX packets 579  bytes 60069 (58.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xe2e00000-e2e20000

I see activity in journalctl. But only IPv6. It doesn't even seem to bother trying for IPv4:

NetworkManager[1371]: <info> (eno1): DHCPv4 state changed nbi -> preinit
Oct 27 16:15:04 nickT_Arch NetworkManager[1371]: dhcpcd[2407]: DUID 00:01:00:01:19:ba:14:f3:d4:be:d9:22:26:fb
Oct 27 16:15:04 nickT_Arch NetworkManager[1371]: dhcpcd[2407]: eno1: IAID d9:22:26:fb
Oct 27 16:15:04 nickT_Arch kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 27 16:15:04 nickT_Arch kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 27 16:15:04 nickT_Arch dhcpcd[2407]: eno1: soliciting a DHCP lease
Oct 27 16:15:04 nickT_Arch NetworkManager[1371]: dhcpcd[2407]: eno1: soliciting a DHCP lease
Oct 27 16:15:04 nickT_Arch kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 27 16:15:05 nickT_Arch dhcpcd[2407]: eno1: soliciting an IPv6 router
Oct 27 16:15:05 nickT_Arch NetworkManager[1371]: dhcpcd[2407]: eno1: soliciting an IPv6 router
Oct 27 16:15:05 nickT_Arch avahi-daemon[329]: Registering new address record for fe80::ab11:c257:f23b:38e1 on eno1.*

I'm out of ideas about what to investigate next. Any suggestions would be really helpful.

Last edited by n_t (2014-10-27 16:40:32)

Offline

#2 2014-10-27 16:43:24

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,353

Re: Cannot Connect with IPv4 Through Wired Interface

Please post the output of ip addr

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2014-10-27 16:53:14

branch
Member
Registered: 2014-03-16
Posts: 209

Re: Cannot Connect with IPv4 Through Wired Interface

It does try to get a IPv4 lease:

Oct 27 16:15:04 nickT_Arch dhcpcd[2407]: eno1: soliciting a DHCP lease

but there is no response.

You have lots of receive errors. 354 RX errors with only 214 RX packets means that most receive packets are being lost. There is a high chance the dpcd server's response was lost due to a recieve error. First thing I would try is a different cable.

Offline

#4 2014-10-27 16:56:19

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

ewaller wrote:

Please post the output of ip addr

ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 8c:70:5a:04:c1:14 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.26/24 brd 192.168.1.255 scope global dynamic wlp2s0
       valid_lft 84097sec preferred_lft 84097sec
    inet6 fe80::c0cb:fbf8:79d3:85ae/64 scope link 
       valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether d4:be:d9:22:26:fb brd ff:ff:ff:ff:ff:ff

Offline

#5 2014-10-27 17:36:45

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

branch wrote:

It does try to get a IPv4 lease:

Oct 27 16:15:04 nickT_Arch dhcpcd[2407]: eno1: soliciting a DHCP lease

but there is no response.

You have lots of receive errors. 354 RX errors with only 214 RX packets means that most receive packets are being lost. There is a high chance the dpcd server's response was lost due to a recieve error. First thing I would try is a different cable.

I had already tried a few cables but just now I went round the office and tried a few cables and sockets that are definitely working for colleagues and still the same problem. Journalctl shows the same logs and the network manager tooltip just indicates it is trying to get an IP address.

Offline

#6 2014-10-27 17:56:50

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,353

Re: Cannot Connect with IPv4 Through Wired Interface

I was poking around looking for cable problems too smile  It looks like it has a carrier, so what do you get from sudo dhcpcd -d eno1

Also, the device is called eno1?  That is usually associated with a network controller that is part of SoC (System on a Chip) computer rather than on a bus, such as PCI or USB.  It could be that this is a NIC that is part of your motherboard, and is not on a PCI-e  connection, but it is a little unusual.   It is not a big deal, I just tend to latch on to anything out of the ordinary.

Last edited by ewaller (2014-10-27 17:57:09)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#7 2014-10-28 09:16:38

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

ewaller wrote:

I was poking around looking for cable problems too smile  It looks like it has a carrier, so what do you get from sudo dhcpcd -d eno1

Also, the device is called eno1?  That is usually associated with a network controller that is part of SoC (System on a Chip) computer rather than on a bus, such as PCI or USB.  It could be that this is a NIC that is part of your motherboard, and is not on a PCI-e  connection, but it is a little unusual.   It is not a big deal, I just tend to latch on to anything out of the ordinary.

I thought there was something odd about en01, too, although I wasn't quite sure why. Anyway, I made a breakthrough that might be relevant.

Yesterday evening I managed to connect via wired connection. It seemed to be intermittent, but one thing I had done is disabled docker. I booted up this morning and it immediately connected. Then I needed to use docker so I started the docker service - immediately my wired connection went down and I had to resort to Wifi.

Is it possible that en01 is an interface controlled by docker, and somehow NetworkManager/DHCPCD think this is a standard connection? Maybe I'm talking rubbish. Here's the journalctl output that occurred just after I enabled docker:

Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> (eno1): deactivating device (reason 'none') [0]
Oct 28 09:08:19 nickT_Arch dhcpcd[4561]: received signal TERM from PID 326, stopping
Oct 28 09:08:19 nickT_Arch dhcpcd[4561]: eno1: removing interface
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: dhcpcd[4561]: received signal TERM from PID 326, stopping
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: dhcpcd[4561]: eno1: removing interface
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <warn> (eno1): DHCP client pid 4561 didn't exit, will kill it.
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> (eno1): canceled DHCP transaction, DHCP client pid 4561
Oct 28 09:08:19 nickT_Arch avahi-daemon[324]: Withdrawing address record for fe80::d6be:d9ff:fe22:26fb on eno1.
Oct 28 09:08:19 nickT_Arch avahi-daemon[324]: Withdrawing address record for 192.168.111.25 on eno1.
Oct 28 09:08:19 nickT_Arch avahi-daemon[324]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.111.25.
Oct 28 09:08:19 nickT_Arch avahi-daemon[324]: Interface eno1.IPv4 no longer relevant for mDNS.
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> NetworkManager state is now DISCONNECTED
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> Activation (eno1) starting connection 'Auto Ethernet'
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> Activation (eno1) Stage 1 of 5 (Device Prepare) scheduled...
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <warn> (pid 4561) unhandled DHCP event for interface eno1
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> Activation (eno1) Stage 1 of 5 (Device Prepare) started...
Oct 28 09:08:19 nickT_Arch NetworkManager[326]: <info> (eno1): device state change: disconnected -> prepare (reason 
sudo dhcpcd -d en01
[sudo] password for nick: 
dhcpcd[4102]: version 6.5.1 starting
dhcpcd[4102]: en01: interface not found or invalid
dhcpcd[4102]: exited

Last edited by n_t (2014-10-28 10:00:20)

Offline

#8 2014-10-28 15:23:52

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,353

Re: Cannot Connect with IPv4 Through Wired Interface

I have never used docker and know nothing about it sad   Let's see if you have more than one thing trying to control it.  What is the output of systemctl status?


By the Way:

sudo dhcpcd -d en01
[sudo] password for nick: 
dhcpcd[4102]: version 6.5.1 starting
dhcpcd[4102]: en01: interface not found or invalid
dhcpcd[4102]: exited

The Interface name is eno1, not en01

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#9 2014-10-28 15:30:25

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

Sorry for the dhcpcd noob mistake:

sudo dhcpcd eno1
dhcpcd[18244]: dhcpcd already running on pid 18235 (/run/dhcpcd-eno1.pid)

systemctl is showing:

● nickT_Arch
    State: degraded
     Jobs: 0 queued
   Failed: 2 units
    Since: Tue 2014-10-28 14:42:29 GMT; 44min ago
   CGroup: /
           ├─1 /sbin/init
           ├─system.slice
           │ ├─avahi-daemon.service
           │ │ ├─324 avahi-daemon: running [nickTArch.local
           │ │ └─335 avahi-daemon: chroot helpe
           │ ├─dbus.service
           │ │ └─331 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
           │ ├─monitorix.service
           │ │ ├─483 /usr/bin/monitorix -c /etc/monitorix.conf -p /run/monitorix.pi
           │ │ └─789 monitorix-httpd listening on 809
           │ ├─wpa_supplicant.service
           │ │ └─754 /usr/bin/wpa_supplicant -u
           │ ├─lightdm.service
           │ │ ├─363 /usr/bin/lightdm
           │ │ └─683 /usr/bin/Xorg.bin :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
           │ ├─colord.service
           │ │ └─698 /usr/lib/colord/colord
           │ ├─systemd-journald.service
           │ │ └─146 /usr/lib/systemd/systemd-journald
           │ ├─udisks2.service
           │ │ └─959 /usr/lib/udisks2/udisksd --no-debug
           │ ├─upower.service
           │ │ └─964 /usr/lib/upower/upowerd
           │ ├─cups.service
           │ │ └─330 /usr/bin/cupsd -f
           │ ├─systemd-logind.service
           │ │ └─348 /usr/lib/systemd/systemd-logind
           │ ├─systemd-udevd.service
           │ │ └─164 /usr/lib/systemd/systemd-udevd
           │ ├─polkit.service
           │ │ └─700 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─NetworkManager.service
           │ │ ├─326 /usr/bin/NetworkManager --no-daemon
           │ │ └─888 /usr/bin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-helper wlp2s0
           │ ├─docker-c5fec690e8d5f9443d6225275c6d15a787aa4ae9b9ac92b4f7d65ec889ae44e8.scope
           │ │ ├─10625 /sbin/init
           │ │ ├─13301 /usr/opt/redis/redis-2.8.3/src/redis-server *:637
           │ │ ├─13307 /usr/opt/redis/redis-2.8.3/src/redis-server *:7878     
           │ │ ├─13315 /usr/sbin/sshd -D
           │ │ ├─13322 rsyslogd -c5
           │ │ ├─13674 sshd: vagrant [priv]
           │ │ ├─13687 sshd: vagrant@pts/0 
           │ │ ├─13688 -bash
           │ │ ├─16473 /usr/lib/jvm/java-7-openjdk-amd64//bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true
           │ │ └─16575 java -Dactivator.home=/vagrant/dev_env/deps/play/activator-1.2.10-minimal -Xms1024m -Xmx1024m
           │ ├─docker.service
           │ │ ├─  745 /usr/bin/docker -d -H fd://
           │ │ ├─10577 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9000 -container-ip 172.17.0.3 -container-
           │ │ ├─10585 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9200 -container-ip 172.17.0.3 -container-
           │ │ ├─10593 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9300 -container-ip 172.17.0.3 -container-
           │ │ ├─10601 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 2222 -container-ip 172.17.0.3 -container-
           │ │ ├─10610 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 7878 -container-ip 172.17.0.3 -container-
           │ │ └─10618 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 6379 -container-ip 172.17.0.3 -container-
           │ └─rtkit-daemon.service
           │   └─1049 /usr/lib/rtkit/rtkit-daemon
           └─user.slice
             ├─user-1000.slice
             │ ├─user@1000.service
             │ │ ├─895 /usr/lib/systemd/systemd --user
             │ │ └─896 (sd-pam)  
             │ └─session-c2.scope
             │   ├─  864 lightdm --session-child 13 20
             │   ├─  898 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
             │   ├─  905 dbus-launch --sh-syntax --exit-with-session
             │   ├─  906 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
             │   ├─  911 xfce4-session
             │   ├─  914 /usr/lib/xfce4/xfconf/xfconfd
             │   ├─  917 /usr/bin/gpg-agent --sh --daemon --enable-ssh-support --write-env-file /home/nick/.cache/gp
             │   ├─  918 xfwm4 --display :0.0 --sm-client-id 23192d16a-9406-4bf5-8f5f-965d09c8464a
             │   ├─  920 Thunar --sm-client-id 2507ae716-1990-4ba2-a13c-421244a5a07f --daemon
             │   ├─  922 xfce4-panel --display :0.0 --sm-client-id 2468c4a63-3784-4c36-842c-521c60c85842
             │   ├─  923 xfsettingsd --display :0.0 --sm-client-id 2dd89ff54-6fd3-431f-8c9b-020d786fb579
             │   ├─  924 xfdesktop --display :0.0 --sm-client-id 277462b4c-723d-4ea3-91b9-4918c95b2346
             │   ├─  925 /usr/lib32/skype/skype -session 2714e075a-cf95-44eb-970f-a81a56d052fd_1414507277_707898
             │   ├─  926 /usr/bin/hipchat -session 2fcd3b22e-bcf6-4705-a60f-5aaf796a6b6d_1414507277_706804 -name hip
             │   ├─  931 xfce4-power-manager --restart --sm-client-id 2bc564082-9265-4aaf-8ff1-1c2e34097a6c
             │   ├─  938 /usr/lib/gvfs/gvfsd
             │   ├─  957 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
             │   ├─  977 /usr/lib/gvfs/gvfsd-trash --spawner :1.11 /org/gtk/gvfs/exec_spaw/0
             │   ├─  990 perl /usr/bin/volwheel
             │   ├─  999 pasystray
             │   ├─ 1012 tint2
             │   ├─ 1018 kalu
             │   ├─ 1036 xscreensaver -no-splash
             │   ├─ 1041 nm-applet
             │   ├─ 1048 /usr/bin/pulseaudio --start
             │   ├─ 1069 /usr/lib/pulse/gconf-helper
             │   ├─ 1071 /usr/lib/GConf/gconfd-2
             │   ├─ 1082 sublime
             │   ├─ 1084 /usr/bin/python2 /usr/bin/terminator
             │   ├─ 1086 conky
             │   ├─ 1204 gnome-pty-helper
             │   ├─ 1207 /bin/zsh
             │   ├─ 1318 /home/nick/.dropbox-dist/dropbox-lnx.x86_64-2.10.30/dropbox /newerversion
             │   ├─ 6478 synapse
             │   ├─ 6570 /usr/lib/chromium/chromium
             │   ├─ 6574 /usr/lib/chromium/chrome-sandbox /usr/lib/chromium/chromium --type=zygote
             │   ├─ 6576 /usr/lib/chromium/chromium --type=zygote
             │   ├─ 6580 /usr/lib/chromium/chrome-sandbox /usr/lib/chromium/nacl_helper
             │   ├─ 6581 /usr/lib/chromium/nacl_helper
             │   ├─ 6583 /usr/lib/chromium/chromium --type=zygote
             │   ├─ 6604 /usr/lib/chromium/chromium --type=gpu-process --channel=6570.0.828054668 --supports-dual-gp
             │   ├─ 6608 /usr/lib/chromium/chromium --type=gpu-broker                                               
             │   ├─ 6617 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6642 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6646 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6661 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6674 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6680 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6690 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 6699 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 7711 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 7816 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 8147 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 8946 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─ 8982 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─13600 bash /usr/bin/vagrant ssh
             │   ├─13607 ssh vagrant@172.17.0.3 -p 22 -o Compression=yes -o DSAAuthentication=yes -o LogLevel=FATAL 
             │   ├─14553 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─18011 /usr/lib/chromium/chromium --type=renderer --enable-deferred-image-decoding --lang=en-GB --
             │   ├─18705 /bin/zsh
             │   ├─18756 sudo systemctl status
             │   ├─18763 systemctl status
             │   └─18764 less
             └─user-620.slice
               ├─user@620.service
               │ ├─842 /usr/lib/systemd/systemd --user
               │ └─843 (sd-pam)  
               └─session-c1.scope
                 ├─850 /usr/bin/dbus-launch --autolaunch b7696f2d7f534ff497e9e6f54a0d3fd0 --binary-syntax --close-st
                 ├─851 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                 ├─853 /usr/lib/at-spi2-core/at-spi-bus-launcher
                 ├─857 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
                 └─860 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session

Offline

#10 2014-10-28 15:50:46

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,353

Re: Cannot Connect with IPv4 Through Wired Interface

Is network manager configured to control the Wired network?  I have had my share of arguments with NM.  If it is, disable that and lets control it by hand until we get this figured out.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#11 2014-10-28 15:59:44

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

I deleted all ethernet connections in the nm gui. I'm now in this state:

mcli dev status
DEVICE       TYPE      STATE        CONNECTION 
docker0      bridge    connected    docker0    
wlp2s0       wifi      connected    Axxs    
eno1         ethernet  unavailable  --         
veth5195a85  ethernet  unmanaged    --         
lo           loopback  unmanaged    --

EDIT:

I've disabled NetworkManager and instead I'm using netctl and wifi-menu to connect wirelessly. The eno1 interface has now disappeared from ifconfig.

I've also realised that the dhcpcd service must be disabled for a wireless connection to work. Otherwise it brings up the wireless interface meaning that I cannot connect through wifi-menu. However, I don't have network access.

ICMP also does not appear to work (but reinstalling iputils fixed this):

➜  ~  ping -c 3 www.google.com
ping: icmp open socket: Operation not permitted
➜  ~  sudo dmesg | grep e1000e
[    5.063195] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    5.063199] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[    5.069030] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    5.069053] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[    5.338026] e1000e 0000:00:19.0 eth0: registered PHC clock
[    5.338031] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d4:be:d9:22:26:fb
[    5.338033] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    5.338067] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 3041FF-0FF
[    5.340240] e1000e 0000:00:19.0 eno1: renamed from eth0
[  308.923985] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[  309.024756] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[  331.167043] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  331.167057] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  335.724831] e1000e: eno1 NIC Link is Down
[  359.769298] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  359.769313] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  364.273902] e1000e: eno1 NIC Link is Down
[  392.139447] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  392.139460] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  396.670430] e1000e: eno1 NIC Link is Down
[  415.248122] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  415.248138] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  420.857055] e1000e: eno1 NIC Link is Down
[  447.488038] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  447.488055] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  452.209286] e1000e: eno1 NIC Link is Down
[  481.355118] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[  481.355134] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[  485.860970] e1000e: eno1 NIC Link is Down

I have also installed the dhcpcd-ui gui. It is intermittently flashing "eno1: cable plugged in" and "eno1: Cable unplugged".

➜  ~  sudo dhcpcd eno1
dhcpcd[2712]: version 6.5.1 starting
dhcpcd[2712]: DUID 00:01:00:01:19:ba:14:f3:d4:be:d9:22:26:fb
dhcpcd[2712]: eno1: IAID d9:22:26:fb
dhcpcd[2712]: eno1: soliciting an IPv6 router
dhcpcd[2712]: eno1: soliciting a DHCP lease
dhcpcd[2712]: eno1: carrier lost
dhcpcd[2712]: eno1: carrier acquired
dhcpcd[2712]: eno1: IAID d9:22:26:fb
dhcpcd[2712]: eno1: soliciting a DHCP lease
dhcpcd[2712]: eno1: soliciting an IPv6 router
dhcpcd[2712]: eno1: carrier lost
dhcpcd[2712]: timed out
dhcpcd[2712]: exited

Also given dhclient a shot:

➜  ~  sudo dhclient eno1  
➜  ~  sudo journalctl -xn 
-- Logs begin at Tue 2014-04-01 17:40:41 BST, end at Tue 2014-10-28 17:27:24 GMT. --
Oct 28 17:27:02 nickT_Arch kernel: e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
Oct 28 17:27:04 nickT_Arch dhclient[6777]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 7
Oct 28 17:27:07 nickT_Arch kernel: e1000e: eno1 NIC Link is Down
Oct 28 17:27:07 nickT_Arch kernel: dell_wmi: Received unknown WMI event (0x0)
Oct 28 17:27:11 nickT_Arch dhclient[6777]: No DHCPOFFERS received.
Oct 28 17:27:11 nickT_Arch dhclient[6777]: No working leases in persistent database - sleeping.
Oct 28 17:27:11 nickT_Arch sudo[6776]: pam_unix(sudo:session): session closed for user root
Oct 28 17:27:12 nickT_Arch kernel: dell_wmi: Received unknown WMI event (0x0)
Oct 28 17:27:24 nickT_Arch sudo[7035]: nick : TTY=pts/1 ; PWD=/home/nick ; USER=root ; COMMAND=/usr/bin/journalctl -
Oct 28 17:27:24 nickT_Arch sudo[7035]: pam_unix(sudo:session): session opened for user root by nick(uid=0)

Last edited by n_t (2014-10-28 17:30:17)

Offline

#12 2014-10-30 11:18:04

n_t
Member
Registered: 2013-02-01
Posts: 48

Re: Cannot Connect with IPv4 Through Wired Interface

I think I'm going to try booting from the arch initramfs usb and then I'll try dual-booting another distro to see if any of that makes a difference (i.e. to isolate it as a software issue). Unless there are better suggestions?

Offline

Pages: 1

Board footer

Powered by FluxBB