Lines Matching refs:traffic
241 traffic recently (the precise criteria depends upon the
242 bonding mode, and the state of the slave). Regular traffic is
274 non-ARP traffic should be filtered (disregarded) for link
314 is receiving the appropriate ARP traffic.
333 target fail (but not the switch itself), the probe traffic
349 determining if a slave has received traffic for link availability
353 levels of third party broadcast traffic would fool the standard
355 filtering can resolve this, as only ARP traffic is considered for
420 often takes place for any traffic, not just ARP
421 traffic, if the switch snoops incoming traffic to
564 Slave selection for outgoing traffic is done according
590 In tlb_dynamic_lb=1 mode; the outgoing traffic is
598 Incoming traffic is received by the current slave.
610 receive load balancing (rlb) for IPV4 traffic, and
620 Receive traffic from connections created by the server
631 of the bond and the balancing of receive traffic
635 the traffic is redistributed. Receive traffic is also
642 bond the receive traffic is redistributed among all
810 This algorithm will place all traffic to a particular
832 This algorithm will place all traffic to a particular
833 network peer on the same slave. For non-IP traffic,
838 distribution of traffic than layer2 alone, especially
848 traffic to a particular network peer to span multiple
864 IPv6 protocol traffic, the source and destination port
865 information is omitted. For non-IP traffic, the
873 of order delivery. Most traffic types will not meet
874 this criteria, as TCP rarely fragments traffic, and
875 most UDP traffic is not involved in extended
916 switch the IGMP traffic from one slave to another. Therefore a fresh
918 IGMP traffic over the newly selected slave.
1551 classes of traffic to certain physical interfaces on output to implement
1555 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1557 using the traffic control utilities inherent in linux.
1598 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1600 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1609 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1794 gives some assurance that traffic is actually flowing to and from one
1798 that traffic is flowing. In particular, the driver must keep up to
1876 may bypass the bonding driver (because outgoing traffic to, in this
1963 traffic while still maintaining carrier on.
2015 common to enable promiscuous mode on the device, so that all traffic
2016 is seen (instead of seeing only traffic destined for the local host).
2028 receiving inbound traffic.
2031 "primary." This slave is used for mode-specific control traffic, for
2108 necessary for some specific one-way traffic to reach both
2125 individual component to pass traffic for any reason). Additionally,
2153 two categories. Depending upon the destination of most traffic, we
2157 as a router, and the majority of traffic passes through this router to
2170 the majority of traffic from Host A will pass through the router to
2174 communicate with many other systems, all of its traffic will be sent
2180 traffic is destined for the "gateway" itself, not some other network
2184 a switch, and the majority of traffic passes through this switch to
2198 that the majority of traffic from Host A is destined for other hosts
2201 In summary, in a gatewayed configuration, traffic to and from
2204 destination. In a local configuration, traffic flows directly to and
2223 TCP/IP connection to stripe traffic across multiple
2245 Many switches do not support any modes that stripe traffic
2247 for those devices, traffic for a particular connection flowing
2270 balance-xor: This mode will limit traffic such that packets destined
2276 if all your traffic is passed through a single router (i.e., a
2302 distributes traffic by peer (using an XOR of MAC addresses
2304 outgoing traffic will generally use the same device. Incoming
2305 traffic may also end up on a single device, but that is
2307 implementation. In a "local" configuration, traffic will be
2313 balance-tlb: The balance-tlb mode balances outgoing traffic by peer.
2316 send all traffic across a single device. However, in a
2326 in this mode all incoming traffic arrives over a single
2333 and will also balance incoming traffic from local network
2418 the link is up (carrier available), but not pass traffic over the
2454 traffic when the bonding device is first used, or after it has been
2477 traffic to all ports until its MAC forwarding table is updated. Since
2479 single switch, when the switch (temporarily) floods the traffic to all
2564 must be able to reach all destinations for traffic sent over the
2591 network traffic, as the SoL system is beyond the control of the