Почему ethernet работает медленно?

Question

[error 404]

eth0 работает медленнее чем wlan0, дело не в кабеле.
ifconfig:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.254  netmask 255.255.255.0  broadcast 192.168.0.254
        inet6 fe80::81:4bff:feca:6fed  prefixlen 64  scopeid 0x20<link>
        ether 02:81:4b:ca:6f:ed  txqueuelen 1000  (Ethernet)
        RX packets 796  bytes 71376 (71.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2361  bytes 2996135 (2.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 40

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 1000  (Local Loopback)
        RX packets 95  bytes 7100 (7.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 95  bytes 7100 (7.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.2  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::76a8:92fd:de04:6ea  prefixlen 64  scopeid 0x20<link>
        ether 12:81:4b:ca:6f:ed  txqueuelen 1000  (Ethernet)
        RX packets 437  bytes 61832 (61.8 KB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 26  bytes 3446 (3.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Answer 1

[Vitaly Karasik]

1) Посмотрите на вывод "ifconfig" - на статистику ошибок
2) ethtool eth0 - может работает на неправильной скорости

Comments

[error 404]

ifconfig:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.254  netmask 255.255.255.0  broadcast 192.168.0.254
        inet6 fe80::81:4bff:feca:6fed  prefixlen 64  scopeid 0x20<link>
        ether 02:81:4b:ca:6f:ed  txqueuelen 1000  (Ethernet)
        RX packets 796  bytes 71376 (71.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2361  bytes 2996135 (2.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 40

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 1000  (Local Loopback)
        RX packets 95  bytes 7100 (7.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 95  bytes 7100 (7.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.2  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::76a8:92fd:de04:6ea  prefixlen 64  scopeid 0x20<link>
        ether 12:81:4b:ca:6f:ed  txqueuelen 1000  (Ethernet)
        RX packets 437  bytes 61832 (61.8 KB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 26  bytes 3446 (3.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[error 404]

ethtool:

Supported ports: [ TP AUI BNC MII FIBRE ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x0000003f (63)
                               drv probe link timer ifdown ifup
        Link detected: yes

[Adamos]

Артём Шупиков, ifconfig в вопрос вынеси. Если, конечно, заинтересован в ответе.
Он, кстати, показывает, что оба интерфейса смотрят в одну сеть - видимо, в этом и проблема.

[error 404]

Adamos, раньше было так же, я просто с таким интернетом еле-еле через ssh подключился к wifi

[Vitaly Karasik]

Артём Шупиков,
Я бы опустил wlan0 временно и проверил не стало ли лучше.
Согласен с Adamos - одинаковая сеть на двух интерфейсах выглядиит очень странно.

[hint000]

Артём Шупиков, ещё и странное broadcast 192.168.0.254 - как бы намекает на небрежность настройки сети, и фиг знает какие косяки, если копнуть глубже.

Answer 2

[Everything_is_not_so_bad]

Попробуй проверить программой Nethogs.
https://www.networkworld.com/article/3196138/whos-...
https://www.binarytides.com/linux-commands-monitor...