Can.t maintain wired connection

bsth123 · 05-02-2017, 01:09 PM

I'm having problems with wireless so I'm using a wired connection. The problem is it keeps dropping my wired connection. If tell it to start I get the message that it's already connected so I have to restart and then it works and then it drops the connection again. H

Code:

bash-4.3# /etc/rc.d/rc.inet1 restart
sending signal ARLM to pid 24329
waiting for pid 24329 to exit
Polling for DHCP server on interface eth0:
eth0: adding address fe80::8eef:b7ac:592e:6d56
eth0: waiting for carrier
eth0: carrier acquired
DUID 00:01:00:01:20:9a:2c:ce:20:47:47:4f:fd:8d
eth0: IAID 47:4f:fd:8d
eth0: carrier lost
eth0: deleting address fe80::8eef:b7ac:592e:6d56
eth0: carrier acquired
eth0: adding address fe80::8eef:b7ac:592e:6d56
eth0: IAID 47:4f:fd:8d
eth0: soliciting an IPv6 router
eth0: rebinding lease of 192.168.0.4
eth0: Router Advertisement from fe80::d2b2:c4ff:fe4c:1c09
eth0: adding address 2605:6001:f180:ad00:ebe4:d72b:70ca:7a53/64
eth0: adding route to 2605:6001:f180:ad00::/64
eth0: adding default route via fe80::d2b2:c4ff:fe4c:1c09
eth0: soliciting a DHCPv6 lease
eth0: REPLY6 received from fe80::d2b2:c4ff:fe4c:1c09
eth0: adding address 2605:6001:f180:ad00::2/128
eth0: renew in 900 seconds, rebind in 1350 seconds
forked to background, child pid 25072

And ifconfig

Code:

bash-4.3# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.4  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 2605:6001:f180:ad00:ebe4:d72b:70ca:7a53  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::8eef:b7ac:592e:6d56  prefixlen 64  scopeid 0x20<link>
        inet6 2605:6001:f180:ad00::2  prefixlen 128  scopeid 0x0<global>
        inet6 2605:6001:f180:ad00:71e8:7b52:22fa:3ab2  prefixlen 64  scopeid 0x0<global>
        ether 20:47:47:4f:fd:8d  txqueuelen 1000  (Ethernet)
        RX packets 206276  bytes 179736332 (171.4 MiB)
        RX errors 0  dropped 30  overruns 0  frame 0
        TX packets 164264  bytes 26411942 (25.1 MiB)
        TX errors 0  dropped 3 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 1  (Local Loopback)
        RX packets 10574  bytes 830672 (811.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10574  bytes 830672 (811.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 18:3d:a2:e0:8c:dd  txqueuelen 1000  (Ethernet)
        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

I'm not sure what other information would be beneficial.

Didier Spaier · 05-02-2017, 02:09 PM

It can be a connector not securely fixed. Also, if you always use the same IP address you could consider setting this fixed IP in netconfig. Or use NetworkManager that automatically reconnects if you plug off then on the Ethernet connector.

bsth123 · 05-02-2017, 03:48 PM

This is a new laptop so I would have no idea how to check a connector. Network Manager is not working properly. The icon shows up in the task bar but it shows no connections. I went to start it and I got the message that it was already connected. But it shows no connection or any of my networks. As far as my ip my ISP uses dhcp. But now that you mention it I wonder about network manager. Any idea how to troubleshoot it? Thanks

Didier Spaier · 05-02-2017, 03:56 PM

Juts run netconfig as root in a terminal and when asked choose NetworkManager as configuration mode.

frankbell · 05-02-2017, 08:32 PM

The oldest hardware troubleshooting trick I know is to swap out the suspect cable (or mouse or whatever) with a device is known to work properly. That tends to provide a certainty about hardware that mucking about with software cannot.

burdi01 · 05-03-2017, 07:48 AM

Are you looking for an IPv4 or an IPv6 connection?
If it is the former then test with NetworkManager's wired connection IPv6 method set to "Ignore".

bsth123 · 05-03-2017, 01:48 PM

I want all my connections to show up like they did before I reinstalled. Sorry!

drgibbon · 05-04-2017, 07:39 AM

Quote:

Originally Posted by bsth123

I'm having problems with wireless so I'm using a wired connection. The problem is it keeps dropping my wired connection.

My wired connection would drop out continuously until I changed the default DHCP client from dhcpcd to dhclient. Might be worth a try? The setting is in /etc/NetworkManager/conf.d/00-dhcp-client.conf. You'd have to do a;

Code:

/etc/rc.d/rc.networkmanager restart

after making any changes I think.

bsth123 · 05-04-2017, 08:52 AM

Quote:

Originally Posted by drgibbon

My wired connection would drop out continuously until I changed the default DHCP client from dhcpcd to dhclient. Might be worth a try? The setting is in /etc/NetworkManager/conf.d/00-dhcp-client.conf. You'd have to do a;

Code:

/etc/rc.d/rc.networkmanager restart

after making any changes I think.

Thanks but that's not the problem anymore. I can't see any of my connections including the wired one. I don't know why network manager can't detect them.