Тёмный

Process Monitor: Matching Wireshark and Procmon Traces 

Paul Offord
Подписаться 1,2 тыс.
Просмотров 6 тыс.
50% 1

Опубликовано:

 

22 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 8   
@chrismcknight7164
@chrismcknight7164 5 лет назад
THANK YOU! I was looking at the stack trace for my process' TCP Send event and was so confused why the stack initiated with an interrupt for a send, rather than the application code. Your explanation about this corresponding with the ACK, not the send call, now makes perfect sense!
@PaulOfford
@PaulOfford 2 года назад
Certainly had me fooled to start with. Glad it was helpful.
@skeetabomb
@skeetabomb 3 месяца назад
My suspicion on why there is a time difference is that Wireshark 'sees' packets at a different level of the TCP/IP driver stack. I would expect it to be lower down, 'closer' to the wire than ProcMon. I don't know for certain, though, but that seems logical to me.
@PaulOfford
@PaulOfford 2 месяца назад
I think you're right.
@skeetabomb
@skeetabomb 3 месяца назад
Any relation to Viv Offord?
@PaulOfford
@PaulOfford 2 месяца назад
Not knowingly.
Далее
TCP Fundamentals Part 1 // TCP/IP Explained with Wireshark
1:17:24
Кольцо Всевластия от Samsung
01:00
Просмотров 528 тыс.
Finding Malware with Sysinternals Process Explorer
9:26
The Tri Folding Phone Impressions!
11:18
Просмотров 3,2 млн
Windows Servers Can Expose PowerShell on the Web
18:12
Microblogging Quick Start
23:12
Просмотров 750
JS8Call Microblogging Overview
38:14
Просмотров 1,3 тыс.
Кольцо Всевластия от Samsung
01:00
Просмотров 528 тыс.