Daniel Lezcano wrote: > Pavel Emelianov wrote: >> Veth stands for Virtual ETHernet. It is a simple tunnel driver >> that works at the link layer and looks like a pair of ethernet >> devices interconnected with each other. >> >> Mainly it allows to communicate between network namespaces but >> it can be used as is as well. >> >> Eric recently sent a similar driver called etun. This >> implementation is closer to the OpenVZ one and it lacks >> some unimportant features of etun driver (like ethtool_ops) >> for simplicity. >> >> The general difference from etun is that a netlink interface >> is used to create and destroy the pairs. The patch for an >> ip utility is also provided. > if etun and veth are similar, why didn't you put the netlink interface > to the etun driver instead of sending a new driver ? Alexey said, that he preferred the name "veth" to "etun". So an incremental patch would look too bad. > -- Daniel > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
