10Gbe network interfaces not working on the Qnap Qhora 301w about openmptcprouter

[Ysurac]

Can you try the 6.6 snapshot release ? https://snapshots.openmptcprouter.com/6.6/

[T0p4Ze]

Can you try the 6.6 snapshot release ? https://snapshots.openmptcprouter.com/6.6/

So I tested some progress but not everywhere
The 10 Gbe lan works but I have very low bandwidth and very high latency compared to1 Gbe which is correct but which does not reach the speed that I had with the old version
The 10 Gbe wan is partially detected but no internet
/

[Ysurac]

What is the result of ip a and ethtool 10g-1 via SSH on the router ?

[T0p4Ze]

What is the result of ip a and ethtool 10g-1 via SSH on the router ?

root@OpenMPTCProuter:~# 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 ::1/128 scope host proto kernel_lo
valid_lft forever preferred_lft forever
2: miireg: <> mtu 0 qdisc noop state DOWN group default qlen 1000
link/netrom
3: lan4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 24:5e:be:52:90:93 brd ff:ff:ff:ff:ff:ff
inet 192.168.8.2/24 brd 192.168.8.255 scope global lan4
valid_lft forever preferred_lft forever
4: lan3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 24:5e:be:52:90:94 brd ff:ff:ff:ff:ff:ff
5: lan2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 24:5e:be:52:90:95 brd ff:ff:ff:ff:ff:ff
6: lan1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 24:5e:be:52:90:96 brd ff:ff:ff:ff:ff:ff
7: 10g-1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 24:5e:be:52:90:97 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global 10g-1
valid_lft forever preferred_lft forever
8: 10g-2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 24:5e:be:52:90:98 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.1/24 brd 192.168.100.255 scope global 10g-2
valid_lft forever preferred_lft forever
inet6 fe80::265e:beff:fe52:9098/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
9: ip6tnl0@NONE: mtu 1452 qdisc noop state DOWN group default qlen 1000
link/tunnel6 :: brd :: permaddr 2ca:3c92:a5df::
10: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
11: gre0@NONE: mtu 1476 qdisc noop state DOWN group default qlen 1000
link/gre 0.0.0.0 brd 0.0.0.0
12: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
13: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
14: ip6gre0@NONE: mtu 1448 qdisc noop state DOWN group default qlen 1000
link/gre6 :: brd :: permaddr 8a92:be58:2249::
15: teql0: mtu 1500 qdisc noop state DOWN group default qlen 100
link/void
51: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1420 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet 10.255.252.2/24 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::a266:b621:f393:a3ec/64 scope link stable-privacy proto kernel_ll
valid_lft forever preferred_lft forever
54: ifb4lan2: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
link/ether 1e:1b:22:37:0c:c3 brd ff:ff:ff:ff:ff:ff
57: ifb4lan3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
link/ether 0e:5e:ad:bc:8d:28 brd ff:ff:ff:ff:ff:ff
60: ifb410g-1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
link/ether c6:5e:08:d3:8d:a1 brd ff:ff:ff:ff:ff:ff

[T0p4Ze]

I forgot to post ethtool 10g-1 @Ysurac

root@OpenMPTCProuter:~# ethtool 10g-1
Settings for 10g-1:
Supported ports: [ ]
Supported link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
1000baseKX/Full
10000baseKX4/Full
10000baseKR/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
1000baseKX/Full
10000baseKX4/Full
10000baseKR/Full
2500baseT/Full
5000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 8
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes

[Ysurac]

All seems ok here.
What do you have when you do a ping -B -I 10g-1 192.168.0.254 ?

[T0p4Ze]

ping -B -I 10g-1 192.168.0.254

root@OpenMPTCProuter:~# ping -B -I 10g-1 192.168.0.254
ping: bind: Address not available

For information, I tried 10g-1 and 10g-2 on openwrt and it works

[Ysurac]

Strange that ping is not able to bind to the interface, maybe due to the "-".
What is the result if you try ping -B -I 192.168.0.1 192.168.0.254 and if this doesn't work ping -I 10g-1 192.168.0.254 ?

[T0p4Ze]

root@OpenMPTCProuter:~# ping -B -I 192.168.0.1 192.168.0.254
PING 192.168.0.254 (192.168.0.254) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=0.282 ms
64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=0.226 ms
64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=0.217 ms
64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=0.217 ms
64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=0.289 ms
64 bytes from 192.168.0.254: icmp_seq=6 ttl=64 time=0.240 ms
64 bytes from 192.168.0.254: icmp_seq=7 ttl=64 time=0.210 ms
64 bytes from 192.168.0.254: icmp_seq=8 ttl=64 time=0.261 ms
64 bytes from 192.168.0.254: icmp_seq=9 ttl=64 time=0.232 ms
64 bytes from 192.168.0.254: icmp_seq=10 ttl=64 time=0.255 ms
^C
--- 192.168.0.254 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9389ms
rtt min/avg/max/mdev = 0.210/0.242/0.289/0.026 ms

root@OpenMPTCProuter:~# ping -I 10g-1 192.168.0.254
PING 192.168.0.254 (192.168.0.254) from 10.0.0.0 10g-1: 56(84) bytes of data.
64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=0.271 ms
64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=0.265 ms
64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=0.191 ms
64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=0.257 ms
64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=0.242 ms
64 bytes from 192.168.0.254: icmp_seq=6 ttl=64 time=0.255 ms
64 bytes from 192.168.0.254: icmp_seq=7 ttl=64 time=0.243 ms
64 bytes from 192.168.0.254: icmp_seq=8 ttl=64 time=0.243 ms
64 bytes from 192.168.0.254: icmp_seq=9 ttl=64 time=0.256 ms
64 bytes from 192.168.0.254: icmp_seq=10 ttl=64 time=0.251 ms
^C
--- 192.168.0.254 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9334ms
rtt min/avg/max/mdev = 0.191/0.247/0.271/0.020 ms

[Ysurac]

So the problem seems to really be the name of the interface...
I need to find a real way to fix that, but for now you can rename them (this doesn't survice a reboot):

ip link set 10g-1 down
ip link set 10g-1 name 10g1
ip link set 10g1 up

And then set the device in Network->Interface