Hello!
Sorry for the English, google translator did it. : D
There is a speed problem with the internal network.
The connection is 10g, but the speed is only 4-5g …
Debian server - ipfire
[root @ wrouter ~] # iperf3 -c 192.168.2.241
Connecting to host 192.168.2.241, port 5201
[5] local 192.168.2.1 port 36002 connected to 192.168.2.241 port 5201
[ID] Interval Transfer Bitrate Retr Cwnd
[5] 0.00-1.00 sec 435 MBytes 3.64 Gbits / sec 0 503 KBytes
[5] 1.00-2.00 sec 552 MBytes 4.63 Gbits / sec 0 611 KBytes
[5] 2.00-3.00 sec 542 MBytes 4.55 Gbits / sec 0 509 KBytes
[5] 3.00-4.00 sec 549 MBytes 4.61 Gbits / sec 0 648 KBytes
[5] 4.00-5.00 sec 562 MBytes 4.72 Gbits / sec 1,503 KBytes
[5] 5.00-6.00 sec 568 MBytes 4.76 Gbits / sec 0 543 KBytes
[5] 6.00-7.00 sec 572 MBytes 4.81 Gbits / sec 0 535 KBytes
[5] 7.00-8.00 sec 570 MBytes 4.77 Gbits / sec 0 628 KBytes
[5] 8.00-9.00 sec 568 MBytes 4.77 Gbits / sec 0 526 KBytes
[5] 9.00-10.00 sec 569 MBytes 4.76 Gbits / sec 0 571 KBytes
[ID] Interval Transfer Bitrate Retr
[5] 0.00-10.00 sec 5.36 GBytes 4.60 Gbits / sec 1 sender
[5] 0.00-10.00 sec 5.36 GBytes 4.60 Gbits / sec receiver
the speed is acceptable as a server but not perfect
ipfire server - debian client
[root @ wrouter ~] # iperf3 -s
Server listening on 5201 (test # 1)
Accepted connection from 192.168.2.241, port 36042
[5] local 192.168.2.1 port 5201 connected to 192.168.2.241 port 36044
[ID] Interval Transfer Bitrate
[5] 0.00-1.00 sec 779 MBytes 6.53 Gbits / sec
[5] 1.00-2.00 sec 1.10 GBytes 9.42 Gbits / sec
[5] 2.00-3.00 sec 1.10 GBytes 9.41 Gbits / sec
[5] 3.00-4.00 sec 1.09 GBytes 9.40 Gbits / sec
[5] 4.00-5.00 sec 1.08 GBytes 9.32 Gbits / sec
[5] 5.00-6.00 sec 1.10 GBytes 9.41 Gbits / sec
[5] 6.00-7.00 sec 1.10 GBytes 9.42 Gbits / sec
[5] 7.00-8.00 sec 1.09 GBytes 9.40 Gbits / sec
[5] 8.00-9.00 sec 1.09 GBytes 9.40 Gbits / sec
[5] 9.00-10.00 sec 1.09 GBytes 9.40 Gbits / sec
[5] 10.00-10.00 sec 636 KBytes 8.66 Gbits / sec
[ID] Interval Transfer Bitrate
[5] 0.00-10.00 sec 10.6 GBytes 9.11 Gbits / sec receiver
IPS is enabled, but only on the RED0 device.
I made another machine with a clean ipfire installation and tested the network cards, cables, sfp + modules and the speeds were good there, they brought what was expected. The machine called wrouter, on the other hand, is slow.
Machine data:
[root @ wrouter ~] # uname -a
Linux wrouter.srv 5.15.6-ipfire # 1 SMP Thu Dec 23 00:55:02 GMT 2021 x86_64 Intel (R) Xeon (R) CPU E5-2630L v2 @ 2.40GHz GenuineIntel GNU / Linux
https://fireinfo.ipfire.org/profile/5abcd62380db781461fcb0d15918c42fcf533c66
[root @ wrouter ~] # lspci | grep Ethernet
01: 00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01: 00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01: 00.2 Ethernet Controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01: 00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
03: 00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 01)
48: 00.0 Ethernet controller: QLogic Corp. cLOM8214 1 / 10GbE Controller (rev 54)
48: 00.1 Ethernet controller: QLogic Corp. cLOM8214 1 / 10GbE Controller (rev 54)
[root @ wrouter ~] # ethtool green0
Settings for green0:
Supported ports: [TP FIBER]
Supported link modes: 10000baseT / Full
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 10000baseT / Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb / s
Duplex: Full
Auto-negotiation: off
Port: FIBER
PHYAD: 0
Transceiver: internal
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000000 (0)
Link detected: yes
[root @ wrouter ~] # ifconfig green0
green0: flags = 4163 <UP, BROADCAST, RUNNING, MULTICAST> mtu 1500
inet 192.168.2.1 netmask 255.255.255.0 broadcast 0.0.0.0
ether c4: 34: 6b: cc: c0: c8 txqueuelen 1000 (Ethernet)
RX packets 59750684 bytes 86829590819 (80.8 GiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 65483441 bytes 96707241490 (90.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 113
What should I do to look for the bug?