LINUX INTERFACE FOR NETWORKING
Linux has wealthy virtual networking capabilities that square measure used as basis for hosting VMs and containers, moreover as cloud environments. during this post, I’ll provides a transient introduction to all or any normally used virtual network interface varieties. there's no code analysis, solely a quick introduction to the interfaces and their usage on UNIX. Anyone with a network background can be curious about this diary post. a listing of interfaces is obtained victimization the command scientific discipline link.
This blog covers the following frequently used interfaces:
- Bridge
- BondeD interface
- Team device
BRIDGE: A Linux bridge behaves sort of a network switch. It forwards packets between interfaces that ar connected to that. it's always used for forwarding packets on routers, on gateways, or between VMs and network namespaces on a bunch. It additionally supports standard temperature, VLAN filter, and multicast snooping
Use a bridge after you need to ascertain communication channels between VMs, containers, and your hosts.
BONDED INTERFACE: The UNIX system bonding driver provides a way for aggregating multiple network interfaces into one logical "bonded" interface. The behavior of the secured interface depends on the mode; usually speaking, modes give either hot standby or load equalisation services.
Use a secured interface after you wish to extend your link speed or do a failover on your server.
TEAM DEVICES: Similar a bonded interface, the purpose of a team device is to provide a mechanism to group multiple NICs (ports) into one logical one (team dev) at the L2 layer.
The main issue to comprehend is that a team device isn't making an attempt to duplicate or mimic a warranted interface. What it will is to unravel identical downside employing a completely different approach, using, for instance, a lockless (RCU) TX/RX path and standard style.
Comments
Post a Comment