Quick Answer

Auto MDI/MDIX—also written Auto-MDI/MDIX or Auto-MDI-X—is an Ethernet PHY feature that automatically determines whether the transmit and receive connections need to be crossed internally.

In older Ethernet networks, you normally had to choose between:

• a straight-through Ethernet cable, or
• a crossover Ethernet cable

depending on what types of devices were being connected.

For example, traditionally:

Connection	Traditional Cable
PC → Switch	Straight-through
PC → Hub	Straight-through
Router → Switch	Straight-through
PC → PC	Crossover
Switch → Switch	Crossover
Hub → Hub	Crossover
Router → Router Ethernet	Crossover

With Auto MDI/MDIX, the Ethernet PHY can automatically compensate for the transmit/receive orientation. As a result, either a straight-through or crossover cable can normally work on supported copper Ethernet ports.

Cisco describes Auto-MDIX as automatically detecting the required connection type and configuring the interface accordingly. Intel likewise documents that its Gigabit copper adapters can automatically accommodate MDI or MDI-X connections.

This is why the distinction between straight-through and crossover patch cables is much less important on modern Ethernet equipment.

What Do MDI and MDIX Mean?

The terminology is easier to understand when expanded.

MDI means:

Media Dependent Interface

MDIX or MDI-X means:

Media Dependent Interface with Crossover

The fundamental problem these modes solve is simple:

The transmitter at one end of an Ethernet connection must ultimately connect to the receiver at the other end.

For traditional 10BASE-T and 100BASE-TX Ethernet, dedicated transmit and receive pairs made this especially obvious.

If both connected devices presented their transmit and receive signals on the same corresponding pins, the cable had to perform the crossover.

MDIX essentially provided the opposite pair orientation.

Why Did Ethernet Need MDI and MDIX?

Consider two Ethernet devices.

Device A needs to send data to Device B:

Device A TX → Device B RX

And Device B needs to send data back:

Device B TX → Device A RX

If the wiring instead effectively connects:

TX → TX

and:

RX → RX

the connection will not work correctly on traditional equipment that cannot compensate for it.

Historically, Ethernet equipment therefore used different port wiring conventions.

End devices such as PCs were generally MDI, while hubs and switches were generally MDIX. Intel describes this historical arrangement: switches and hubs were deliberately wired opposite to end stations so that a straight-through cable could connect the two device classes.

MDI vs MDIX

A simplified comparison is:

Feature	MDI	MDIX
Full name	Media Dependent Interface	Media Dependent Interface with Crossover
Traditional use	End devices	Hubs/switches
Examples	PC, workstation, some routers	Switch, hub
Pair arrangement	Normal MDI orientation	Internally crossed orientation
Purpose	Standard endpoint connection	Complement MDI wiring

This distinction explains the original Ethernet cabling rule.

Different port types

MDI ↔ MDIX

Use a straight-through cable.

Same port types

MDI ↔ MDI

or:

MDIX ↔ MDIX

Use a crossover cable.

That was extremely important before Auto MDI/MDIX became common.

Straight-Through vs Crossover Ethernet Cable

Straight-Through Cable

A straight-through cable uses the same wiring standard at both ends.

For example:

T568B → T568B

or:

T568A → T568A

Conceptually:

End A                 End B

Pin 1  -------------- Pin 1
Pin 2  -------------- Pin 2
Pin 3  -------------- Pin 3
Pin 4  -------------- Pin 4
Pin 5  -------------- Pin 5
Pin 6  -------------- Pin 6
Pin 7  -------------- Pin 7
Pin 8  -------------- Pin 8

Traditionally this was used for connections such as:

Computer ---------------- Switch
   MDI                      MDIX

because the switch already provided the complementary wiring.

What Is a Crossover Cable?

A crossover cable intentionally crosses the required Ethernet pairs.

For classic 10/100 Ethernet, the relevant transmit and receive pairs are exchanged.

Conceptually:

TX ---------------- RX
RX ---------------- TX

Historically, this allowed similar devices to communicate.

For example:

PC ---------------- PC
MDI                 MDI

Without a crossover, the two devices could effectively have TX facing TX and RX facing RX.

A crossover cable corrected that.

Traditional Ethernet Cabling Rules

Before Auto MDI/MDIX became common, networking students and technicians often learned the following rule:

Unlike devices → Straight-through cable

Examples:

PC -------- Switch
PC -------- Hub
Router ---- Switch

Like devices → Crossover cable

Examples:

PC -------- PC
Switch ---- Switch
Hub ------- Hub

This was a useful practical rule, although the underlying reason was really MDI versus MDIX port orientation, not simply whether the devices had the same name.

What Does Auto MDI/MDIX Do?

Auto MDI/MDIX removes the need for the administrator or technician to manually determine which orientation is required.

The Ethernet PHY determines whether the connection needs to operate in:

MDI

or:

MDIX

orientation.

If the pairs need to be crossed, the PHY performs the necessary crossover electronically.

Intel describes its Ethernet controller PHY as automatically determining whether it needs to cross between pairs so that a crossover cable is not required.

Therefore:

PC -------- Straight Cable -------- PC

can work when Auto MDI/MDIX is supported.

Likewise:

Switch ---- Straight Cable ---- Switch

can work.

Even a crossover cable may work where it was traditionally unnecessary because the ports can compensate automatically.

How Auto MDI/MDIX Works

The exact PHY implementation varies, but the basic process can be understood in several stages.

Step 1: Cable Is Connected

When you insert the RJ45 cable:

NIC
 |
 | Ethernet cable
 |
Switch

the physical-layer hardware begins establishing the Ethernet link.

The relevant hardware is generally called the PHY.

PHY means:

Physical Layer Transceiver

It handles physical Ethernet signaling and functions such as link detection and, depending on the Ethernet implementation, capabilities including Auto-Negotiation and MDI/MDIX resolution.

Step 2: PHY Determines the Required Pair Orientation

The PHY determines whether the physical connection requires normal MDI orientation or the crossover orientation.

Conceptually, it needs to establish:

Local transmit ↔ Remote receive
Local receive  ↔ Remote transmit

rather than leaving an incompatible orientation.

Step 3: Internal Crossover Is Applied If Necessary

If the cable orientation does not match what is required, the PHY can internally change its MDI/MDIX configuration.

Conceptually:

Physical RJ45 Pins
       |
       V
+----------------+
| Ethernet PHY   |
|                |
| MDI / MDIX     |
| switching      |
+----------------+
       |
       V
Ethernet controller

No physical rewiring of the cable occurs.

The adjustment happens electronically inside the Ethernet interface.

Step 4: Link Establishment Continues

Once a compatible physical orientation is established, the Ethernet link can proceed with the other required PHY processes.

The link LEDs may then indicate that a physical link has been established.

Auto MDI/MDIX and Auto-Negotiation Are Not the Same Thing

This is an important distinction.

Auto-Negotiation and Auto MDI/MDIX solve different problems.

Auto-Negotiation

Determines or coordinates link capabilities such as:

• supported Ethernet mode
• speed
• duplex
• other PHY capabilities depending on the standard

Auto MDI/MDIX

Deals with:

• physical pair orientation
• MDI versus MDIX
• automatic crossover handling

A useful simplification is:

Auto-Negotiation
      ↓
How should the Ethernet link operate?

Auto MDI/MDIX
      ↓
Do the physical pair connections need crossover handling?

They are related PHY functions, but they should not be treated as two names for the same feature.

On some Cisco implementations, Auto-MDIX depends on Auto-Negotiation configuration. Cisco documents that Auto-MDI/MDIX is enabled when either speed or duplex is set to auto-negotiate, while fixing both can disable Auto-MDIX on those interfaces.

Therefore, the exact interaction can depend on the Ethernet standard, PHY, NIC, switch and driver.

Auto MDI/MDIX in Gigabit Ethernet

Auto MDI/MDIX is particularly relevant when discussing 1000BASE-T Gigabit Ethernet.

Gigabit Ethernet over ordinary twisted-pair copper differs substantially from classic 10/100 Ethernet.

1000BASE-T uses all four twisted pairs for bidirectional signaling.

A simplified representation is:

Pair 1 ↔ Data
Pair 2 ↔ Data
Pair 3 ↔ Data
Pair 4 ↔ Data

rather than thinking only in terms of the dedicated TX pair and RX pair model commonly taught for 10BASE-T and 100BASE-TX.

The IEEE 802.3 specifications for 1000BASE-T include automatic MDI/MDI-X configuration requirements, and 1000BASE-T also requires Auto-Negotiation support.

Intel's current Ethernet adapter documentation similarly states that its Gigabit and 10-Gigabit server adapters using copper connections automatically accommodate MDI or MDI-X connections.

10/100 Ethernet vs Gigabit Ethernet

Feature	10/100 Ethernet	1000BASE-T
Common standards	10BASE-T / 100BASE-TX	1000BASE-T
Pair usage	Traditionally two pairs for 10/100	Four pairs
Dedicated TX/RX pair concept	Yes, useful model	Signaling is bidirectional across pairs
Crossover historically important	Yes	Much less of a practical concern
Auto MDI/MDIX	Device dependent	Integral to modern 1000BASE-T implementations
Auto-Negotiation	Common but legacy exceptions exist	Required for 1000BASE-T PHY operation

Does Auto MDI/MDIX Mean Any Ethernet Cable Will Work?

No.

This is an important misconception.

Auto MDI/MDIX can correct pair orientation/crossover requirements.

It cannot repair a physically defective cable.

For example, it cannot magically correct:

• broken conductors
• poor RJ45 termination
• excessive cable length
• severe electromagnetic interference
• damaged connectors
• bad patch-panel termination
• unsuitable cable category for the intended link
• excessive signal loss
• split pairs
• certain incorrect wiring faults

So:

Wrong crossover orientation
        ↓
Auto MDI/MDIX may correct it

Broken or badly terminated cable
        ↓
Auto MDI/MDIX cannot repair it

Does Auto MDI/MDIX Correct T568A vs T568B?

This needs careful explanation.

T568A and T568B are valid structured cabling termination schemes.

A cable terminated:

T568A → T568A

is straight-through.

A cable terminated:

T568B → T568B

is also straight-through.

The important point is consistency.

Auto MDI/MDIX should not be considered a substitute for correctly terminating Ethernet cabling.

A badly wired connector should be fixed rather than relying on the NIC to compensate for wiring mistakes.

Does Auto MDI/MDIX Increase Network Speed?

No.

Auto MDI/MDIX does not make Ethernet faster.

It primarily improves:

connection compatibility and convenience.

For example, it does not convert:

100 Mbps

into:

1 Gbps

The negotiated link speed still depends on factors including:

• NIC capabilities
• switch capabilities
• Ethernet standard
• cable quality/category
• cable condition
• configuration
• driver/firmware behavior
• link partner

Does Auto MDI/MDIX Affect Duplex?

Not directly.

Duplex determines whether communication can operate in both directions simultaneously.

For example:

Full Duplex

Device A ======> Device B
Device A <====== Device B

Auto MDI/MDIX instead concerns the physical crossover/orientation needed for the link.

So these are separate concepts:

Feature	Purpose
Auto MDI/MDIX	Correct MDI/MDIX pair orientation
Auto-Negotiation	Establish compatible link capabilities
Speed	10/100/1000 Mbps etc.
Duplex	Half or Full
Flow Control	Controls handling of congestion in supported scenarios

Why Do Modern PCs Usually Not Need Crossover Cables?

Suppose you directly connect:

Laptop A
   |
   | Cat6 straight-through cable
   |
Laptop B

Historically, a PC-to-PC connection generally required a crossover cable.

Modern Ethernet PHYs commonly support Auto MDI/MDIX, so one or both interfaces can establish the correct orientation automatically.

Intel explicitly documents that Auto-MDI-X on its Gigabit copper adapters allows two adapters to be connected directly without a crossover cable.

This is one reason crossover cables have largely disappeared from everyday networking.

Is a Crossover Cable Completely Obsolete?

For most modern networks, almost—but not absolutely.

Crossover cables can still matter when dealing with:

• older Ethernet adapters
• legacy switches
• old hubs
• embedded devices
• industrial equipment
• specialized networking hardware
• devices without Auto MDI/MDIX
• certain forced/manual port configurations

Therefore, technicians working with old hardware should still understand crossover cabling.

What Happens If Only One Device Supports Auto MDI/MDIX?

In many implementations, one Auto-MDIX-capable side is sufficient.

For example:

Old device
No Auto MDIX
      |
      |
Modern switch
Auto MDIX

The modern device can detect the necessary orientation and compensate.

Cisco documentation shows supported configurations where a link can still come up when Auto-MDIX is enabled on one side and disabled on the other, including with otherwise incorrect cabling.

This interoperability is one of the major advantages of the technology.

What If Both Devices Support Auto MDI/MDIX?

That is completely normal.

For example:

Modern PC
Auto MDIX
     |
     |
Modern Switch
Auto MDIX

Both PHYs participate in establishing a valid link.

IEEE-defined behavior includes mechanisms for avoiding both sides continually changing their crossover state at the same time. Intel describes a randomized algorithm for situations where both PHYs implement MDI/MDI-X crossover.

Auto MDI/MDIX in Network Cards

Modern copper Ethernet NICs commonly implement the feature inside the PHY.

This can include:

• onboard motherboard Ethernet
• PCI Ethernet cards
• PCI Express Gigabit LAN cards
• server network adapters
• USB-to-Ethernet adapters
• docking-station Ethernet ports

However, support should be verified from the specifications of the particular controller or adapter rather than assumed for every product.

Auto MDI/MDIX in Network Switches

Modern Ethernet switches also commonly support Auto MDI/MDIX.

A typical modern switch port can therefore handle:

PC → Switch
Switch → Switch
Router → Switch
Access Point → Switch
Server → Switch

without requiring the technician to choose between straight-through and crossover patch cables solely on the basis of the connected device types.

Cisco, for example, documents Auto-MDIX as enabled by default on various switch platforms.

Auto MDI/MDIX and Fiber Ethernet

Auto MDI/MDIX is primarily a twisted-pair copper Ethernet concept.

Do not apply the same RJ45 MDI/MDIX terminology blindly to fiber connections.

For example, Cisco documentation notes that Auto-MDIX is not supported on 1000BASE-SX or 1000BASE-LX SFP interfaces.

Fiber has its own transmit/receive considerations and connector arrangements.

Can Auto MDI/MDIX Be Disabled?

On some devices, yes.

A managed switch may expose options such as:

Auto
MDI
MDIX

Cisco Nexus documentation, for example, exposes administrative MDIX modes of Auto, MDI and MDI-X on applicable interfaces.

Some Ethernet controllers also provide registers or driver-level mechanisms for controlling MDI/MDIX behavior.

However, most ordinary users should leave the feature at its default automatic setting.

Should You Disable Auto MDI/MDIX?

Normally:

No.

For ordinary PCs, servers and network switches, automatic operation provides the greatest compatibility.

Manual MDI/MDIX configuration may be useful for:

• network diagnostics
• hardware testing
• specialized industrial equipment
• interoperability testing
• legacy equipment
• controlled lab environments

It generally provides no performance advantage for an ordinary LAN.

Auto MDI/MDIX vs Auto-Negotiation

Because both features are automatic, they are frequently confused.

Feature	Auto MDI/MDIX	Auto-Negotiation
Main purpose	Resolve crossover/orientation	Establish compatible Ethernet operating parameters
Handles straight/crossover issue	Yes	No
Handles speed negotiation	No	Yes
Handles duplex negotiation	No	Yes
PHY function	Yes	Yes
Normally automatic	Yes	Yes
Should usually remain enabled	Yes	Yes

A useful way to remember the difference:

Auto MDI/MDIX determines how the copper pairs should be logically oriented; Auto-Negotiation determines how compatible Ethernet capabilities should be used.

Example: PC Connected to a Switch

Traditional arrangement:

PC                    Switch
MDI                    MDIX
 |                       |
 +---- Straight Cable ---+

This already has the required complementary orientation.

No cable crossover is necessary.

Example: PC Connected Directly to Another PC

Traditional arrangement:

PC                    PC
MDI                   MDI
 |                     |
 +--- Crossover Cable -+

The cable crosses the necessary pairs.

With Auto MDI/MDIX:

Modern PC          Modern PC
Auto MDIX          Auto MDIX
    |                  |
    +-- Straight ------+

The PHY can handle the required crossover internally.

Example: Switch Connected to Another Switch

Traditional:

Switch                Switch
MDIX                   MDIX
  |                      |
  +--- Crossover Cable --+

Modern:

Switch                Switch
Auto MDIX             Auto MDIX
  |                      |
  +--- Straight Cable ---+

Either suitable cable orientation can normally be handled automatically.

How to Check Whether Your NIC Supports Auto MDI/MDIX

Windows does not provide one universal command that guarantees a simple:

Auto MDIX = Enabled

result for every network adapter.

The feature is largely implemented in the PHY and may not be exposed as a configurable Windows property.

The best sources are:

1. Network controller datasheet
2. NIC manufacturer's documentation
3. Driver documentation
4. Device Manager advanced properties
5. Managed switch port documentation

Checking NIC Advanced Properties in Windows

Open:

Device Manager

Expand:

Network adapters

Right-click your Ethernet adapter and select:

Properties

Then open:

Advanced

Depending on the NIC and driver, you may see settings related to:

• Speed & Duplex
• Flow Control
• Energy Efficient Ethernet
• Gigabit options
• Auto Disable Gigabit
• power-saving features

A dedicated Auto-MDIX option may not be exposed even if the hardware supports it.

That is normal.

PowerShell Commands Useful for Checking Ethernet Adapters

You can list network adapters with:

Get-NetAdapter

To display advanced driver properties:

Get-NetAdapterAdvancedProperty

For a particular adapter:

Get-NetAdapterAdvancedProperty -Name "Ethernet"

These commands do not guarantee that Auto MDI/MDIX will appear. The available properties depend on the network adapter and its driver.

Administrator privileges may be required for some configuration changes, although basic information queries often work without elevation.

Troubleshooting: Ethernet Link Does Not Come Up

If a modern Ethernet connection does not work, do not immediately assume that MDI/MDIX is the problem.

Check the following.

1. Check Link LEDs

Look at the Ethernet LEDs on:

• NIC
• switch
• router
• docking station

No link light may indicate a Layer 1 problem.

2. Replace the Ethernet Cable

Try a known-good Cat5e, Cat6 or other appropriate cable for the intended Ethernet standard.

A damaged conductor can prevent link establishment.

3. Check All Four Pairs for Gigabit Ethernet

A common practical problem occurs when a poorly terminated cable works at:

100 Mbps

but fails to establish:

1 Gbps

1000BASE-T uses all four twisted pairs, so faults that did not prevent a 10/100 link may prevent Gigabit operation.

4. Check Speed and Duplex

In Windows:

Device Manager
→ Network adapters
→ Ethernet Adapter
→ Properties
→ Advanced
→ Speed & Duplex

Normally, leave it at:

Auto Negotiation

unless you have a specific technical reason to force a setting.

Both ends should be configured compatibly.

5. Test Another Switch Port

Move the cable to another known-good port.

This helps determine whether the problem is:

NIC
Cable
Switch port
Configuration

6. Check the RJ45 Termination

Inspect the plug for:

• loose conductors
• incomplete insertion
• damaged contacts
• incorrect crimping
• split pairs
• incorrect wiring

A cable tester is highly useful for troubleshooting structured cabling.

7. Check for Legacy Hardware

If one or both devices are very old and the link refuses to establish, try the historically correct cable type.

For example:

Old PC → Old PC

Try a crossover cable.

Likewise:

Old switch → Old switch

may require crossover cabling.

Common Misconceptions About Auto MDI/MDIX

Myth 1: Auto MDIX Automatically Increases Network Speed

False.

It handles pair orientation, not link performance.

Myth 2: Auto MDIX Can Fix Any Incorrect Ethernet Wiring

False.

It cannot repair damaged or improperly constructed cabling.

Myth 3: Auto MDIX and Auto-Negotiation Are the Same Feature

False.

They perform different PHY functions.

Myth 4: Every Ethernet Port Ever Manufactured Supports Auto MDIX

False.

Legacy hardware may not support it.

Myth 5: Crossover Cables Can Never Be Used on Modern Equipment

False.

Modern Auto-MDIX equipment can generally accommodate either orientation.

Myth 6: A Straight-Through Cable Always Means T568B

False.

Both of these are straight-through:

T568A → T568A
T568B → T568B

Advantages of Auto MDI/MDIX

Auto MDI/MDIX provides several practical advantages.

Easier Network Installation

Technicians do not normally need separate straight-through and crossover patch cables.

Fewer Cabling Errors

Using the "wrong" crossover orientation is much less likely to prevent the link.

Easier Direct Connections

Modern PCs can often be connected directly using an ordinary Ethernet patch cable.

Simplified Inventory

IT departments do not need to maintain large numbers of specially identified crossover cables.

Better Compatibility

Modern devices can often connect more easily to older equipment.

Easier Troubleshooting

Cable type can often be eliminated as one possible cause of a connection problem.

Limitations of Auto MDI/MDIX

Auto MDI/MDIX does not solve every physical-layer problem.

It cannot compensate for:

• defective cables
• broken conductors
• excessive cable runs
• damaged RJ45 connectors
• inappropriate cabling
• faulty switch ports
• faulty network adapters
• severe electromagnetic interference
• incompatible optical interfaces
• all forms of incorrect termination

It should therefore be viewed as automatic crossover handling, not automatic Ethernet cable repair.

Best Practices

For modern Ethernet networks:

1. Use correctly terminated straight-through patch cables as the normal default.
2. Follow T568A or T568B consistently according to your cabling standard.
3. Leave Auto MDI/MDIX enabled unless there is a specific reason to change it.
4. Normally leave Ethernet speed and duplex on Auto-Negotiation.
5. Use appropriate cable categories for the required Ethernet speed and distance.
6. Test questionable cabling with a proper cable tester.
7. Do not use Auto MDI/MDIX as an excuse for poor termination.
8. Keep crossover cables only when supporting legacy or specialized equipment.
9. Check manufacturer documentation before changing PHY or switch-port settings.

Frequently Asked Questions

What does Auto MDI/MDIX mean?

It means that an Ethernet PHY can automatically determine whether MDI or MDI-X pair orientation is required and perform the necessary crossover internally.

What is MDI?

MDI stands for Media Dependent Interface and traditionally describes the Ethernet port arrangement associated with end devices such as computers.

What is MDIX?

MDIX stands for Media Dependent Interface with Crossover and traditionally describes the complementary port arrangement used by equipment such as hubs and switches.

What is Auto MDI-X?

Auto MDI-X is another common way of referring to automatic MDI/MDIX crossover detection and configuration.

Do modern network cards support Auto MDI/MDIX?

Many modern copper Ethernet adapters do, especially Gigabit Ethernet adapters, but support should be verified for the particular controller or device.

Do I need a crossover cable to connect two modern computers?

Usually not. If the Ethernet interfaces support Auto MDI/MDIX, an ordinary correctly wired Ethernet patch cable can normally be used.

Do I need a crossover cable between two modern switches?

Usually not when the switch ports support Auto MDI/MDIX.

Can I use a crossover cable on an Auto-MDIX port?

Generally yes. The PHY can normally detect the required orientation and compensate.

Is Auto MDIX the same as Auto-Negotiation?

No. Auto MDIX handles crossover/orientation, while Auto-Negotiation establishes compatible Ethernet operating capabilities such as speed and duplex.

Does Auto MDIX improve network speed?

No. It improves cabling compatibility rather than increasing bandwidth.

Does Auto MDIX work with Gigabit Ethernet?

Yes. Automatic MDI/MDI-X behavior is an important part of modern 1000BASE-T operation.

Does Auto MDIX work with fiber?

The traditional MDI/MDIX crossover concept discussed here applies to twisted-pair copper Ethernet. Fiber interfaces have different physical connection requirements.

Why does my Ethernet cable work at 100 Mbps but not 1 Gbps?

One possible reason is a wiring or termination problem affecting one or more pairs. 1000BASE-T uses all four twisted pairs, so a cable fault can prevent Gigabit operation even when a lower-speed link is possible.

Should I manually set MDI or MDIX?

For ordinary modern networks, no. Automatic mode is normally preferable unless you are troubleshooting or working with specialized or legacy hardware.

Should Speed & Duplex be set to Auto Negotiation?

Normally yes. Manual configuration should generally be used only when there is a known interoperability or network-design requirement.

Conclusion

Auto MDI/MDIX is one of the small Ethernet technologies that made modern networking significantly easier.

Traditional Ethernet installations required technicians to understand whether the connected ports were MDI or MDIX and then select either a straight-through or crossover cable.

The historical rule was approximately:

PC → Switch       = Straight-through
PC → PC           = Crossover
Switch → Switch   = Crossover

With Auto MDI/MDIX, the Ethernet PHY can automatically determine the required MDI/MDIX orientation and electronically compensate.

As a result, modern networking is generally:

Connect the appropriate Ethernet patch cable
                ↓
PHY determines the required orientation
                ↓
Auto MDI/MDIX handles crossover if necessary
                ↓
Ethernet link is established

This is why crossover cables, once an essential part of every network technician's toolkit, are now rarely needed in ordinary modern LAN installations.

However, understanding MDI, MDIX, straight-through wiring, crossover wiring, Ethernet PHYs and Auto-Negotiation remains valuable—especially when troubleshooting legacy hardware, unusual Ethernet equipment, industrial devices or physical-layer network problems.

 

#AutoMDI #AutoMDIX #AutoMDI_X #MDI #MDIX #Ethernet #EthernetNetworking #NetworkCard #NIC #LANCard #GigabitEthernet #FastEthernet #1000BaseT #100BaseTX #10BaseT #EthernetPHY #PHY #AutoNegotiation #NetworkSwitch #EthernetSwitch #RJ45 #RJ45Cable #EthernetCable #NetworkCable #CrossoverCable #StraightThroughCable #T568A #T568B #EthernetWiring #EthernetPinout #LAN #Networking #ComputerNetworking #NetworkBasics #NetworkTroubleshooting #EthernetTroubleshooting #CableTroubleshooting #GigabitLAN #PCIeLANCard #NetworkAdapter #WindowsNetworking #SwitchPort #EthernetStandards #IEEE8023 #PhysicalLayer #TwistedPair #Cat5e #Cat6 #Cat6a #BisonKnowledgebase