Tjyylli

How to type this arrow in math mode?

Looking for Correct Greek Translation for Heraclitus

Feature engineering suggestion required

Why is the Constellation's nose gear so long?

Am I thawing this London Broil safely?

Have you ever entered Singapore using a different passport or name?

Why didn't the Event Horizon Telescope team mention Sagittarius A*?

Did 3000BC Egyptians use meteoric iron weapons?

Resizing object distorts it (Illustrator CC 2018)

"as much details as you can remember"

Why do we hear so much about the Trump administration deciding to impose and then remove tariffs?

How to deal with fear of taking dependencies

Are there any other methods to apply to solving simultaneous equations?

If I score a critical hit on an 18 or higher, what are my chances of getting a critical hit if I roll 3d20?

Can one be advised by a professor who is very far away?

Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown?

Is flight data recorder erased after every flight?

How technical should a Scrum Master be to effectively remove impediments?

Button changing it's text & action. Good or terrible?

Is a "Democratic" Oligarchy-Style System Possible?

What to do when moving next to a bird sanctuary with a loosely-domesticated cat?

What is the most effective way of iterating a std::vector and why?

Worn-tile Scrabble

Why was M87 targetted for the Event Horizon Telescope instead of Sagittarius A*?

Client not responding TCP SYN-ACK packet ethernet driver

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

1

I am developing an Ethernet driver and implementing TCP exchange code. To test my TCP code this is the scenario (monitored on wireshark):

Server: Custom Ethernet device

Client: PC

1. I opened TCP client socket from hercules utility.


2. I am able to see ARP request and response exchange from the ethernet device and hercules.


3. After ARP request is served, client sends TCP SYN packet and server repsonses with SYN-ACK.


4. To complete 3 way handshake client should send ACK at the end which I am not getting and hercules says TCP connection time out.

I need to diagnose the possible issue of why the client is not acknowledging SYN-ACK to complete 3-way handshake.

drivers ethernet tcp wireshark

share|improve this question

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI 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 | 

1

I am developing an Ethernet driver and implementing TCP exchange code. To test my TCP code this is the scenario (monitored on wireshark):

Server: Custom Ethernet device

Client: PC

1. I opened TCP client socket from hercules utility.


2. I am able to see ARP request and response exchange from the ethernet device and hercules.


3. After ARP request is served, client sends TCP SYN packet and server repsonses with SYN-ACK.


4. To complete 3 way handshake client should send ACK at the end which I am not getting and hercules says TCP connection time out.

I need to diagnose the possible issue of why the client is not acknowledging SYN-ACK to complete 3-way handshake.

drivers ethernet tcp wireshark

share|improve this question

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI 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 developing an Ethernet driver and implementing TCP exchange code. To test my TCP code this is the scenario (monitored on wireshark):

Server: Custom Ethernet device

Client: PC

1. I opened TCP client socket from hercules utility.


2. I am able to see ARP request and response exchange from the ethernet device and hercules.


3. After ARP request is served, client sends TCP SYN packet and server repsonses with SYN-ACK.


4. To complete 3 way handshake client should send ACK at the end which I am not getting and hercules says TCP connection time out.

I need to diagnose the possible issue of why the client is not acknowledging SYN-ACK to complete 3-way handshake.

drivers ethernet tcp wireshark

share|improve this question

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited yesterday

Tiago Caldeira

1,224521

edited yesterday

Tiago Caldeira

1,224521

asked yesterday

RAJ JOHRIRAJ JOHRI

82

New contributor

RAJ JOHRI is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked yesterday

RAJ JOHRIRAJ JOHRI

82

1 Answer
1

active

oldest

votes

0

Where are you capturing, on the client or the server? If you're capturing on the client, then try enabling IP header checksum validation via "Edit -> Preferences -> Protocols -> IPv4 -> Validate the IPv4 checksum if possible".

It looks to me like the IP header checksum of the server's SYN/ACK packet is 0, thus invalid, and if that's the case, you'll have to compute it; otherwise the client machine will drop the IP packet as being invalid.

Note that if you're capturing on the client and the client's IP header checksum of the SYN packet is 0, then as Wireshark indicates, that's probably because the client machine is configured for "IP checksum offload" and Wireshark is receiving the packets before the checksum is computed by the hardware.

If you really want to see what's going on, you should capture on a separate machine using a SPAN port or TAP; that way you will receive packets with proper checksums computed. For more information on capturing, you might want to have a look at Wireshark's Ethernet capture setup wiki page, or Jasper Bongertz' very helpful 6-part Network Capture Playbook, beginning with Part 1 - Ethernet Basics in which is referenced another one of his articles, The drawbacks of local packet captures.

share|improve this answer

edited 17 hours ago

answered yesterday

Christopher MaynardChristopher Maynard

35617

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks Christopher. I am new user to superuser and don't have much credit score to up vote you. You gave nice and useful explanation solved my problem. Thanks once again. Some please up vote Christopher's answer.
  
  – RAJ JOHRI
  18 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

RAJ JOHRI is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1423242%2fclient-not-responding-tcp-syn-ack-packet-ethernet-driver%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Where are you capturing, on the client or the server? If you're capturing on the client, then try enabling IP header checksum validation via "Edit -> Preferences -> Protocols -> IPv4 -> Validate the IPv4 checksum if possible".

It looks to me like the IP header checksum of the server's SYN/ACK packet is 0, thus invalid, and if that's the case, you'll have to compute it; otherwise the client machine will drop the IP packet as being invalid.

Note that if you're capturing on the client and the client's IP header checksum of the SYN packet is 0, then as Wireshark indicates, that's probably because the client machine is configured for "IP checksum offload" and Wireshark is receiving the packets before the checksum is computed by the hardware.

If you really want to see what's going on, you should capture on a separate machine using a SPAN port or TAP; that way you will receive packets with proper checksums computed. For more information on capturing, you might want to have a look at Wireshark's Ethernet capture setup wiki page, or Jasper Bongertz' very helpful 6-part Network Capture Playbook, beginning with Part 1 - Ethernet Basics in which is referenced another one of his articles, The drawbacks of local packet captures.

share|improve this answer

edited 17 hours ago

answered yesterday

Christopher MaynardChristopher Maynard

35617

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks Christopher. I am new user to superuser and don't have much credit score to up vote you. You gave nice and useful explanation solved my problem. Thanks once again. Some please up vote Christopher's answer.
  
  – RAJ JOHRI
  18 hours ago
  

  
  
  
  

add a comment | 

0

Where are you capturing, on the client or the server? If you're capturing on the client, then try enabling IP header checksum validation via "Edit -> Preferences -> Protocols -> IPv4 -> Validate the IPv4 checksum if possible".

It looks to me like the IP header checksum of the server's SYN/ACK packet is 0, thus invalid, and if that's the case, you'll have to compute it; otherwise the client machine will drop the IP packet as being invalid.

Note that if you're capturing on the client and the client's IP header checksum of the SYN packet is 0, then as Wireshark indicates, that's probably because the client machine is configured for "IP checksum offload" and Wireshark is receiving the packets before the checksum is computed by the hardware.

If you really want to see what's going on, you should capture on a separate machine using a SPAN port or TAP; that way you will receive packets with proper checksums computed. For more information on capturing, you might want to have a look at Wireshark's Ethernet capture setup wiki page, or Jasper Bongertz' very helpful 6-part Network Capture Playbook, beginning with Part 1 - Ethernet Basics in which is referenced another one of his articles, The drawbacks of local packet captures.

share|improve this answer

edited 17 hours ago

answered yesterday

Christopher MaynardChristopher Maynard

35617

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks Christopher. I am new user to superuser and don't have much credit score to up vote you. You gave nice and useful explanation solved my problem. Thanks once again. Some please up vote Christopher's answer.
  
  – RAJ JOHRI
  18 hours ago
  

  
  
  
  

add a comment | 

Where are you capturing, on the client or the server? If you're capturing on the client, then try enabling IP header checksum validation via "Edit -> Preferences -> Protocols -> IPv4 -> Validate the IPv4 checksum if possible".

It looks to me like the IP header checksum of the server's SYN/ACK packet is 0, thus invalid, and if that's the case, you'll have to compute it; otherwise the client machine will drop the IP packet as being invalid.

Note that if you're capturing on the client and the client's IP header checksum of the SYN packet is 0, then as Wireshark indicates, that's probably because the client machine is configured for "IP checksum offload" and Wireshark is receiving the packets before the checksum is computed by the hardware.

If you really want to see what's going on, you should capture on a separate machine using a SPAN port or TAP; that way you will receive packets with proper checksums computed. For more information on capturing, you might want to have a look at Wireshark's Ethernet capture setup wiki page, or Jasper Bongertz' very helpful 6-part Network Capture Playbook, beginning with Part 1 - Ethernet Basics in which is referenced another one of his articles, The drawbacks of local packet captures.

share|improve this answer

edited 17 hours ago

answered yesterday

Christopher MaynardChristopher Maynard

35617

share|improve this answer

edited 17 hours ago

answered yesterday

Christopher MaynardChristopher Maynard

35617

answered yesterday

Christopher MaynardChristopher Maynard

35617

answered yesterday

Christopher MaynardChristopher Maynard

35617