Latency Test OK, dennoch Fehlermeldung
31 Jul 2024 19:45 #306561
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 862882sec preferred_lft 862882sec
inet6 2003:ce:5f08:8600:c668:e1df:16a1:628a/64 scope global dynamic noprefixroute
valid_lft 6832sec preferred_lft 971sec
inet6 fe80::3e8d:84c2:564c:edaa/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::282c:39b2:ab82:4316/64 scope link noprefixroute
valid_lft forever preferred_lft forever
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 862882sec preferred_lft 862882sec
inet6 2003:ce:5f08:8600:c668:e1df:16a1:628a/64 scope global dynamic noprefixroute
valid_lft 6832sec preferred_lft 971sec
inet6 fe80::3e8d:84c2:564c:edaa/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::282c:39b2:ab82:4316/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Please Log in or Create an account to join the conversation.
31 Jul 2024 19:47 #306562
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
" IRQ coalescing is not disabled." How can I do that?
Please Log in or Create an account to join the conversation.
31 Jul 2024 20:39 #306566
by PCW
Replied by PCW on topic Latency Test OK, dennoch Fehlermeldung
man hm2_eth
for instructions for doing this permanently
to test temporarily:
sudo ethtool -C eno1 rx-usecs 0
for instructions for doing this permanently
to test temporarily:
sudo ethtool -C eno1 rx-usecs 0
The following user(s) said Thank You: Muftijaja
Please Log in or Create an account to join the conversation.
31 Jul 2024 21:43 - 31 Jul 2024 21:52 #306570
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
Attachments:
Last edit: 31 Jul 2024 21:52 by Muftijaja.
Please Log in or Create an account to join the conversation.
31 Jul 2024 22:11 #306571
by PCW
Replied by PCW on topic Latency Test OK, dennoch Fehlermeldung
As described in the hm2_eth man page, it involves adding the appropriate text
to the /etc/network/interfaces file, in your case, adding something like:
auto eno1
iface eno1 inet static
address 10.10.10.2
hardware-irq-coalesce-rx-usecs 0
You need to run the editor as root (with sudo) to edit this file
After editing the file its probably best to re-boot and then check if the
setting works with:
ethtool -c en01
to the /etc/network/interfaces file, in your case, adding something like:
auto eno1
iface eno1 inet static
address 10.10.10.2
hardware-irq-coalesce-rx-usecs 0
You need to run the editor as root (with sudo) to edit this file
After editing the file its probably best to re-boot and then check if the
setting works with:
ethtool -c en01
The following user(s) said Thank You: Muftijaja
Please Log in or Create an account to join the conversation.
04 Aug 2024 12:36 - 04 Aug 2024 12:42 #306912
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
Hello PCW,
thank you for your answers! (sorry for delay, I was very busy the last days and couldn't do anything at my machine.)
I tried the lines in /etc/network/interfaces file and after reboot my internal Intel network was disabled. Just auto internet with RLT8111 is possible. The file is as follows:
Well, internet network is ok. What is the faulty setting here?
thank you for your answers! (sorry for delay, I was very busy the last days and couldn't do anything at my machine.)
I tried the lines in /etc/network/interfaces file and after reboot my internal Intel network was disabled. Just auto internet with RLT8111 is possible. The file is as follows:
Well, internet network is ok. What is the faulty setting here?
Attachments:
Last edit: 04 Aug 2024 12:42 by Muftijaja. Reason: wrong data
Please Log in or Create an account to join the conversation.
04 Aug 2024 13:06 #306914
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
This is the feedback of ip a without the suggested lines:
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 862758sec preferred_lft 862758sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7101sec preferred_lft 1700sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 862758sec preferred_lft 862758sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7101sec preferred_lft 1700sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
Please Log in or Create an account to join the conversation.
04 Aug 2024 13:18 #306915
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
And this is ip a with the 4 lines in /etc/network/
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 863931sec preferred_lft 863931sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7132sec preferred_lft 1118sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/8 brd 10.255.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::223:24ff:fe5b:b4ac/64 scope link
valid_lft forever preferred_lft forever
why does it change the altname to enp0s25? that is a conflict with 2. where can I change the altname manually to fix this?
Or should I change the priorities so that eno1 is launched before enp2?
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 863931sec preferred_lft 863931sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7132sec preferred_lft 1118sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/8 brd 10.255.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::223:24ff:fe5b:b4ac/64 scope link
valid_lft forever preferred_lft forever
why does it change the altname to enp0s25? that is a conflict with 2. where can I change the altname manually to fix this?
Or should I change the priorities so that eno1 is launched before enp2?
Please Log in or Create an account to join the conversation.
04 Aug 2024 13:26 #306916
by Muftijaja
Replied by Muftijaja on topic Latency Test OK, dennoch Fehlermeldung
Hmm I tried both, changed priorities eno1 to 1 and auto/enp2 to 0 - no effect.
Then I changed the position of the lines in /etc/network/interfaces - no effect at all.
On what reason ever, the network definitions are faulty.
WTF is going on there?
Then I changed the position of the lines in /etc/network/interfaces - no effect at all.
On what reason ever, the network definitions are faulty.
WTF is going on there?
Please Log in or Create an account to join the conversation.
04 Aug 2024 13:29 - 04 Aug 2024 13:40 #306917
by PCW
Replied by PCW on topic Latency Test OK, dennoch Fehlermeldung
The only thing that I see is different is the netmask
you might try
address 10.10.10.2/24
Also ipv6 has been enabled, which is really odd
you might try
address 10.10.10.2/24
Also ipv6 has been enabled, which is really odd
Last edit: 04 Aug 2024 13:40 by PCW.
The following user(s) said Thank You: Muftijaja
Please Log in or Create an account to join the conversation.
Time to create page: 0.139 seconds