Lines Matching refs:traffic
278 traffic recently (the precise criteria depends upon the
279 bonding mode, and the state of the slave). Regular traffic is
311 non-ARP traffic should be filtered (disregarded) for link
351 is receiving the appropriate ARP traffic.
370 target fail (but not the switch itself), the probe traffic
386 determining if a slave has received traffic for link availability
390 levels of third party broadcast traffic would fool the standard
392 filtering can resolve this, as only ARP traffic is considered for
457 often takes place for any traffic, not just ARP
458 traffic, if the switch snoops incoming traffic to
601 Slave selection for outgoing traffic is done according
627 In tlb_dynamic_lb=1 mode; the outgoing traffic is
635 Incoming traffic is received by the current slave.
647 receive load balancing (rlb) for IPV4 traffic, and
657 Receive traffic from connections created by the server
668 of the bond and the balancing of receive traffic
672 the traffic is redistributed. Receive traffic is also
679 bond the receive traffic is redistributed among all
847 This algorithm will place all traffic to a particular
869 This algorithm will place all traffic to a particular
870 network peer on the same slave. For non-IP traffic,
875 distribution of traffic than layer2 alone, especially
885 traffic to a particular network peer to span multiple
901 IPv6 protocol traffic, the source and destination port
902 information is omitted. For non-IP traffic, the
910 of order delivery. Most traffic types will not meet
911 this criteria, as TCP rarely fragments traffic, and
912 most UDP traffic is not involved in extended
953 switch the IGMP traffic from one slave to another. Therefore a fresh
955 IGMP traffic over the newly selected slave.
1588 classes of traffic to certain physical interfaces on output to implement
1592 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1594 using the traffic control utilities inherent in linux.
1635 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1637 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1646 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1674 traffic and / or spoofing traffic from that machine themselves (potentially
1878 gives some assurance that traffic is actually flowing to and from one
1882 that traffic is flowing. In particular, the driver must keep up to
1960 may bypass the bonding driver (because outgoing traffic to, in this
2047 traffic while still maintaining carrier on.
2099 common to enable promiscuous mode on the device, so that all traffic
2100 is seen (instead of seeing only traffic destined for the local host).
2112 receiving inbound traffic.
2115 "primary." This slave is used for mode-specific control traffic, for
2192 necessary for some specific one-way traffic to reach both
2209 individual component to pass traffic for any reason). Additionally,
2237 two categories. Depending upon the destination of most traffic, we
2241 as a router, and the majority of traffic passes through this router to
2254 the majority of traffic from Host A will pass through the router to
2258 communicate with many other systems, all of its traffic will be sent
2264 traffic is destined for the "gateway" itself, not some other network
2268 a switch, and the majority of traffic passes through this switch to
2282 that the majority of traffic from Host A is destined for other hosts
2285 In summary, in a gatewayed configuration, traffic to and from
2288 destination. In a local configuration, traffic flows directly to and
2307 TCP/IP connection to stripe traffic across multiple
2329 Many switches do not support any modes that stripe traffic
2331 for those devices, traffic for a particular connection flowing
2354 balance-xor: This mode will limit traffic such that packets destined
2360 if all your traffic is passed through a single router (i.e., a
2386 distributes traffic by peer (using an XOR of MAC addresses
2388 outgoing traffic will generally use the same device. Incoming
2389 traffic may also end up on a single device, but that is
2391 implementation. In a "local" configuration, traffic will be
2397 balance-tlb: The balance-tlb mode balances outgoing traffic by peer.
2400 send all traffic across a single device. However, in a
2410 in this mode all incoming traffic arrives over a single
2417 and will also balance incoming traffic from local network
2502 the link is up (carrier available), but not pass traffic over the
2538 traffic when the bonding device is first used, or after it has been
2561 traffic to all ports until its MAC forwarding table is updated. Since
2563 single switch, when the switch (temporarily) floods the traffic to all
2648 must be able to reach all destinations for traffic sent over the
2675 network traffic, as the SoL system is beyond the control of the