Lines Matching refs: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
488 often takes place for any traffic, not just ARP
489 traffic, if the switch snoops incoming traffic to
645 Slave selection for outgoing traffic is done according
671 In tlb_dynamic_lb=1 mode; the outgoing traffic is
679 Incoming traffic is received by the current slave.
691 receive load balancing (rlb) for IPV4 traffic, and
701 Receive traffic from connections created by the server
712 of the bond and the balancing of receive traffic
716 the traffic is redistributed. Receive traffic is also
723 bond the receive traffic is redistributed among all
912 This algorithm will place all traffic to a particular
934 This algorithm will place all traffic to a particular
935 network peer on the same slave. For non-IP traffic,
940 distribution of traffic than layer2 alone, especially
950 traffic to a particular network peer to span multiple
967 IPv6 protocol traffic, the source and destination port
968 information is omitted. For non-IP traffic, the
976 of order delivery. Most traffic types will not meet
977 this criteria, as TCP rarely fragments traffic, and
978 most UDP traffic is not involved in extended
1005 hash to load-balance traffic per-vlan, with failover
1032 switch the IGMP traffic from one slave to another. Therefore a fresh
1034 IGMP traffic over the newly selected slave.
1694 classes of traffic to certain physical interfaces on output to implement
1698 traffic over eth0 first, using eth1 only as a fall back, while all other traffic
1700 using the traffic control utilities inherent in linux.
1741 a multiqueue qdisc and filters to bias certain traffic to transmit on certain
1743 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1752 bond0 interface and filter traffic enqueued to it, such that packets with a dst
1780 traffic and / or spoofing traffic from that machine themselves (potentially
1984 gives some assurance that traffic is actually flowing to and from one
2057 may bypass the bonding driver (because outgoing traffic to, in this
2144 traffic while still maintaining carrier on.
2198 common to enable promiscuous mode on the device, so that all traffic
2199 is seen (instead of seeing only traffic destined for the local host).
2211 receiving inbound traffic.
2214 "primary." This slave is used for mode-specific control traffic, for
2293 necessary for some specific one-way traffic to reach both
2310 individual component to pass traffic for any reason). Additionally,
2338 two categories. Depending upon the destination of most traffic, we
2342 as a router, and the majority of traffic passes through this router to
2355 the majority of traffic from Host A will pass through the router to
2359 communicate with many other systems, all of its traffic will be sent
2365 traffic is destined for the "gateway" itself, not some other network
2369 a switch, and the majority of traffic passes through this switch to
2383 that the majority of traffic from Host A is destined for other hosts
2386 In summary, in a gatewayed configuration, traffic to and from
2389 destination. In a local configuration, traffic flows directly to and
2409 TCP/IP connection to stripe traffic across multiple
2431 Many switches do not support any modes that stripe traffic
2433 for those devices, traffic for a particular connection flowing
2458 This mode will limit traffic such that packets destined
2464 if all your traffic is passed through a single router (i.e., a
2492 distributes traffic by peer (using an XOR of MAC addresses
2494 outgoing traffic will generally use the same device. Incoming
2495 traffic may also end up on a single device, but that is
2497 implementation. In a "local" configuration, traffic will be
2504 The balance-tlb mode balances outgoing traffic by peer.
2507 send all traffic across a single device. However, in a
2517 in this mode all incoming traffic arrives over a single
2525 and will also balance incoming traffic from local network
2610 the link is up (carrier available), but not pass traffic over the
2646 traffic when the bonding device is first used, or after it has been
2669 traffic to all ports until its MAC forwarding table is updated. Since
2671 single switch, when the switch (temporarily) floods the traffic to all
2756 must be able to reach all destinations for traffic sent over the
2783 network traffic, as the SoL system is beyond the control of the