How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?
I am trying to understand how a collision occurs in Ethernet, especially when a duplex mismatch exists or when on a legacy Ethernet network two nodes transmit simultaneously.
Everyone explains the collision in an upper level (two frames collide when the one is being sent and the other is being received). However, the graph below shows that there are different circuits for Rx and Tx. How a collision can happen since there are dedicated circuits for sending and receiving frames?

ethernet autonegotiation ieee-802.3x
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am trying to understand how a collision occurs in Ethernet, especially when a duplex mismatch exists or when on a legacy Ethernet network two nodes transmit simultaneously.
Everyone explains the collision in an upper level (two frames collide when the one is being sent and the other is being received). However, the graph below shows that there are different circuits for Rx and Tx. How a collision can happen since there are dedicated circuits for sending and receiving frames?

ethernet autonegotiation ieee-802.3x
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am trying to understand how a collision occurs in Ethernet, especially when a duplex mismatch exists or when on a legacy Ethernet network two nodes transmit simultaneously.
Everyone explains the collision in an upper level (two frames collide when the one is being sent and the other is being received). However, the graph below shows that there are different circuits for Rx and Tx. How a collision can happen since there are dedicated circuits for sending and receiving frames?

ethernet autonegotiation ieee-802.3x
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am trying to understand how a collision occurs in Ethernet, especially when a duplex mismatch exists or when on a legacy Ethernet network two nodes transmit simultaneously.
Everyone explains the collision in an upper level (two frames collide when the one is being sent and the other is being received). However, the graph below shows that there are different circuits for Rx and Tx. How a collision can happen since there are dedicated circuits for sending and receiving frames?

ethernet autonegotiation ieee-802.3x
ethernet autonegotiation ieee-802.3x
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 3 hours ago
Cown
6,34431030
6,34431030
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 3 hours ago
Christos DalamagkasChristos Dalamagkas
111
111
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Christos Dalamagkas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Great question.
In full duplex, there is a dedicated channel for traffic from "left to right" and a dedicated channel from traffic from "right to left":

Therefore, in full duplex, collisions are impossible -- even if both NIC's transmit at the same time.
In half-duplex, however, traffic in either direction is meant to only use the wire, one direction at a time. So while physically, there is still dedicated channels, logically if one NIC receives something while it is transmitting, it logs it as a collision. The bits/signal do not actually "collide" on the wire -- a collision counter is simply incremented when the NIC is Receiving and Transmitting at the same time.
add a comment |
A hub is really just a powered cable that repeats every signal it receives on one interface to all the other interfaces. If two devices transmit at the same time to the receive of the hub interfaces, the hub repeats both signals at the same time to the transmit of all the other hub interfaces, and both signals received will collide at the transmit of the other interfaces, thus you have a collision where all the other interfaces have garbage signals because it is two signals at the same time.
Think of it this way, the receive of every hub interface is wired to the transmit of every other interface. Inside the hub, the transmit and receive are connected, even if they are separate at the interface.
Contrast that with a switch, where each link is terminated at the switch interface, and the switch does not have the interfaces wired together. Instead the switch has logic (usually embedded in hardware) to determine where to send frames it receives on one interface, and to prevent collisions inside the switch.
A switch is a high-density bridge. The original bridges were like PCs with multiple interfaces. You would not expect a PC with multiple interfaces to have collisions if it received simultaneous frames on multiple interfaces.
add a comment |
Please note that 10Base2 or 10Base5 shared the same medium, e.g. the same cable.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Christos Dalamagkas is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57521%2fhow-exactly-does-an-ethernet-collision-happen-in-the-cable-since-nodes-use-diff%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Great question.
In full duplex, there is a dedicated channel for traffic from "left to right" and a dedicated channel from traffic from "right to left":

Therefore, in full duplex, collisions are impossible -- even if both NIC's transmit at the same time.
In half-duplex, however, traffic in either direction is meant to only use the wire, one direction at a time. So while physically, there is still dedicated channels, logically if one NIC receives something while it is transmitting, it logs it as a collision. The bits/signal do not actually "collide" on the wire -- a collision counter is simply incremented when the NIC is Receiving and Transmitting at the same time.
add a comment |
Great question.
In full duplex, there is a dedicated channel for traffic from "left to right" and a dedicated channel from traffic from "right to left":

Therefore, in full duplex, collisions are impossible -- even if both NIC's transmit at the same time.
In half-duplex, however, traffic in either direction is meant to only use the wire, one direction at a time. So while physically, there is still dedicated channels, logically if one NIC receives something while it is transmitting, it logs it as a collision. The bits/signal do not actually "collide" on the wire -- a collision counter is simply incremented when the NIC is Receiving and Transmitting at the same time.
add a comment |
Great question.
In full duplex, there is a dedicated channel for traffic from "left to right" and a dedicated channel from traffic from "right to left":

Therefore, in full duplex, collisions are impossible -- even if both NIC's transmit at the same time.
In half-duplex, however, traffic in either direction is meant to only use the wire, one direction at a time. So while physically, there is still dedicated channels, logically if one NIC receives something while it is transmitting, it logs it as a collision. The bits/signal do not actually "collide" on the wire -- a collision counter is simply incremented when the NIC is Receiving and Transmitting at the same time.
Great question.
In full duplex, there is a dedicated channel for traffic from "left to right" and a dedicated channel from traffic from "right to left":

Therefore, in full duplex, collisions are impossible -- even if both NIC's transmit at the same time.
In half-duplex, however, traffic in either direction is meant to only use the wire, one direction at a time. So while physically, there is still dedicated channels, logically if one NIC receives something while it is transmitting, it logs it as a collision. The bits/signal do not actually "collide" on the wire -- a collision counter is simply incremented when the NIC is Receiving and Transmitting at the same time.
answered 1 hour ago
EddieEddie
9,36022462
9,36022462
add a comment |
add a comment |
A hub is really just a powered cable that repeats every signal it receives on one interface to all the other interfaces. If two devices transmit at the same time to the receive of the hub interfaces, the hub repeats both signals at the same time to the transmit of all the other hub interfaces, and both signals received will collide at the transmit of the other interfaces, thus you have a collision where all the other interfaces have garbage signals because it is two signals at the same time.
Think of it this way, the receive of every hub interface is wired to the transmit of every other interface. Inside the hub, the transmit and receive are connected, even if they are separate at the interface.
Contrast that with a switch, where each link is terminated at the switch interface, and the switch does not have the interfaces wired together. Instead the switch has logic (usually embedded in hardware) to determine where to send frames it receives on one interface, and to prevent collisions inside the switch.
A switch is a high-density bridge. The original bridges were like PCs with multiple interfaces. You would not expect a PC with multiple interfaces to have collisions if it received simultaneous frames on multiple interfaces.
add a comment |
A hub is really just a powered cable that repeats every signal it receives on one interface to all the other interfaces. If two devices transmit at the same time to the receive of the hub interfaces, the hub repeats both signals at the same time to the transmit of all the other hub interfaces, and both signals received will collide at the transmit of the other interfaces, thus you have a collision where all the other interfaces have garbage signals because it is two signals at the same time.
Think of it this way, the receive of every hub interface is wired to the transmit of every other interface. Inside the hub, the transmit and receive are connected, even if they are separate at the interface.
Contrast that with a switch, where each link is terminated at the switch interface, and the switch does not have the interfaces wired together. Instead the switch has logic (usually embedded in hardware) to determine where to send frames it receives on one interface, and to prevent collisions inside the switch.
A switch is a high-density bridge. The original bridges were like PCs with multiple interfaces. You would not expect a PC with multiple interfaces to have collisions if it received simultaneous frames on multiple interfaces.
add a comment |
A hub is really just a powered cable that repeats every signal it receives on one interface to all the other interfaces. If two devices transmit at the same time to the receive of the hub interfaces, the hub repeats both signals at the same time to the transmit of all the other hub interfaces, and both signals received will collide at the transmit of the other interfaces, thus you have a collision where all the other interfaces have garbage signals because it is two signals at the same time.
Think of it this way, the receive of every hub interface is wired to the transmit of every other interface. Inside the hub, the transmit and receive are connected, even if they are separate at the interface.
Contrast that with a switch, where each link is terminated at the switch interface, and the switch does not have the interfaces wired together. Instead the switch has logic (usually embedded in hardware) to determine where to send frames it receives on one interface, and to prevent collisions inside the switch.
A switch is a high-density bridge. The original bridges were like PCs with multiple interfaces. You would not expect a PC with multiple interfaces to have collisions if it received simultaneous frames on multiple interfaces.
A hub is really just a powered cable that repeats every signal it receives on one interface to all the other interfaces. If two devices transmit at the same time to the receive of the hub interfaces, the hub repeats both signals at the same time to the transmit of all the other hub interfaces, and both signals received will collide at the transmit of the other interfaces, thus you have a collision where all the other interfaces have garbage signals because it is two signals at the same time.
Think of it this way, the receive of every hub interface is wired to the transmit of every other interface. Inside the hub, the transmit and receive are connected, even if they are separate at the interface.
Contrast that with a switch, where each link is terminated at the switch interface, and the switch does not have the interfaces wired together. Instead the switch has logic (usually embedded in hardware) to determine where to send frames it receives on one interface, and to prevent collisions inside the switch.
A switch is a high-density bridge. The original bridges were like PCs with multiple interfaces. You would not expect a PC with multiple interfaces to have collisions if it received simultaneous frames on multiple interfaces.
edited 1 hour ago
answered 1 hour ago
Ron Maupin♦Ron Maupin
66.7k1369124
66.7k1369124
add a comment |
add a comment |
Please note that 10Base2 or 10Base5 shared the same medium, e.g. the same cable.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
add a comment |
Please note that 10Base2 or 10Base5 shared the same medium, e.g. the same cable.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
add a comment |
Please note that 10Base2 or 10Base5 shared the same medium, e.g. the same cable.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Please note that 10Base2 or 10Base5 shared the same medium, e.g. the same cable.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
Patrick TerlistenPatrick Terlisten
11
11
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Patrick Terlisten is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
add a comment |
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
Still I have the same question regarding 100base-tx, in case we have duplex mismatch and the nodeA is half duplex and nodeB full duplex. Suppose nodeA has an MDI interface and nodeB an MDI-X one. NodeB transmits from pins 3 and 4 and nodeB only receives from 3 and 4. How a collision can happen in nodeA since it only receives from these pins?
– Christos Dalamagkas
2 hours ago
add a comment |
Christos Dalamagkas is a new contributor. Be nice, and check out our Code of Conduct.
Christos Dalamagkas is a new contributor. Be nice, and check out our Code of Conduct.
Christos Dalamagkas is a new contributor. Be nice, and check out our Code of Conduct.
Christos Dalamagkas is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57521%2fhow-exactly-does-an-ethernet-collision-happen-in-the-cable-since-nodes-use-diff%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown