Timeline for Simplified Windows' tracert command
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2020 at 17:38 | comment | added | Carcigenicate |
@Cukic0d You were right. The timings now roughly match what tracert reports. Thanks again.
|
|
| Nov 17, 2020 at 17:38 | answer | added | Carcigenicate | timeline score: 2 | |
| Nov 17, 2020 at 16:31 | comment | added | Carcigenicate |
@Cukic0d Oh, cool, thanks. I had no idea it provided that information. I wouldn't have guessed that it would mutate request with the time. Thanks. That definitely helps.
|
|
| Nov 17, 2020 at 16:03 | comment | added | Cukic0d |
oh wait you're doing it wrong. use answer.time - request.sent_time and it will be much more accurate
|
|
| Nov 17, 2020 at 15:41 | comment | added | Carcigenicate |
@Cukic0d Thanks. That's what I'm currently using though. I think it's just the overhead of the library, and other stuff like the fact that I'm wrapping the code in a lambda before timing. Timing the entirety of the sr1 is probably not great since sr1 seems to be doing quite a lot behind the scenes.
|
|
| Nov 17, 2020 at 15:33 | comment | added | Cukic0d | Make sure you are using 2.4.4. It fixed most of the issues with packet timestamps | |
| Nov 11, 2020 at 14:00 | vote | accept | Carcigenicate | ||
| Sep 28, 2020 at 10:58 | answer | added | user985366 | timeline score: 3 | |
| Sep 27, 2020 at 4:31 | history | edited | Carcigenicate | CC BY-SA 4.0 |
deleted 72 characters in body
|
| Sep 27, 2020 at 3:48 | history | edited | Carcigenicate | CC BY-SA 4.0 |
edited title
|
| Sep 27, 2020 at 3:00 | history | tweeted | twitter.com/StackCodeReview/status/1310051553089384452 | ||
| Sep 27, 2020 at 1:02 | history | edited | Carcigenicate | CC BY-SA 4.0 |
added 223 characters in body
|
| Sep 27, 2020 at 1:00 | comment | added | Peilonrayz♦ | Ok, that seems fine for me. Our short exchange should keep your question from being closed. | |
| Sep 27, 2020 at 0:57 | comment | added | Carcigenicate |
@Peilonrayz The code works, the times are just not very accurate. I only included them to match the incremental behavior of the actual program. They weren't the focus of this program. No, I don't want the timing inflation dealt with here. I just included the comment since anyone who uses tracert would probably notice the odd time pattern.
|
|
| Sep 27, 2020 at 0:55 | comment | added | Peilonrayz♦ | Is the Scapy issues acceptable? Are you asking for help with it? | |
| Sep 27, 2020 at 0:38 | history | asked | Carcigenicate | CC BY-SA 4.0 |