Ubuntu 16.06.3 Desktop network errors and overruns

Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I changed my network connection to manual and configured ip address, mask, and gateway. It says it connected but all i get is errors and overruns. I rchangeded back to auto DHCP and it will not connect. I tried both NIC's with the same result.
$ifconfig -a
enp0s16 Link encap:Ethernet HWaddr 00:1b:fc:66:c7:5d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp0s17 Link encap:Ethernet HWaddr 00:1b:fc:66:cb:7f
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b216:acc8:71a8:5547/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1300 Metric:1
RX packets:0 errors:12360 dropped:0 overruns:12360 frame:0
TX packets:0 errors:0 dropped:41 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:217041 (217.0 KB) TX bytes:217041 (217.0 KB)
wlx0015af19bb85 Link encap:Ethernet HWaddr 00:15:af:19:bb:85
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8762:961b:59fc:6c8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2491 errors:0 dropped:1 overruns:0 frame:0
TX packets:2241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1039609 (1.0 MB) TX bytes:288780 (288.7 KB)
$dmesg |grep enp0s17
[ 2.258053] forcedeth 0000:00:11.0 enp0s17: renamed from eth1
[ 28.918159] IPv6: ADDRCONF(NETDEV_UP): enp0s17: link is not ready
[ 28.918684] forcedeth 0000:00:11.0 enp0s17: MSI enabled
[ 39.824025] NETDEV WATCHDOG: enp0s17 (forcedeth): transmit queue 0 timed out
[ 39.824120] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
[ 41.380091] device enp0s17 entered promiscuous mode
[ 44.832019] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
$sudo dmidecode -t 2
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N32-SLI DELUXE
Version: 1.XX
Serial Number: 123456789000
$lspci -k
00:10.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
networking nvidia
add a comment |Â
up vote
0
down vote
favorite
I changed my network connection to manual and configured ip address, mask, and gateway. It says it connected but all i get is errors and overruns. I rchangeded back to auto DHCP and it will not connect. I tried both NIC's with the same result.
$ifconfig -a
enp0s16 Link encap:Ethernet HWaddr 00:1b:fc:66:c7:5d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp0s17 Link encap:Ethernet HWaddr 00:1b:fc:66:cb:7f
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b216:acc8:71a8:5547/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1300 Metric:1
RX packets:0 errors:12360 dropped:0 overruns:12360 frame:0
TX packets:0 errors:0 dropped:41 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:217041 (217.0 KB) TX bytes:217041 (217.0 KB)
wlx0015af19bb85 Link encap:Ethernet HWaddr 00:15:af:19:bb:85
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8762:961b:59fc:6c8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2491 errors:0 dropped:1 overruns:0 frame:0
TX packets:2241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1039609 (1.0 MB) TX bytes:288780 (288.7 KB)
$dmesg |grep enp0s17
[ 2.258053] forcedeth 0000:00:11.0 enp0s17: renamed from eth1
[ 28.918159] IPv6: ADDRCONF(NETDEV_UP): enp0s17: link is not ready
[ 28.918684] forcedeth 0000:00:11.0 enp0s17: MSI enabled
[ 39.824025] NETDEV WATCHDOG: enp0s17 (forcedeth): transmit queue 0 timed out
[ 39.824120] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
[ 41.380091] device enp0s17 entered promiscuous mode
[ 44.832019] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
$sudo dmidecode -t 2
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N32-SLI DELUXE
Version: 1.XX
Serial Number: 123456789000
$lspci -k
00:10.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
networking nvidia
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I changed my network connection to manual and configured ip address, mask, and gateway. It says it connected but all i get is errors and overruns. I rchangeded back to auto DHCP and it will not connect. I tried both NIC's with the same result.
$ifconfig -a
enp0s16 Link encap:Ethernet HWaddr 00:1b:fc:66:c7:5d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp0s17 Link encap:Ethernet HWaddr 00:1b:fc:66:cb:7f
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b216:acc8:71a8:5547/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1300 Metric:1
RX packets:0 errors:12360 dropped:0 overruns:12360 frame:0
TX packets:0 errors:0 dropped:41 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:217041 (217.0 KB) TX bytes:217041 (217.0 KB)
wlx0015af19bb85 Link encap:Ethernet HWaddr 00:15:af:19:bb:85
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8762:961b:59fc:6c8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2491 errors:0 dropped:1 overruns:0 frame:0
TX packets:2241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1039609 (1.0 MB) TX bytes:288780 (288.7 KB)
$dmesg |grep enp0s17
[ 2.258053] forcedeth 0000:00:11.0 enp0s17: renamed from eth1
[ 28.918159] IPv6: ADDRCONF(NETDEV_UP): enp0s17: link is not ready
[ 28.918684] forcedeth 0000:00:11.0 enp0s17: MSI enabled
[ 39.824025] NETDEV WATCHDOG: enp0s17 (forcedeth): transmit queue 0 timed out
[ 39.824120] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
[ 41.380091] device enp0s17 entered promiscuous mode
[ 44.832019] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
$sudo dmidecode -t 2
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N32-SLI DELUXE
Version: 1.XX
Serial Number: 123456789000
$lspci -k
00:10.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
networking nvidia
I changed my network connection to manual and configured ip address, mask, and gateway. It says it connected but all i get is errors and overruns. I rchangeded back to auto DHCP and it will not connect. I tried both NIC's with the same result.
$ifconfig -a
enp0s16 Link encap:Ethernet HWaddr 00:1b:fc:66:c7:5d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp0s17 Link encap:Ethernet HWaddr 00:1b:fc:66:cb:7f
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b216:acc8:71a8:5547/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1300 Metric:1
RX packets:0 errors:12360 dropped:0 overruns:12360 frame:0
TX packets:0 errors:0 dropped:41 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:217041 (217.0 KB) TX bytes:217041 (217.0 KB)
wlx0015af19bb85 Link encap:Ethernet HWaddr 00:15:af:19:bb:85
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8762:961b:59fc:6c8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2491 errors:0 dropped:1 overruns:0 frame:0
TX packets:2241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1039609 (1.0 MB) TX bytes:288780 (288.7 KB)
$dmesg |grep enp0s17
[ 2.258053] forcedeth 0000:00:11.0 enp0s17: renamed from eth1
[ 28.918159] IPv6: ADDRCONF(NETDEV_UP): enp0s17: link is not ready
[ 28.918684] forcedeth 0000:00:11.0 enp0s17: MSI enabled
[ 39.824025] NETDEV WATCHDOG: enp0s17 (forcedeth): transmit queue 0 timed out
[ 39.824120] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
[ 41.380091] device enp0s17 entered promiscuous mode
[ 44.832019] forcedeth 0000:00:11.0 enp0s17: Got tx_timeout. irq status: 00000020
$sudo dmidecode -t 2
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N32-SLI DELUXE
Version: 1.XX
Serial Number: 123456789000
$lspci -k
00:10.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. MCP55 Ethernet
Kernel driver in use: forcedeth
Kernel modules: forcedeth
networking nvidia
networking nvidia
asked Feb 25 at 18:29
TonyD
61
61
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21
add a comment |Â
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009696%2fubuntu-16-06-3-desktop-network-errors-and-overruns%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I figured it out. I had a router in the network that was creating the issue. As soon as i took it off line the problem went away. I currently check what in the router is causing the problem.
â TonyD
Feb 25 at 19:21