sureguy Posted January 1, 2018 Share Posted January 1, 2018 (edited) I've tried in 6.3.5 and 6.4.0_rc18f. I"ve booted ubuntu 16.04.3 Desktop live from usb on the same hardware and the issue doesn't exist. Basically if I ping (my workstation or router) with a size greater than 1504 from unraid the ping fails. The same thing happens if I ping unraid from these devices. I've disabled my onboard NIC as it's not being used. The NIC is an "Intel Corporation 82574L Gigabit Network Connection PCIE card. I can even use jumbo frames from within VMs hosted on unRAID and ping my router or workstation with 9000 byte packets. Any suggestions on how to resolve this issue would be appreciated. Currently running 6.4.0_rc18f the output of ifconfig and ethtool follow: root@Phatstore:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 9000 inet6 fe80::21b:21ff:fe4c:233 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 42682 bytes 59851034 (57.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24282 bytes 2824528 (2.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 192.168.3.5 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::b0ce:3bff:fe18:71e8 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 41635 bytes 58363303 (55.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22821 bytes 2550997 (2.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:b5ff:fefe:4cbe prefixlen 64 scopeid 0x20<link> ether 02:42:b5:fe:4c:be txqueuelen 0 (Ethernet) RX packets 18414 bytes 1294607 (1.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 33881 bytes 49590312 (47.2 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000 ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 42682 bytes 59851034 (57.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24282 bytes 2824528 (2.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xf79c0000-f79e0000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2205 bytes 1039524 (1015.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2205 bytes 1039524 (1015.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth38984e9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::5440:dfff:fea6:31c2 prefixlen 64 scopeid 0x20<link> ether 56:40:df:a6:31:c2 txqueuelen 0 (Ethernet) RX packets 17204 bytes 1145249 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 32662 bytes 49118877 (46.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth62466e9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::1452:88ff:feca:98ef prefixlen 64 scopeid 0x20<link> ether 16:52:88:ca:98:ef txqueuelen 0 (Ethernet) RX packets 3 bytes 138 (138.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 267 bytes 30010 (29.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth67b76ef: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc3c:9cff:fef3:59e1 prefixlen 64 scopeid 0x20<link> ether fe:3c:9c:f3:59:e1 txqueuelen 0 (Ethernet) RX packets 509 bytes 333141 (325.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 811 bytes 91753 (89.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6871e2b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::78e3:eff:fe65:9b80 prefixlen 64 scopeid 0x20<link> ether 7a:e3:0e:65:9b:80 txqueuelen 0 (Ethernet) RX packets 360 bytes 39419 (38.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 632 bytes 271505 (265.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6b5b5fa: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::54c1:13ff:feac:7a17 prefixlen 64 scopeid 0x20<link> ether 56:c1:13:ac:7a:17 txqueuelen 0 (Ethernet) RX packets 189 bytes 18172 (17.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 430 bytes 107104 (104.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetha3e3d5a: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::8833:24ff:fec0:b352 prefixlen 64 scopeid 0x20<link> ether 8a:33:24:c0:b3:52 txqueuelen 0 (Ethernet) RX packets 149 bytes 16284 (15.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 418 bytes 123108 (120.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:cd:a2:9b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fee2:4e5f prefixlen 64 scopeid 0x20<link> ether fe:54:00:e2:4e:5f txqueuelen 1000 (Ethernet) RX packets 359 bytes 55360 (54.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1386 bytes 518894 (506.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:feb1:f956 prefixlen 64 scopeid 0x20<link> ether fe:54:00:b1:f9:56 txqueuelen 1000 (Ethernet) RX packets 232 bytes 31416 (30.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1290 bytes 494438 (482.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fe44:dd23 prefixlen 64 scopeid 0x20<link> ether fe:54:00:44:dd:23 txqueuelen 1000 (Ethernet) RX packets 477 bytes 43040 (42.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1511 bytes 546422 (533.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Phatstore:~# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes root@Phatstore:~# ethtool bond0 Settings for bond0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes Edited January 1, 2018 by sureguy more info Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 1. Check your switch. Does it support jumbo frames and up to what size? 2. Is your router also configured to use jumbo frames? Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 (edited) Yes Jumbo Frames are enabled on my router, and my switch supports 15K jumbo frames. I booted a live linux distro from my unraid server, and ran ping -s 9000 to both my router and workstation without issue. So it's not a problem with any of the hardware being used. Below is the output of me pinging from my router: unraid (192.168.3.5) with 1504 bytes, unraid (192.168.3.5) with 1505 bytes, a ubuntu VM (192.168.3.198) hosted on unraid with 9000 bytes: root@unknown:/tmp/home/root# ping 192.168.3.5 -c 4 -s 1504 PING 192.168.3.5 (192.168.3.5): 1504 data bytes 1512 bytes from 192.168.3.5: seq=0 ttl=64 time=0.870 ms 1512 bytes from 192.168.3.5: seq=1 ttl=64 time=0.470 ms 1512 bytes from 192.168.3.5: seq=2 ttl=64 time=1.977 ms 1512 bytes from 192.168.3.5: seq=3 ttl=64 time=0.615 ms --- 192.168.3.5 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.470/0.983/1.977 ms root@unknown:/tmp/home/root# ping 192.168.3.5 -c 4 -s 1505 PING 192.168.3.5 (192.168.3.5): 1505 data bytes --- 192.168.3.5 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss root@unknown:/tmp/home/root# ping 192.168.3.198 -c 4 -s 9000 PING 192.168.3.198 (192.168.3.198): 9000 data bytes 9008 bytes from 192.168.3.198: seq=0 ttl=64 time=5.254 ms 9008 bytes from 192.168.3.198: seq=1 ttl=64 time=1.241 ms 9008 bytes from 192.168.3.198: seq=2 ttl=64 time=1.034 ms 9008 bytes from 192.168.3.198: seq=3 ttl=64 time=1.063 ms --- 192.168.3.198 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.034/2.148/5.254 ms Edited January 1, 2018 by sureguy additional info Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 (edited) Looking at your list of interfaces. I am missing eth0, is this interface up? It is needed by unRAID itself. jumbo frames are working fine on my test server. # ping 10.0.101.1 -s 9000 PING 10.0.101.1 (10.0.101.1) 9000(9028) bytes of data. 9008 bytes from 10.0.101.1: icmp_seq=1 ttl=64 time=0.879 ms 9008 bytes from 10.0.101.1: icmp_seq=2 ttl=64 time=0.787 ms 9008 bytes from 10.0.101.1: icmp_seq=3 ttl=64 time=0.803 ms ^C --- 10.0.101.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2032ms rtt min/avg/max/mdev = 0.787/0.823/0.879/0.040 ms The above is my test server pinging my router. Edited January 1, 2018 by bonienl Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 eth0 is my onboard nic - which I disabled in the bios as part of my troubleshooting. I'm not sure why unraid decided to assign my NIC to eth1. Attached is my network.cfg: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0 eth1" BRNICS[0]="bond0" DESCRIPTION[0]="" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.3.5" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.3.254" METRIC[0]="" DNS_SERVER1="192.168.3.250" DNS_SERVER2="192.168.3.198" DNS_SERVER3="" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" MTU[0]="9000" SYSNICS="1" Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 Rereading your first post. Likely your disabled interface was eth0. You'll need to change your current interface from eth1 to eth0. See Network Settings -> Interfcae Rules Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 I've eliminated eth1 but the problem persists. New output of ifconfig: root@Phatstore:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 9000 inet6 fe80::21b:21ff:fe4c:233 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 3530 bytes 1707911 (1.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3555 bytes 2419328 (2.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 192.168.3.5 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::7831:80ff:fea8:b412 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 2885 bytes 958663 (936.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1870 bytes 2247105 (2.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:68ff:fea2:b842 prefixlen 64 scopeid 0x20<link> ether 02:42:68:a2:b8:42 txqueuelen 0 (Ethernet) RX packets 43 bytes 16594 (16.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 111 bytes 28321 (27.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000 ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 4944 bytes 2927792 (2.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5107 bytes 3036116 (2.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xf79c0000-f79e0000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 46 bytes 24013 (23.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 46 bytes 24013 (23.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4fd73ef: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::249e:55ff:fe4f:132d prefixlen 64 scopeid 0x20<link> ether 26:9e:55:4f:13:2d txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24 bytes 4513 (4.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth72c2b6f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::ec85:7aff:feb7:6885 prefixlen 64 scopeid 0x20<link> ether ee:85:7a:b7:68:85 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 59 bytes 9497 (9.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethcb9657f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::c42b:abff:fe8c:6cc5 prefixlen 64 scopeid 0x20<link> ether c6:2b:ab:8c:6c:c5 txqueuelen 0 (Ethernet) RX packets 23 bytes 14920 (14.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 118 bytes 19053 (18.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethe7a24c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::7cd5:8eff:fe9c:deeb prefixlen 64 scopeid 0x20<link> ether 7e:d5:8e:9c:de:eb txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 74 bytes 12197 (11.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethf02c911: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::4033:2dff:fea8:9db4 prefixlen 64 scopeid 0x20<link> ether 42:33:2d:a8:9d:b4 txqueuelen 0 (Ethernet) RX packets 20 bytes 2276 (2.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 84 bytes 24661 (24.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethf45dbe2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::2829:20ff:fe20:40ad prefixlen 64 scopeid 0x20<link> ether 2a:29:20:20:40:ad txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 63 bytes 9813 (9.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:cd:a2:9b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:feb1:f956 prefixlen 64 scopeid 0x20<link> ether fe:54:00:b1:f9:56 txqueuelen 1000 (Ethernet) RX packets 182 bytes 26149 (25.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 548 bytes 270968 (264.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fee2:4e5f prefixlen 64 scopeid 0x20<link> ether fe:54:00:e2:4e:5f txqueuelen 1000 (Ethernet) RX packets 219 bytes 33064 (32.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 576 bytes 280055 (273.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fe44:dd23 prefixlen 64 scopeid 0x20<link> ether fe:54:00:44:dd:23 txqueuelen 1000 (Ethernet) RX packets 255 bytes 24056 (23.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 622 bytes 311214 (303.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 What happens when you do the ping from the unRAID server (192.168.3.5) to your router (192.168.3.254) ? Any firewall rule on your router which may interfere with this? Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 I am also missing a setting in your network file. There should be: DHCP_KEEPRESOLV="yes" Can you re-apply the network settings? Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 No - no firewall or anything like that inside my network - only the router acts as a firewall: root@Phatstore:~# ping 192.168.3.254 -s 1504 -c 4 PING 192.168.3.254 (192.168.3.254) 1504(1532) bytes of data. 1512 bytes from 192.168.3.254: icmp_seq=1 ttl=64 time=0.384 ms 1512 bytes from 192.168.3.254: icmp_seq=2 ttl=64 time=0.395 ms 1512 bytes from 192.168.3.254: icmp_seq=3 ttl=64 time=0.370 ms 1512 bytes from 192.168.3.254: icmp_seq=4 ttl=64 time=0.369 ms --- 192.168.3.254 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3056ms rtt min/avg/max/mdev = 0.369/0.379/0.395/0.022 ms root@Phatstore:~# ping 192.168.3.254 -s 1505 -c 4 PING 192.168.3.254 (192.168.3.254) 1505(1533) bytes of data. --- 192.168.3.254 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3086ms Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 Here's the output of my network.cfg - it may not have the DHCP_KEEPRESOLV="yes" line, as I'm configured statically: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0" BRNICS[0]="bond0" DESCRIPTION[0]="" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.3.5" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.3.254" METRIC[0]="" DNS_SERVER1="192.168.3.250" DNS_SERVER2="192.168.3.198" DNS_SERVER3="" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" MTU[0]="9000" SYSNICS="1" Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 (edited) Perhaps re-applying the network settings may "solve" something. Interfaces look okay and I can't tell why it isn't working. Btw did you ping from server to router? Edited January 1, 2018 by bonienl Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 I rebooted - still the same thing. Thanks for trying (oh and happy new year!), maybe someone else has some sort of idea. Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 Rebooting and re-applying settings is two different things. Please try. Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 Reapplied the settings - same thing - anything more than 1504 bytes fails Quote Link to comment
bonienl Posted January 1, 2018 Share Posted January 1, 2018 The only thing I can think off is your hardware NIC not supporting jumbo frames. Quote Link to comment
sureguy Posted January 1, 2018 Author Share Posted January 1, 2018 I'd like to think that's the issue, but if I power down the server, stick a live linux distro on a USB stick in it and boot that, I have no issue pinging with 9000 bytes. This is specific to unraid or the driver being used by unraid. Just for kicks I'll probably re-enable the onboard nic, and test using that (test linux first and then unraid to see if it works) Quote Link to comment
raftrider Posted May 7, 2018 Share Posted May 7, 2018 I have the same issue in unraid 6.5 . It shows eth0 , eth1 and bond at 9000 but it can't ping over 1450. I can ping from the switch (unifi 16-150w) to my proxmox host and from the proxmox host to the switch @9000 but unraid won't . This is running on a Lenovo D10 Workstation, both ethernet ports are onboard. Is there any update on this issue? Quote Link to comment
pwm Posted May 8, 2018 Share Posted May 8, 2018 Note that ping with size 9000 doesn't guarantee you test with jumbo packets. If the device you ping from doesn't support jumbo packets then it will send out a fragmented packet that will work through other devices that doesn't support jumbo packets. But when you issue a ping of size 9000 from a device that handles jumbo packets, then all other devices in the path to the target must also support jumbo packets. Quote Link to comment
bonienl Posted May 8, 2018 Share Posted May 8, 2018 True, you should set the "do not fragment" option to ensure a ping packet doesn't get fragmented. Quote Link to comment
sureguy Posted May 8, 2018 Author Share Posted May 8, 2018 (edited) I was never able to get this sorted out. I was able to boot into a live Ubuntu install and use Jumbo frames properly. Both my onboard NIC (Broadcom BCM57781) and an Intel Corporation 82574L Gigabit Network Connection did not work properly I've subsequently replaced my router with an ER-X which doesn't support Jumbo frames, so no reason to pursue it on my end. Edited May 8, 2018 by sureguy Quote Link to comment
raftrider Posted May 8, 2018 Share Posted May 8, 2018 @pwm read my post again. I have a unifi switch 16-150w with jumbo frames enabled(switch has terminal/ssh access to test that jumbo works). I have a proxmox server with jumbo frames enabled. The server that now has unraid previously had proxmox as well with jumbo frames enabled and worked perfectly fine. The issue is with unraid, that is just a fact. My boss has the same version of unraid on his server and jumbo frames don't work either. Quote Link to comment
bonienl Posted May 8, 2018 Share Posted May 8, 2018 I have set both my servers to MTU 9000 root@vesta:~# ping -s 9000 -M do 10.0.101.6 PING 10.0.101.6 (10.0.101.6) 9000(9028) bytes of data. ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 root@vesta:~# ping -s 8972 -M do 10.0.101.6 PING 10.0.101.6 (10.0.101.6) 8972(9000) bytes of data. 8980 bytes from 10.0.101.6: icmp_seq=1 ttl=64 time=0.621 ms 8980 bytes from 10.0.101.6: icmp_seq=2 ttl=64 time=0.924 ms 8980 bytes from 10.0.101.6: icmp_seq=3 ttl=64 time=0.611 ms 8980 bytes from 10.0.101.6: icmp_seq=4 ttl=64 time=0.971 ms 8980 bytes from 10.0.101.6: icmp_seq=5 ttl=64 time=0.968 ms Quote Link to comment
pwm Posted May 8, 2018 Share Posted May 8, 2018 25 minutes ago, bonienl said: I have set both my servers to MTU 9000 root@vesta:~# ping -s 9000 -M do 10.0.101.6 PING 10.0.101.6 (10.0.101.6) 9000(9028) bytes of data. ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 ping: local error: Message too long, mtu=9000 root@vesta:~# ping -s 8972 -M do 10.0.101.6 PING 10.0.101.6 (10.0.101.6) 8972(9000) bytes of data. 8980 bytes from 10.0.101.6: icmp_seq=1 ttl=64 time=0.621 ms 8980 bytes from 10.0.101.6: icmp_seq=2 ttl=64 time=0.924 ms 8980 bytes from 10.0.101.6: icmp_seq=3 ttl=64 time=0.611 ms 8980 bytes from 10.0.101.6: icmp_seq=4 ttl=64 time=0.971 ms 8980 bytes from 10.0.101.6: icmp_seq=5 ttl=64 time=0.968 ms Correct - MTU is the total payload size of the IP packet. But the -s parameter to ping can actually differ for different implementations of ping. unRAID without jumbo packets can't do ping -s 1500 -M do because the ping doesn't result in MTU 1500. unRAID can do poing -s 1472 -M do <ipv4> So that should mean that on unRAID, ping -s 8972 -M do <ipv4> should work if all involved devices has support for MTU 9000. ICMP has an overhead of 8 bytes. TCP has an overhead of 20 bytes. Quote Link to comment
bonienl Posted May 8, 2018 Share Posted May 8, 2018 (edited) My example above required the switch to support jumbo frames (on my Ubiquiti switch this needs to be explicitely enabled). The next example is jumbo frame support in a Ubuntu VM, which requires the VM interface to support jumbo frames (Ubuntu allows changes thru GUI, but requires a restart to make them effective) AND because this VM is in a separate network (VLAN) it is required that the router supports jumbo frames too on its LAN interface(s). The same for a Windows 10 VM This is from inside a docker container (Netdata) Edited May 8, 2018 by bonienl Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.