10gb wan issue?

[burt (Bertel Schmitt)]

Qotom Q11032H6-S13 N355

[pscar13 (Phil SCAR)]

This is indeed the model I tested, but the N305.

I returned it after my unsatisfactory tests.

FYI, it’s more expensive now with Black Friday and the so-called AliExpress promotions.
Black Friday is a scam!

[burt (Bertel Schmitt)]

There is next to no difference between the 305 and the 355. You should have tested it some more with iperf3.

[ms (Michael Tremer)]

@burt

You really should familiarize yourself with the hardware used by by Joe IpFire user, and you should try not to throw shade on their hardware when they have a software problem. Recommending “server grade” hardware to that crowd is not helpful. Likewise unhelpful is gaslighting against the Marvell chip if you have no experience with it. We will get to that chip below.

This is a very interesting allegation that you are making against me.

Clearly you failed to understand what I was saying.

@burt

With IpFire, the results were:
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.0 GBytes 9.42 Gbits/sec 49 sender
[ 5] 0.00-10.00 sec 11.0 GBytes 9.41 Gbits/sec receiver

This is the maximum throughput that is possible in that configuration. You started to compare apples with pears here.

My statement still stands. With such oversized CPUs, you won’t have a problem with the NICs offloading any work to the CPU. However, a Threadripper system as a firewall is by far not the norm.

[current_user]

meh! just OT

i really hope that @skyeci73 returns
with an explanation why ipf performs
so obviously bad on hardware that was
performing good with other distros

[burt (Bertel Schmitt)]

You should have read the rest of the post. With jumbo frames, the iperf3 throughput went up to 9.8. Also, you need to educate your customers on the impact of IDS.

[pscar13 (Phil SCAR)]

@burt

I have a similar box as yours, possible the same (Qotom?), except that mine has a 355 CPU vs your 305, which really should not matter. Your box and your NICs are fine., don’t let them dissuade you,

With iperf3, my box gets:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.0 GBytes 9.42 Gbits/sec 49 sender
[ 5] 0.00-10.00 sec 11.0 GBytes 9.41 Gbits/sec receiver

And when I switch on jumbo frames, it gets:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec 14 sender
[ 5] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec receiver

What might have cut your performance in half is IPS/IDS. That sends any affordable router to its knees.

Were your tests performed with both AQC113 cards connected via IPFire from the LAN (Green) to the WAN (Red) up and Down ?

Or only from IPFire to LAN and IPFire to WAN ?

I’ll try again.

[burt (Bertel Schmitt)]

Both AQC113 connected. One to WAN. One to LAN. Jumbo frames enabled. Important: No IDS/IPS.

Most importantly, you need a performant server on the other side of your iperf3 test. The test won’t go faster than what BOTH client and server allow.

Even more importantly: Forget Speedtest. It will give you the speed between your machine and another server via the public network, and it will be as fast as the slowest link in this chain.. For your network speed and nothing else, you need iperf3.

[pscar13 (Phil SCAR)]

I can confirm there’s a problem with IPFire routing for the 10Gbps connection.

I ran tests with my Qotom Q11032H6 S13 miniPC, equipped with a Twin Lake-N Core i3 N355 processor 8GB RAM and two NICS Marvell AQC113 10 Gigabit LAN interfaces.

On the WAN (Red) side, a PC A: Windows 11 I7-12700KF 32GB RAM with NIC Marvell AQC113 10 Gigabit LAN (Antivirus and firewall disabled) 192.168.1.254
On the LAN (Green) side, a PC B: Windows 11 I5-12400 16GB RAM with NIC Marvell AQC113 10 Gigabit LAN (Antivirus and firewall disabled) 192.168.20.32

I ran several iperf3 tests:
PC A → PC B direct: 9.5 Gbps
PC A → IPFire Red: 9.5 Gbps
PC B → IPFire Green 9.5 Gbps
PC A → Ipfire → PC B: < 4 Gbps (IPFire 2.29 CU 196/197/198 tests, initial installation with no services enabled)

I performed the same test with Vyos:
PC A → Vyos → PC B: 9.5 Gbps

The iperf test:
iperf3 -c 192.168.1.254 -P8 (-R)
The 8 CPUs are never saturated.

Why IPFire divides bandwidth by 2 (and more) but vyos no ?

[porkyle (mapi)]

Maybe issue is with driver?

WARNING:
AQtion driver is built with the LRO (Large Receive Offload) feature enabled
by default.
This option offers the lowest CPU utilization for receives, but it is completely
incompatible with routing/ip forwarding and bridging.
If you need ip forwarding or bridging, please make sure to disable LRO using the
compile time options described in the LRO section below.
NB! If LRO is enabled, attempts to use ip forwarding or bridging can result in
low throughput or even a kernel panic.

README.txt

[pscar13 (Phil SCAR)]

I repeated the test with

ethtool -K red0 lro off
ethtool -K green0 lro off

No improvement.

I tested with IPFire 2.29 CU 199 (Latest Build) and saw a slight improvement :
4.55 Gbps.

Any other ideas?

[current_user]

interesting

now there are two examples with a direct comparison
of the very same hardware just different distros
and since the two examples are different too it is
a nice problem to solve

@pscar13
can you post/compare the ip/lspci/ethtool outputs
from both distros
let us see if we find a thousend and one reason

[burt (Bertel Schmitt)]

Asa noted by pscar13, LRO (along with other sundry offloads) can be switched on/off with ethtool. No recompiles needed.

[burt (Bertel Schmitt)]

@pscar13

Any other ideas?

I recommend ditching the kludgey IpFire and to go with VyOs. VyOs is a bit harder on the neophyte, but worth the effort. That’s what I did after evaluating both. I was encouraged by the arrogant posts of IpFire’s founder.

[tratru]

Hi @burt,
I think it’s unfair and unethical to invite a user to a competing product because of personal issues with a user.
I won’t add anything else.

[burt (Bertel Schmitt)]

@tratru

I won’t add anything else.

It’s better that way.

[pscar13 (Phil SCAR)]

This isn’t the answer I was expecting.

I don’t intend to abandon IPFire; I just want to try and understand why IPFire won’t allow the use of this machine.

Here are the two console outputs requested by @current_user.

vyos

vyos@vyos# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:32:30 brd ff:ff:ff:ff:ff:ff
    altname enp4s0
    inet6 fe80::227c:14ff:fef8:3230/64 scope link tentative
       valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:34:ea brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet 192.168.1.200/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::227c:14ff:fef8:34ea/64 scope link tentative
       valid_lft forever preferred_lft forever
4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:34:eb brd ff:ff:ff:ff:ff:ff
    altname enp2s0
    inet 192.168.20.1/24 brd 192.168.20.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::227c:14ff:fef8:34eb/64 scope link tentative
       valid_lft forever preferred_lft forever
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:32:31 brd ff:ff:ff:ff:ff:ff
    altname enp5s0
    inet6 fe80::227c:14ff:fef8:3231/64 scope link tentative
       valid_lft forever preferred_lft forever
6: pim6reg@NONE: <NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue state UNKNOWN group default qlen 1000
    link/pimreg
[edit]
vyos@vyos# lspci
00:00.0 Host bridge: Intel Corporation Device 4617
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [Intel Graphics]
00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant
00:0d.0 USB controller: Intel Corporation Alder Lake-N Thunderbolt 4 USB Controller
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:15.0 Serial bus controller: Intel Corporation Device 54e8
00:16.0 Communication controller: Intel Corporation Alder Lake-N PCH HECI Controller
00:1a.0 SD Host controller: Intel Corporation Device 54c4
00:1c.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1c.2 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1c.6 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1d.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1d.1 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.4 SMBus: Intel Corporation Alder Lake-N SMBus
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-N SPI (flash) Controller
01:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)
02:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)
03:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1202 (rev 01)
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
[edit]
vyos@vyos#
vyos@vyos# ethtool -k eth0
Features for eth0:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
        tx-tcp-segmentation: on
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: off [fixed]
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: offoad: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]

vyos@vyos# ethtool -k eth1
Features for eth1:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
        tx-tcp-segmentation: on
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: off [fixed]
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]

vyos@vyos# ethtool -i eth0
driver: atlantic
version: 6.6.114-vyos
firmware-version: 1.3.37
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

vyos@vyos# ethtool -i eth1
driver: atlantic
version: 6.6.114-vyos
firmware-version: 1.3.37
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

vyos@vyos# ethtool -g eth0
Ring parameters for eth0:
Pre-set maximums:
RX:                     8184
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     8184
TX push buff len:       n/a
Current hardware settings:
RX:                     2048
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     4096
RX Buf Len:             n/a
CQE Size:               n/a
TX Push:                off
RX Push:                off
TX push buff len:       n/a
TCP data split:         n/a

vyos@vyos# ethtool -g eth1
Ring parameters for eth1:
Pre-set maximums:
RX:                     8184
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     8184
TX push buff len:       n/a
Current hardware settings:
RX:                     2048
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     4096
RX Buf Len:             n/a
CQE Size:               n/a
TX Push:                off
RX Push:                off
TX push buff len:       n/a
TCP data split:         n/a

ipfire

[root@ipfire ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:32:30 brd ff:ff:ff:ff:ff:ff
3: red0: <NO-CARRIER,BROADCAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:34:ea brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.200/24 scope global red0
       valid_lft forever preferred_lft forever
4: blue0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 20:7c:14:f8:32:31 brd ff:ff:ff:ff:ff:ff
    inet 192.168.30.1/24 scope global blue0
       valid_lft forever preferred_lft forever
5: green0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 20:7c:14:f8:34:eb brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.1/24 scope global green0
       valid_lft forever preferred_lft forever
[root@ipfire ~]#
[root@ipfire ~]# lspci
00:00.0 Host bridge: Intel Corporation Device 4617
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [Intel Graphics]
00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant
00:0d.0 USB controller: Intel Corporation Alder Lake-N Thunderbolt 4 USB Controller
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 Gen 2x1 (10 Gb/s) xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:15.0 Serial bus controller: Intel Corporation Alder Lake-N PCH I2C Controller
00:16.0 Communication controller: Intel Corporation Alder Lake-N PCH HECI Controller
00:1a.0 SD Host controller: Intel Corporation Alder Lake-N eMMC Controller
00:1c.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #1
00:1c.2 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #3
00:1c.6 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #7
00:1d.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #9
00:1d.1 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #10
00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.4 SMBus: Intel Corporation Alder Lake-N SMBus
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-N SPI (flash) Controller
01:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)
02:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)
03:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1202 (DRAM-less) (rev 01)
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)

[root@ipfire ~]# ethtool -k red0
Features for red0:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
        tx-tcp-segmentation: on
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: off [fixed]
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: on
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]
[root@ipfire ~]#
[root@ipfire ~]# ethtool -k green0
Features for green0:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
        tx-tcp-segmentation: on
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: off [fixed]
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: on
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]
[root@ipfire ~]#
[root@ipfire ~]# ethtool -i red0
driver: atlantic
version: 6.12.41-ipfire
firmware-version: 1.3.37
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
[root@ipfire ~]# ethtool -i green0
driver: atlantic
version: 6.12.41-ipfire
firmware-version: 1.3.37
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

[root@ipfire ~]# ethtool -g red0
Ring parameters for red0:
RX:                     8184
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     8184
TX push buff len:       n/a
HDS thresh:             n/a
RX:                     2048
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     4096
RX Buf Len:             n/a
CQE Size:               n/a
TX Push:                off
RX Push:                off
TX push buff len:       n/a
TCP data split:         n/a
HDS thresh:             n/a

[root@ipfire ~]# ethtool -g green0
Ring parameters for green0:
RX:                     8184
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     8184
TX push buff len:       n/a
HDS thresh:             n/a
RX:                     2048
RX Mini:                n/a
RX Jumbo:               n/a
TX:                     4096
RX Buf Len:             n/a
CQE Size:               n/a
TX Push:                off
RX Push:                off
TX push buff len:       n/a
TCP data split:         n/a
HDS thresh:             n/a

[xperimental (Terry)]

@pscar13

This is a fake news; you cannot obtain these values ​​through IPFire with this configuration

Why is that? The device exists.

Qotom 10Gbase-T Mini PC with Intel N355 Review

[pscar13 (Phil SCAR)]

@xperimental

Why is that? The device exists.

I’m not saying the device doesn’t exist, since I just tested it.

10gb wan issue?

I can confirm there’s a problem with IPFire routing for the 10Gbps connection. I ran tests with my Qotom Q11032H6 S13 miniPC, equipped with a Twin Lake-N Core i3 N355 processor 8GB RAM and two NICS Marvell AQC113 10 Gigabit LAN interfaces. On the WAN (Red) side, a PC A: Windows 11 I7-12700KF 32GB RAM with NIC Marvell AQC113 10 Gigabit LAN (Antivirus and firewall disabled) 192.168.1.254 On the LAN (Green) side, a PC B: Windows 11 I5-12400 16GB RAM with NIC Marvell AQC113 10 Gigabit LAN (Antivi…

I’m saying that @burt information is incorrect; you can’t get 10Gbps through IPFire with this device.

[current_user]

@pscar13
so there are some/huge/significant differences when comparing
both outputs. especially the kernel driver for eth0/red0
also some parameters of ethtool
have you tried to alter these on ipf

@topic
indeed the data from @burt confuses me also