Link Speed after 188 update

Hello everyone
Since update 188 speeds are limited to 100mb even though I have gbits cards. I have this phenomenon on several ipfire.
No Qos, no configuration changed since the update, the phenomenon appeared after the update.
Am I the only one with this problem?
Best regards

What kind of NICs do you use? Which drivers are installed?

Have you checked the NIC / switch physical indicator to see if it’s negotiated only a 100Mb/s connection?

I’ve had a couple of slightly tempremantal (maybe because they were cheaper end of market) network equipment, where a small sample of Intel 1G NICs would randomly only sync at 100Mb after power cycling - reconnecting them almost always ended up getting a 1Gb/s link again.
This when using the normal kernel drivers, nothing special.

1 Like

HI,

I remember one command to view how to go speed and negotiation in interface.

ethtool green0

and

ethtool red0

In ssh.

Check this and say us something.

Regards.

2 Likes

Hi, so

ethtool green0 
        Settings for green0:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/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
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Transmit-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        master-slave cfg: preferred slave
        master-slave status: slave
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Link detected: yes

ethtool red0
        Settings for red0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/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
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

and also a speed test on green side

Regards

Hello
they both connect to 1g, one card is the motherboard, the other is an intel 1g card.
As I explained at the beginning, this problem appeared after the 188 update without any modification, and I have it on at least 2 ipfire.

1 Like

Would you please share the network card brand and chip?

Hi, here the complete configuration

lshw -short
H/W path           Device     Class          Description
========================================================
                              system         B560M DS3H (Default string)
/0                            bus            B560M DS3H
/0/0                          memory         64KiB BIOS
/0/3b                         memory         8GiB System Memory
/0/3b/0                       memory         [empty]
/0/3b/1                       memory         4GiB DIMM DDR4 Synchronous 2400 MHz
/0/3b/2                       memory         [empty]
/0/3b/3                       memory         4GiB DIMM DDR4 Synchronous 2400 MHz
/0/4c                         memory         256KiB L1 cache
/0/4d                         memory         1MiB L2 cache
/0/4e                         memory         6MiB L3 cache
/0/4f                         processor      Intel(R) Core(TM) i3-10105 CPU @ 3.
/0/100                        bridge         10th Gen Core Processor Host Bridge
/0/100/2                      display        CometLake-S GT2 [UHD Graphics 630]
/0/100/14                     bus            Tiger Lake-H USB 3.2 Gen 2x1 xHCI H
/0/100/14.2                   memory         RAM memory
/0/100/16                     communication  Tiger Lake-H Management Engine Inte
/0/100/17          scsi0      storage        Intel Corporation
/0/100/17/0.0.0    /dev/sda   disk           500GB WDC WD5003AZEX-0
/0/100/17/0.0.0/1  /dev/sda1  volume         128MiB EXT4 volume
/0/100/17/0.0.0/2  /dev/sda2  volume         15EiB Windows FAT volume
/0/100/17/0.0.0/3  /dev/sda3  volume         1GiB Linux swap volume
/0/100/17/0.0.0/4  /dev/sda4  volume         464GiB EXT4 volume
/0/100/1c                     bridge         Tiger Lake-H PCI Express Root Port
/0/100/1c/0        green0     network        RTL8111/8168/8211/8411 PCI Express
/0/100/1c.5                   bridge         Intel Corporation
/0/100/1c.5/0      red0       network        82574L Gigabit Network Connection
/0/100/1f                     bridge         B560 LPC/eSPI Controller
/0/100/1f/0                   system         PnP device PNP0c02
/0/100/1f/1                   printer        PnP device PNP0400
/0/100/1f/2                   communication  PnP device PNP0501
/0/100/1f/3                   system         PnP device PNP0c02
/0/100/1f/4                   generic        PnP device INT3f0d
/0/100/1f/5                   system         PnP device PNP0c02
/0/100/1f/6                   system         PnP device PNP0c02
/0/100/1f/7                   system         PnP device PNP0c02
/0/100/1f/8                   system         PnP device PNP0c02
/0/100/1f/9                   system         PnP device PNP0c02
/0/100/1f.3        card0      multimedia     Intel Corporation
/0/100/1f.3/0      input10    input          HDA Intel PCH Line Out
/0/100/1f.3/1      input11    input          HDA Intel PCH Front Headphone
/0/100/1f.3/2      input7     input          HDA Intel PCH Front Mic
/0/100/1f.3/3      input8     input          HDA Intel PCH Rear Mic
/0/100/1f.3/4      input9     input          HDA Intel PCH Line
/0/100/1f.4                   bus            Tiger Lake-H SMBus Controller
/0/100/1f.5                   bus            Tiger Lake-H SPI Controller
/1                            power          To Be Filled By O.E.M.
/2                 /dev/fb0   display        simple
/3                 input0     input          Sleep Button
/4                 input1     input          Power Button
/5                 input2     input          CHESEN PS2 to USB Converter
/6                 input3     input          CHESEN PS2 to USB Converter Mouse
/7                 input4     input          CHESEN PS2 to USB Converter System
/8                 input5     input          CHESEN PS2 to USB Converter Consume
/9                 input6     input          PC Speaker

Really strange/interesting.
Different network cards and different vendors/drivers.

That had never been a problem until now.

If the link speed is correct (1000mbps) I’d check BWM settings.

how to check or change this setting

I’m sorry, BWM for IpFire is uncorrect.

QoS is the way as IpFire manages the allocation of transport priority.

there no qos configured

Have you done speed tests between IPFire and a computer on your green network?
e.g. using iperf/fireperf

1 Like

Good advice!
Because measuring to an external target just gives the speed of the whole way, which isn’t greater than the slowest part.
“A chain is as strong as it’s weakest link”.

1 Like

Only due to sheer simplicity, IPfire’s speedtest-cli tool is usually a good way to check you are getting the expected performance on the red interface.

If it’s slower through the IPfire firewall/NAT there is either a mis-configuration or some other network issue somewhere.

2 Likes

I wouldn’t expect any problems with that either

What is the ISP advertised speed?

edit: nevermind. I didn’t notice GREEN. I saw the Speedtest.net and assumed you were testing RED. BTW, how did you use Speedtest.net to test GREEN speed? I thought that service was specifically for testing the WAN side, not LAN?

1 Like

I’ve checked with my system.
I also can’t get more than about 100MBit/s. With or without QOS.
My WAN speed is 250MBit/s. The speed test of my ISP ( Vodafone ) gives 250MBit to my cable modem and ~100MBit to my desktop ( same speed as measured by speedtest-cli tool ).

1 Like