Timeline for What exactly is fragment free switching?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2023 at 7:01 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 763 characters in body
|
| Oct 3, 2023 at 6:48 | comment | added | Zac67♦ | @user253751 You can't check the FCS while the frame is still being received which is implied by the question. | |
| Aug 30, 2023 at 17:01 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 299 characters in body
|
| Aug 30, 2023 at 16:58 | comment | added | Zac67♦ | @user253751 There's no way to detect a damaged frame within the first 64 bytes. That limit is designed to filter out runts. | |
| Aug 29, 2023 at 7:27 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 7 characters in body
|
| Aug 29, 2023 at 5:52 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 1 character in body
|
| Dec 20, 2019 at 13:52 | vote | accept | Weezy | ||
| Jun 26, 2019 at 17:13 | comment | added | Zac67♦ | There is no extra integrity check for the first 64 bytes in Ethernet. On L2, there's only FCS for the whole frame, nothing else. Depending on the actual L1 PHY, there may be additional PCS level checks or FEC, but these are on line symbols or code groups. For IPv4 (L3) there's an IP header checksum that falls into the first 64 bytes, but IPv6 and other L3 protocols don't have that. Some transport-layer protocols (L4) also use header checksums but those differ as well. | |
| Jun 26, 2019 at 16:48 | comment | added | Weezy | While I agree with what you've written, you don't seem to mention what exactly is the integrity check performed on the 64 bytes. Are the switches checking if the bits are present or not or are they performing some kind of calculation? I know that fragment free won't do a CRC on it. | |
| Jun 25, 2019 at 19:16 | history | answered | Zac67♦ | CC BY-SA 4.0 |