Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi Who adds MAC headers to the TCP/IP packets. IS it hardware or software? If you look into TCP/IP packets the first part of the packet is MAC headers. so who adds this MAC headers to the packets? is it the network card or Software(could be OS or anything other than hardware)?
It's the sort of functionality that is conventionally performed by the hardware offload features on the NIC, but certainly possible to pull it back into pure software if more complex functionality is required.
Most "server class" NICs have a TCP/IP Offload feature; it is very unlikely that a "desktop class" commodity NIC (or a built-in laptop NIC) will have offload.
If your NIC has offload functionality it will add and remove the MAC headers; if no offload, or it is turned off, then the MAC header is added and removed in software.
A whole layer in the OSI model. If you aren't aware of the differences, you should do some backgroud reading. Essentially though a TCP/IP packet is created with IP details etc, and payload, and then needs to be wrapped in whatever framing method is used for the link, e.g. ethernet, adsl, frame relay, isdn...
http://www.aboutdebian.com has all that info for free. It explain how packets are created, what info goes where and how routers differentiate between ip packets etc. quite a good read.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.