I am looking at starting a project to implment 802.3ad ethernet link aggregation under Linux. For those of you that have never heard of it I've given a description and a few pointers at the end. Bef
How would it be user-space? Doesn't it aggregate several physical layers together into one interface? That seems like a kernel level thing to me.... Ben -- Ben Greear (greearb@xxxxxxxxxxxxxxx) http:/
802.3ad is not just channel bonding (the kernel-level mechanism), it also including sending packets down each link to detect topology and verify that the connection continues to work. Donald Becker b
My original thought is that the actual aggregating and frame collection / distribution is certainly a kernel issue, as with the current bonding driver. As for the link detection and automatic aggrega
Like most of such things, there is the fast-path (of packet forwarding), and there is the management protocol. (Comparing to 802.1Q, a lot more than half of the specification is about the management
Likewise with 802.3ad the specification for LACPDU packets is the major part of the spec, once all of the IEEE requirements stuff is jumped over. In that case a logical split for development would be
The required kernel level mechanisms already exit: bounding, teql, equal cost multipath routing. Only multipath routing is strictly conforming to the SPEC of keeping an "conversation" on the same lin
The kernel already has all necessary mechanisms for that in place: queryable neighbour states, after going into slow path the protocol does its own checking anyways. I believe you'll be able to do a
Hello, I am looking at starting a project to implment 802.3ad ethernet link aggregation under Linux. For those of you that have never heard of it I've given a description and a few pointers at the en
How would it be user-space? Doesn't it aggregate several physical layers together into one interface? That seems like a kernel level thing to me.... Ben -- Ben Greear (greearb@xxxxxxxxxxxxxxx) http:/
802.3ad is not just channel bonding (the kernel-level mechanism), it also including sending packets down each link to detect topology and verify that the connection continues to work. Donald Becker b
My original thought is that the actual aggregating and frame collection / distribution is certainly a kernel issue, as with the current bonding driver. As for the link detection and automatic aggrega
Like most of such things, there is the fast-path (of packet forwarding), and there is the management protocol. (Comparing to 802.1Q, a lot more than half of the specification is about the management
Likewise with 802.3ad the specification for LACPDU packets is the major part of the spec, once all of the IEEE requirements stuff is jumped over. In that case a logical split for development would be
The required kernel level mechanisms already exit: bounding, teql, equal cost multipath routing. Only multipath routing is strictly conforming to the SPEC of keeping an "conversation" on the same lin
The kernel already has all necessary mechanisms for that in place: queryable neighbour states, after going into slow path the protocol does its own checking anyways. I believe you'll be able to do a