Lines Matching refs:carrier
531 asserting carrier. It is similar to the Cisco EtherChannel min-links
534 (carrier on). This is useful for situations where higher level services
539 The default value is 0. This will cause carrier to be asserted (for
825 "carrier on," so if a driver does not support netif_carrier,
1760 TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0
1766 TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0
1773 TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0
1916 The MII monitor monitors only the carrier state of the local
1918 depending upon the device driver to maintain its carrier state, by
1923 then the MII monitor will rely on the driver for carrier state
1926 detect carrier loss on the device (e.g., when the cable is physically
1932 request fails (not just that it returns carrier down), then the MII
2025 instructs bonding to trust the driver to maintain carrier state.
2038 it does, then it may be that the driver checks the carrier state at a
2045 carrier state. It has no way to determine the state of devices on or
2047 traffic while still maintaining carrier on.
2502 the link is up (carrier available), but not pass traffic over the
2722 above). In general, miimon monitors the carrier state as sensed by