User talk:Zac67/Archives/2023/August
Fragment Free SwitchingHi,Zac67, sorry for writing here, I read an answer of yours on "Stack Exchange", but for some reason I don't know I cannot create a count and login "Stack Exchange", but I'm really want to get some help from you about the fragment free switching mechanism(please excuse me for my silly question, I'm a new guy for ethernet, and learning and testing about the switching mechanism).On "Stack Exchange"([1]https://networkengineering.stackexchange.com/questions/60049/what-exactly-is-fragment-free-switching), you mentioned". There is no 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. – Zac67♦ Jun 26, 2019 at 17:13 ", So my question is if a fragment free switch reviewed a frame more than 64 bytes(e.g. 128bytes), but with a CRC error, then what will be the behavior of the switch? To my understanding, the switch will forward the frame, until it monitored that there is a "CRC Error", that means the switch will "cut off" a part of the frame, and forward a part of the frame, am I right? And for the forwarded frame, is there a "CRC" 4 bytes in it? As a results of my test, there is a CRC on in the forwarded frame, and it is a Error CRC, that makes me confuse. I hope I didn't disturb you and hope to receive your reply. Best Regards 111.118.203.20 (talk) 01:55, 29 August 2023 (UTC)
|