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
320 non-ARP traffic should be filtered (disregarded) for link
360 is receiving the appropriate ARP traffic.
379 target fail (but not the switch itself), the probe traffic
395 determining if a slave has received traffic for link availability
399 levels of third party broadcast traffic would fool the standard
401 filtering can resolve this, as only ARP traffic is considered for
466 often takes place for any traffic, not just ARP
467 traffic, if the switch snoops incoming traffic to
610 Slave selection for outgoing traffic is done according
636 In tlb_dynamic_lb=1 mode; the outgoing traffic is
644 Incoming traffic is received by the current slave.
656 receive load balancing (rlb) for IPV4 traffic, and
666 Receive traffic from connections created by the server
677 of the bond and the balancing of receive traffic
681 the traffic is redistributed. Receive traffic is also
688 bond the receive traffic is redistributed among all
866 This algorithm will place all traffic to a particular
888 This algorithm will place all traffic to a particular
889 network peer on the same slave. For non-IP traffic,
894 distribution of traffic than layer2 alone, especially
904 traffic to a particular network peer to span multiple
920 IPv6 protocol traffic, the source and destination port
921 information is omitted. For non-IP traffic, the
929 of order delivery. Most traffic types will not meet
930 this criteria, as TCP rarely fragments traffic, and
931 most UDP traffic is not involved in extended
972 switch the IGMP traffic from one slave to another. Therefore a fresh
974 IGMP traffic over the newly selected slave.
1634 classes of traffic to certain physical interfaces on output to implement
1638 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1640 using the traffic control utilities inherent in linux.
1681 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1683 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1692 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1720 traffic and / or spoofing traffic from that machine themselves (potentially
1924 gives some assurance that traffic is actually flowing to and from one
1928 that traffic is flowing. In particular, the driver must keep up to
2006 may bypass the bonding driver (because outgoing traffic to, in this
2093 traffic while still maintaining carrier on.
2147 common to enable promiscuous mode on the device, so that all traffic
2148 is seen (instead of seeing only traffic destined for the local host).
2160 receiving inbound traffic.
2163 "primary." This slave is used for mode-specific control traffic, for
2242 necessary for some specific one-way traffic to reach both
2259 individual component to pass traffic for any reason). Additionally,
2287 two categories. Depending upon the destination of most traffic, we
2291 as a router, and the majority of traffic passes through this router to
2304 the majority of traffic from Host A will pass through the router to
2308 communicate with many other systems, all of its traffic will be sent
2314 traffic is destined for the "gateway" itself, not some other network
2318 a switch, and the majority of traffic passes through this switch to
2332 that the majority of traffic from Host A is destined for other hosts
2335 In summary, in a gatewayed configuration, traffic to and from
2338 destination. In a local configuration, traffic flows directly to and
2358 TCP/IP connection to stripe traffic across multiple
2380 Many switches do not support any modes that stripe traffic
2382 for those devices, traffic for a particular connection flowing
2407 This mode will limit traffic such that packets destined
2413 if all your traffic is passed through a single router (i.e., a
2441 distributes traffic by peer (using an XOR of MAC addresses
2443 outgoing traffic will generally use the same device. Incoming
2444 traffic may also end up on a single device, but that is
2446 implementation. In a "local" configuration, traffic will be
2453 The balance-tlb mode balances outgoing traffic by peer.
2456 send all traffic across a single device. However, in a
2466 in this mode all incoming traffic arrives over a single
2474 and will also balance incoming traffic from local network
2559 the link is up (carrier available), but not pass traffic over the
2595 traffic when the bonding device is first used, or after it has been
2618 traffic to all ports until its MAC forwarding table is updated. Since
2620 single switch, when the switch (temporarily) floods the traffic to all
2705 must be able to reach all destinations for traffic sent over the
2732 network traffic, as the SoL system is beyond the control of the