Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is my first post on the forum, so I apologize if my question was already asked.
I have two proxmox 4.2 (based on debian 8) servers with 4 nics.
1 is for admin network and 2 are dedicated to nas access (via NFS). Those nics are bonded and it works fine. Below is my bond :
auto bond0
iface bond0 inet static
address 192.168.253.199
netmask 255.255.255.0
slaves eth1 eth2
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2
bond_downdelay 500
bond_updelay 900
However, when I change the mtu of the bond to 9000 (and yhe one of the ywo slave interfaces), the test with ping -s 9000 my_nas_ip does not work
My switch is a netgear GS728TXS with MTU at 9028
My nas is a synology RS814 RP+ with MTU at 9000
I tried with a bridge instead of the bond, and ping -s 9000 my_nas_ip works
Is there anything I have forgotten to configure my bond ?
First am I understanding you correctly you are only changing one interface and not both on the Bond?
Second Bond interface doesn't mean you are going to get double the download or upload. Connections between hosts will only use one of the 2 interfaces. That being said if you only changed one of the interfaces then it could be possible that the communications between hosts was using the interface you never changed.
root@pve:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:f2:64 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:f2:66 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:f2:66 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:e2:f2 brd ff:ff:ff:ff:ff:ff
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:f2:66 brd ff:ff:ff:ff:ff:ff
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether e4:11:5b:d6:f2:64 brd ff:ff:ff:ff:ff:ff
root@pve:~#
The mtu of my switch is 8028.
It still doesn't work. Is there something I misunderstood ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.