Lines Matching full:traffic
287 traffic recently (the precise criteria depends upon the
288 bonding mode, and the state of the slave). Regular traffic is
331 non-ARP traffic should be filtered (disregarded) for link
371 is receiving the appropriate ARP traffic.
390 target fail (but not the switch itself), the probe traffic
406 determining if a slave has received traffic for link availability
410 levels of third party broadcast traffic would fool the standard
412 filtering can resolve this, as only ARP traffic is considered for
500 often takes place for any traffic, not just ARP
501 traffic, if the switch snoops incoming traffic to
657 Slave selection for outgoing traffic is done according
683 In tlb_dynamic_lb=1 mode; the outgoing traffic is
691 Incoming traffic is received by the current slave.
703 receive load balancing (rlb) for IPV4 traffic, and
713 Receive traffic from connections created by the server
724 of the bond and the balancing of receive traffic
728 the traffic is redistributed. Receive traffic is also
735 bond the receive traffic is redistributed among all
925 This algorithm will place all traffic to a particular
947 This algorithm will place all traffic to a particular
948 network peer on the same slave. For non-IP traffic,
953 distribution of traffic than layer2 alone, especially
963 traffic to a particular network peer to span multiple
980 IPv6 protocol traffic, the source and destination port
981 information is omitted. For non-IP traffic, the
989 of order delivery. Most traffic types will not meet
990 this criteria, as TCP rarely fragments traffic, and
991 most UDP traffic is not involved in extended
1018 hash to load-balance traffic per-vlan, with failover
1045 switch the IGMP traffic from one slave to another. Therefore a fresh
1047 IGMP traffic over the newly selected slave.
1707 classes of traffic to certain physical interfaces on output to implement
1711 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1713 using the traffic control utilities inherent in linux.
1754 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1756 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1765 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1793 traffic and / or spoofing traffic from that machine themselves (potentially
1997 gives some assurance that traffic is actually flowing to and from one
2070 may bypass the bonding driver (because outgoing traffic to, in this
2157 traffic while still maintaining carrier on.
2211 common to enable promiscuous mode on the device, so that all traffic
2212 is seen (instead of seeing only traffic destined for the local host).
2224 receiving inbound traffic.
2227 "primary." This slave is used for mode-specific control traffic, for
2306 necessary for some specific one-way traffic to reach both
2323 individual component to pass traffic for any reason). Additionally,
2351 two categories. Depending upon the destination of most traffic, we
2355 as a router, and the majority of traffic passes through this router to
2368 the majority of traffic from Host A will pass through the router to
2372 communicate with many other systems, all of its traffic will be sent
2378 traffic is destined for the "gateway" itself, not some other network
2382 a switch, and the majority of traffic passes through this switch to
2396 that the majority of traffic from Host A is destined for other hosts
2399 In summary, in a gatewayed configuration, traffic to and from
2402 destination. In a local configuration, traffic flows directly to and
2422 TCP/IP connection to stripe traffic across multiple
2444 Many switches do not support any modes that stripe traffic
2446 for those devices, traffic for a particular connection flowing
2471 This mode will limit traffic such that packets destined
2477 if all your traffic is passed through a single router (i.e., a
2505 distributes traffic by peer (using an XOR of MAC addresses
2507 outgoing traffic will generally use the same device. Incoming
2508 traffic may also end up on a single device, but that is
2510 implementation. In a "local" configuration, traffic will be
2517 The balance-tlb mode balances outgoing traffic by peer.
2520 send all traffic across a single device. However, in a
2530 in this mode all incoming traffic arrives over a single
2538 and will also balance incoming traffic from local network
2623 the link is up (carrier available), but not pass traffic over the
2659 traffic when the bonding device is first used, or after it has been
2682 traffic to all ports until its MAC forwarding table is updated. Since
2684 single switch, when the switch (temporarily) floods the traffic to all
2769 must be able to reach all destinations for traffic sent over the
2796 network traffic, as the SoL system is beyond the control of the