| 2021-06-25 08:38:46 +0000 | received badge | ● Famous Question (source) |
| 2021-06-25 08:38:46 +0000 | received badge | ● Notable Question (source) |
| 2019-11-01 18:12:54 +0000 | received badge | ● Popular Question (source) |
| 2019-07-24 23:12:52 +0000 | commented question | Ethernet hardware loopback This also works. It's a little more convenient to be able to do it all in Wireshark and to capture all of it in one pla |
| 2019-07-22 18:31:06 +0000 | marked best answer | Ethernet hardware loopback I am working on a hardware implementation using a PHY chip that allows far-end loopback, that is, data from the host that is sent to this chip is echoed back exactly as received. I wanted to create some software that would use this loopback to test the hardware out, but the echoed data has the source and destination addresses set to the same values as when they went out from the computer. Is it possible to automatically differentiate the transmitted frames from the received frames, since they have the same source and destination addresses? Wireshark sees both the transmitted and the received packets, and I don't see any indication as to which is which in the display. Obviously (?), the earlier one should be the transmitted frame, but I don't know of any way to tell programatically. Is there a way to tell the transmitted from the received and filter out the transmitted frame? |
| 2019-07-22 18:31:06 +0000 | received badge | ● Scholar (source) |
| 2019-07-22 18:30:59 +0000 | commented question | Ethernet hardware loopback Hi all. These are raw Ethernet frames that are 1344 bytes in length. It appears that the checksum is added/checked in |
| 2019-07-19 21:53:00 +0000 | asked a question | Ethernet hardware loopback Ethernet hardware loopback I am working on a hardware implementation using a PHY chip that allows far-end loopback, that |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.