Why this video has so less views? This is a wonderful video. It dealt with all the concepts of frame very brilliantly. Not everyone explains all these things. Thank you!
Amazing explanation also justifies why frame fields are important, Can you also create a video on different types of Frames like MACsec frames, Jumbo Frames, VLAN frames..
היי, שאלה יפה :) שני בתים זה אולי יותר מידי, אבל אין דבר בעייתי יותר מלהתקע עם מעט מידי (ראה כמה קשה לעשות שינוי בפרוטוקול כזה בהמשך). אם היינו משתמשים בבית אחד, היו רק 256 אופציות, וזה בהחלט משהו שעלול לא להספיק. ולעבוד עם מספר ביטים שלא מתחלק ב-8 זה הרבה פחות נוח בצד המימושי.
Hi Panagiotis and thank you for your question! Yes, it is indeed in use, but mostly by switches. So if you capture frames on an enterprise network where you are connected to a (say, rather massive) Switch, for example one by Cisco, you will be able to capture these frames. I hope it answers your question 💪🏻
@Ashutosh, it's currently in the process of production. I will prioritize it following your request and upload once it's finished Thanks for your feedback
wouldn't the value now be 44-bytes instead of the original 45 since the 0 is apart of the payload? or does 0 not translate to a byte in this situation?
Hi Joshua and thanks for your question! In case a byte is used as padding (and not data), it is not considered as "part of the payload" and the length field doesn't include it. I hope this answers your question, if not - please clarify and I would love to make this clear.
Thank you for your question, Actuallt, there is no error... Please allow me to clarify: The minimum *total* size of an Ethernet Frame consists of 64 bytes: * 46 bytes of data (and padding) * 6 bytes of dest address * 6 bytes of source address * 2 bytes of type/length * 4 bytes of Checksum (CRC32) That is, all in all, 64 bytes. I hope this is clear :)
Thanks for your question Fahad, these values are undefined - they are reserved for scenarios that have not been defined yet and may be used in the future
Thank you for your question Fahad. Jumbo frames are actually anything larget than 1500 bytes (that "original" Ethernet frames can carry). They are out of scope of the current series, but you can find out more about them here - en.wikipedia.org/wiki/Jumbo_frame. I may create a separate video about them in the future.
Hi N Ph; The preamble enables network devices easily synchronize their receiver clocks. Remember that when transmitting a bit, we do so over a very short period of time. We are sending, for example, 1010 - these are 4 bits. To be able to disect each one, the receiver needs to know when the transmission of the "1" bit starts and ends... For example, imagine I am sending a stream of "11111". In order to be able to tell how many "1"s I sent, the receiver needs to know how much time is used to send each bit, and where to "start" the "listening". You can find a nice illustration for this on page 7 of this document: www4.comp.polyu.edu.hk/~comp2322/Bit%20and%20Frame%20Synchronization%20Techiques.pdf I hope this helps!
Why this video has so less views? This is a wonderful video. It dealt with all the concepts of frame very brilliantly. Not everyone explains all these things.
Thank you!
Thank you very much Ashutosh!
Very underrated video. Clear and to the point. Thank you!!
Glad you enjoyed it! Please help me share the word 🙏🏻
One of the Best Video I have ever seen on youtube for ETHERNET
Thank you so much Rajat!
Best explanation of ethernet frame .
Thank you! 🙏🏻
Finally understand the purpose of LLC. Thanks mate!!
Thank you for your kind response @Panagiotis!
@@BriefVid :-)
Amazing. You have done the best ever. Thanks in advance for your effort.
Thanks a lot for your kind words!
Please let me know if there are other topics you'd like me to cover
I have a quiz tomorrow
That helped a lot
Thanks❤
I am glad I could help. Thank you for commenting 🙏🏻
Excellent video
Thank you very much Vinoth!
Thanks so much!!!!! 💜💜💜💜💜great vidioe
Thank you very much!
Please help me spread the word 🙏🏻
Lovely video, thank you
Glad you enjoyed it! Thank you @Eric!
Amazing explanation also justifies why frame fields are important, Can you also create a video on different types of Frames like MACsec frames, Jumbo Frames, VLAN frames..
Thank you Ravi! I will add these to my todo :)
Thanks great job!!!
Thank you Nasrullah!
שמח שחזרת להעלות סרטונים. חיכיתי לזה
תודה!
היי עומר, לגבי השדה TYPE ב Ethernet2 או LLC-TYPE ב IEEE, למה צריך 2 בתים שלמים בשביל בחירת אופציה? (IP handler או arp handler)
היי, שאלה יפה :)
שני בתים זה אולי יותר מידי, אבל אין דבר בעייתי יותר מלהתקע עם מעט מידי (ראה כמה קשה לעשות שינוי בפרוטוקול כזה בהמשך). אם היינו משתמשים בבית אחד, היו רק 256 אופציות, וזה בהחלט משהו שעלול לא להספיק. ולעבוד עם מספר ביטים שלא מתחלק ב-8 זה הרבה פחות נוח בצד המימושי.
Very useful
Glad you think so! Thanks for writing :)
Thanks
Thank you for writing! :)
Is LLC (802.3) still in use? I have captured millions of packets in wireshark, but all of them seems to use Ethernet II.
Hi Panagiotis and thank you for your question!
Yes, it is indeed in use, but mostly by switches. So if you capture frames on an enterprise network where you are connected to a (say, rather massive) Switch, for example one by Cisco, you will be able to capture these frames.
I hope it answers your question 💪🏻
@@BriefVid Thanks a lot for your response. I use it for capture frames on my pc, so thats can explain their absence.
Could you please share the link of BONUS VIDEO here or in your description because it's very hard to find it in your channel with the title?
@Ashutosh, it's currently in the process of production. I will prioritize it following your request and upload once it's finished
Thanks for your feedback
Thanks for considering, man! Will be waiting.
@@ashutosh57 I published it today:
ruclips.net/video/ECl8DnWeVD4/видео.html
I hope you will like it :)
@@BriefVid Thanks a lot! Will watch it tonight.
@@ashutosh57 Great, looking forward to hearing your thoughts :)
wouldn't the value now be 44-bytes instead of the original 45 since the 0 is apart of the payload? or does 0 not translate to a byte in this situation?
Hi Joshua and thanks for your question!
In case a byte is used as padding (and not data), it is not considered as "part of the payload" and the length field doesn't include it. I hope this answers your question, if not - please clarify and I would love to make this clear.
i believe there is an error? the least amount of data is 64 bytes not 46?
Thank you for your question,
Actuallt, there is no error... Please allow me to clarify:
The minimum *total* size of an Ethernet Frame consists of 64 bytes:
* 46 bytes of data (and padding)
* 6 bytes of dest address
* 6 bytes of source address
* 2 bytes of type/length
* 4 bytes of Checksum (CRC32)
That is, all in all, 64 bytes. I hope this is clear :)
what about frame is greater than 1500 but less than 1536 ?
Thanks for your question Fahad, these values are undefined - they are reserved for scenarios that have not been defined yet and may be used in the future
what if Jumbo frame (9000 byte data) ?
Thank you for your question Fahad.
Jumbo frames are actually anything larget than 1500 bytes (that "original" Ethernet frames can carry). They are out of scope of the current series, but you can find out more about them here - en.wikipedia.org/wiki/Jumbo_frame. I may create a separate video about them in the future.
I am still confused about synchronization feature of preamble. Can anyone explain to me??
Hi N Ph;
The preamble enables network devices easily synchronize their receiver clocks. Remember that when transmitting a bit, we do so over a very short period of time. We are sending, for example, 1010 - these are 4 bits. To be able to disect each one, the receiver needs to know when the transmission of the "1" bit starts and ends... For example, imagine I am sending a stream of "11111". In order to be able to tell how many "1"s I sent, the receiver needs to know how much time is used to send each bit, and where to "start" the "listening".
You can find a nice illustration for this on page 7 of this document:
www4.comp.polyu.edu.hk/~comp2322/Bit%20and%20Frame%20Synchronization%20Techiques.pdf
I hope this helps!
@@BriefVid thank you very much. I've understood more clearly. 👍👏👏
@@NguyenPhuong-te6qy great! Thanks for replying and letting me know :)
It’s like a heads up to the computer that the frames are coming