Announcement

Collapse
No announcement yet.

Dreadful network performance --- how to start?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Dreadful network performance --- how to start?

    My wife's computer runs W10 and I'm on the latest Neon. Both are connected by gigabit ethernet to a "modem" which is connected to our internet provider by a fiber network. My wife's computer gets much better network rates. I switched computers (only) just to make sure it's not the cabling and it isn't. She gets over 900 Mbs down and 700 up. I get 400 down and 350 up.

    It's very embarrassing.

    I have no idea where to start looking for network problems and would welcome any suggestions.
    'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

    #2
    Wifi? Wired?

    Which card?
    Maybe it needs a config edit.

    There are various ways to get the card info.
    https://www.cyberciti.biz/faq/linux-...cards-command/


    Comment


      #3
      Sorry I forgot to mention the n/w card. And thanks for the link -- very useful.

      I'm connected by wired gigabit ethernet to a "modem" and from there by fiber to the ISP.

      $ sudo lshw -class network
      *-network
      description: Ethernet interface
      product: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
      vendor: Realtek Semiconductor Co., Ltd.
      physical id: 0
      bus info: pci@0000:03:00.0
      logical name: enp3s0
      version: 0c
      serial: 40:8d:5c:77:34:78
      size: 1Gbit/s
      capacity: 1Gbit/s
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.14.0-37-generic duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.1.60 l
      atency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
      resources: irq:18 ioport:d000(size=256) memory:f7900000-f7900fff memory:f2100000-f2103fff


      cat /proc/net/dev
      Inter-| Receive | Transmit
      face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
      lo: 183044 1504 0 0 0 0 0 0 183044 1504 0 0 0 0 0 0
      enp3s0: 28247818 26722 0 11 0 0 0 228 2678633 12771 0 0 0 0 0 0
      I googled the driver and managed to extract this info:

      $ grep -i driver net-card.out
      configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.14.0-37-generic duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.1.60 l
      atency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
      jon@jon-desktop:~$ sudo su
      root@jon-desktop:/home/jon# for i in $(ls /sys/class/net); do
      echo $i '====================='
      ethtool -i $i
      done
      enp3s0 =====================
      driver: r8169
      version: 6.14.0-37-generic
      firmware-version: rtl8168g-2_0.0.1 02/06/13
      expansion-rom-version:
      bus-info: 0000:03:00.0
      supports-statistics: yes
      supports-test: no
      supports-eeprom-access: no
      supports-register-dump: yes
      supports-priv-flags: no
      lo =====================
      Cannot get driver information: Operation not supported
      This is not the latest driver, according to this. But it worked find up til a few weeks or months ago. Could a system update have caused an incompatibility? Not being an expert, I hesitate to start playing with drivers.
      'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

      Comment


        #4
        Originally posted by joneall View Post
        firmware=rtl8168g-2_0.0.1 02/06/1
        This *might* be useful.
        There is a *chance* that using the 8168-dkms might be an alternative but am unsure if this works in the 6.14 kernel.
        Also not completely sure if this is even useful for your specific card, or if there are any useful options to use to make the current driver behave properly.

        Don't forget the easy part of checking for a bad or damaged cable, etc.


        Comment

        Users Viewing This Topic

        Collapse

        There are 0 users viewing this topic.

        Working...
        X