What is the interface control?
The interface controller is a small computer program or a set of programs that acts as a connection between computer software and hardware of the network interface card (nothing). The creators and programmers use nothing specific interface of application programming (API) known as the NDIS (NDIS) interface specifications. It lays down all the rules necessary for a computer program, such as the operating system, for interaction with nothing. In fact, there are several types of controls of the interface described under the NDIS, but basically the primary role of NDIS is to obtain several layers of connection of open systems (OSI) for mutual cooperation. The first layer is a physical layer that deals with physical specifications for nothing, such as the universal serial bus (USB), Ethernet card, wireless adapter card, etc. The second and third layers of the OSI model are the vanish Magie NDIS will happen. The second layer is a layer of data connection and consists of two sub -layers, upper referred to as logical connection control (LLC) and DOlní named Media Access control (MAC). The driver processes the MAC to the MAC, while the LLC sub -layer processes the interface control and provides an interface between it and the third OSI layer, a network layer.
, which works as an intermediary, NDIS basically packs all the confusing complexity of hardware and provides a set of functions for its interaction with network protocols necessary for communication. The programmer must simply follow the rules set out in the NDIS to create the actual interface controls. At a lower hardware level, these drivers are known as miniPort drivers, while the upper level drivers are written using the NDIS APIs to process the basic network protocols such as Internet Protocol (IP), Security Internet Protocol (IPSEC), Internet Control Message Protocol (ICMP) and InternetWork Packet Exchange (IPX).
When network communication occurs by meansNothing, data bits are first accepted by a physical device and then moved from hardware to different layers of OSI through OSI architecture architecture until it is easier to understand by the user. So each layer of the model provides services to its neighbors. The data leaves the first layer, the physical layer and affect the MAC of the lower partial layer in the second layer, where the device controls it along the LLC. LLC controls then move them to the network layer.
Another type of interface driver is a temporary controller that acts as a housing, containing the Miniport interface and for network protocol drivers. These medium drivers can then be attached together and provide the drivers of the interface to control the operation of the accepted nothing. Intermediate controls are useful for various needs such as data filtering, load leveling, network traffic monitoring and collecting statistical information. They also work as a translator among STarish transport drivers and miniPort control, which speaks with a media format that the older driver does not understand.
NDIS was originally designed by Microsoft® and works in conjunction with 3COM®, so many hardware manufacturers write their drivers to support first Microsoft® operating systems. As a result, NDIS is limited to computer hardware architecture based on Intel® 80386, either 32 -bit or 64 -bit processors. Free software Movement has also developed a program called NDISWRAPPER, which is capable of loading the interface drivers originally developed for Microsoft® Windows® for use with free operating systems such as Linux®. Distributions (BSD) usersley software, such as FreeBSD® and NetBSD®, also found the ability to use Windows® drivers using software developed by a project known as Project Evil. The X86 NDIS hardware restrictions led to another project developed by Apple and Novell®, called Open Data-Link Interface (from(I), which provided many of the same rules and functionality as NDIS, but focusing on Apple® Macintosh &; and Novell Netware® systems.