Lines Matching full:traffic
286 traffic recently (the precise criteria depends upon the
287 bonding mode, and the state of the slave). Regular traffic is
319 non-ARP traffic should be filtered (disregarded) for link
359 is receiving the appropriate ARP traffic.
378 target fail (but not the switch itself), the probe traffic
394 determining if a slave has received traffic for link availability
398 levels of third party broadcast traffic would fool the standard
400 filtering can resolve this, as only ARP traffic is considered for
465 often takes place for any traffic, not just ARP
466 traffic, if the switch snoops incoming traffic to
609 Slave selection for outgoing traffic is done according
635 In tlb_dynamic_lb=1 mode; the outgoing traffic is
643 Incoming traffic is received by the current slave.
655 receive load balancing (rlb) for IPV4 traffic, and
665 Receive traffic from connections created by the server
676 of the bond and the balancing of receive traffic
680 the traffic is redistributed. Receive traffic is also
687 bond the receive traffic is redistributed among all
865 This algorithm will place all traffic to a particular
887 This algorithm will place all traffic to a particular
888 network peer on the same slave. For non-IP traffic,
893 distribution of traffic than layer2 alone, especially
903 traffic to a particular network peer to span multiple
919 IPv6 protocol traffic, the source and destination port
920 information is omitted. For non-IP traffic, the
928 of order delivery. Most traffic types will not meet
929 this criteria, as TCP rarely fragments traffic, and
930 most UDP traffic is not involved in extended
971 switch the IGMP traffic from one slave to another. Therefore a fresh
973 IGMP traffic over the newly selected slave.
1633 classes of traffic to certain physical interfaces on output to implement
1637 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1639 using the traffic control utilities inherent in linux.
1680 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1682 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1691 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1719 traffic and / or spoofing traffic from that machine themselves (potentially
1923 gives some assurance that traffic is actually flowing to and from one
1927 that traffic is flowing. In particular, the driver must keep up to
2005 may bypass the bonding driver (because outgoing traffic to, in this
2092 traffic while still maintaining carrier on.
2146 common to enable promiscuous mode on the device, so that all traffic
2147 is seen (instead of seeing only traffic destined for the local host).
2159 receiving inbound traffic.
2162 "primary." This slave is used for mode-specific control traffic, for
2241 necessary for some specific one-way traffic to reach both
2258 individual component to pass traffic for any reason). Additionally,
2286 two categories. Depending upon the destination of most traffic, we
2290 as a router, and the majority of traffic passes through this router to
2303 the majority of traffic from Host A will pass through the router to
2307 communicate with many other systems, all of its traffic will be sent
2313 traffic is destined for the "gateway" itself, not some other network
2317 a switch, and the majority of traffic passes through this switch to
2331 that the majority of traffic from Host A is destined for other hosts
2334 In summary, in a gatewayed configuration, traffic to and from
2337 destination. In a local configuration, traffic flows directly to and
2357 TCP/IP connection to stripe traffic across multiple
2379 Many switches do not support any modes that stripe traffic
2381 for those devices, traffic for a particular connection flowing
2406 This mode will limit traffic such that packets destined
2412 if all your traffic is passed through a single router (i.e., a
2440 distributes traffic by peer (using an XOR of MAC addresses
2442 outgoing traffic will generally use the same device. Incoming
2443 traffic may also end up on a single device, but that is
2445 implementation. In a "local" configuration, traffic will be
2452 The balance-tlb mode balances outgoing traffic by peer.
2455 send all traffic across a single device. However, in a
2465 in this mode all incoming traffic arrives over a single
2473 and will also balance incoming traffic from local network
2558 the link is up (carrier available), but not pass traffic over the
2594 traffic when the bonding device is first used, or after it has been
2617 traffic to all ports until its MAC forwarding table is updated. Since
2619 single switch, when the switch (temporarily) floods the traffic to all
2704 must be able to reach all destinations for traffic sent over the
2731 network traffic, as the SoL system is beyond the control of the