February 21, 201610 yr Hi peeps Can someone please comment on my UNRAID network settings as per my ifconfig output below? I set an MTU of 9000 on eth0 using ifconfig eth0 MTU 9000 - however, I added MTU 9000 to my network.cfg but it doesnt seem to stick after reboot. Any ideas? Additionaly, I am not able to set MTU 9000 on br0 bridged interface, do I need to? All my VMs are set to jumbo frames. root@MOUNRAID01:/boot/config# ifconfig br0 mtu 9000 SIOCSIFMTU: Invalid argument Also, I noticed BR0 and VIRBR0 interfaces have interface IP addresses different to my local LAN of 192.168.1.x - why is this? I ask this because my dockers like EMBY try to communicate to the BR0 and VIRBR0 IPs which causes problems. Please help me understand what is going on here... ----- root@MOUNRAID01:/boot/config# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.80 netmask 255.255.255.0 broadcast 192.168.1.255 ether d8:cb:8a:ec:c8:bb txqueuelen 0 (Ethernet) RX packets 306369 bytes 196227804 (187.1 MiB) RX errors 0 dropped 812 overruns 0 frame 0 TX packets 198741 bytes 174558536 (166.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 6a:dd:07:ec:27:41 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 10224 bytes 3886243 (3.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 9000 ether d8:cb:8a:ed:03:1f 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 device interrupt 18 eth1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d8:cb:8a:ec:c8:bb txqueuelen 1000 (Ethernet) RX packets 303307 bytes 139459903 (132.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 277562 bytes 96066192 (91.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 162394 bytes 61349826 (58.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 162394 bytes 61349826 (58.5 MiB) 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:ce:bc:33 txqueuelen 0 (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
February 21, 201610 yr Community Expert I am not sure if the bridges support jumbo frames - from what you tried it is likely they do not. The virbr0 and docker0 bridges are NAT style bridges running on local virtual networks and are not visible outside the server. The br0 bridge IS visible on the network, not sure what you meant by saying it is not on the local LAN IP range. as it appears to be.
February 21, 201610 yr Author I am not sure if the bridges support jumbo frames - from what you tried it is likely they do not. The virbr0 and docker0 bridges are NAT style bridges running on local virtual networks and are not visible outside the server. The br0 bridge IS visible on the network, not sure what you meant by saying it is not on the local LAN IP range. as it appears to be. Sorry I meant docker0 not br0 - br0 is fine. The issue is this.. Im using Emby docker and when I look inside the logs for Emby there are many references to the docker0 interface IP and emby is trying to communicate with docker0 172.x.x.x IP range. Do I need to set Docker0 to be on my local LAN or is it all configured as it should be?
Archived
This topic is now archived and is closed to further replies.