08-24-2009
The driver itself allows for far greater capabilities than NDIS wrapping or even native drivers. Allows you to run in higher modes: Master mode (act as a wireless access point), or Monitor mode (allows for wireless packet sniffing).
Really depends if you need this type of capability as to whether you would install it.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi new user to UNIX and I am in the process of networking my UNIX box to my windows2000....Is there a special program I have to install so that my windows would recognize and see the Unix box....any suggestions would be great
Thanks (1 Reply)
Discussion started by: jonas27
1 Replies
2. IP Networking
HI guys/gals
basic question
lets say i am running a network. lets say i am using Win Me.
how would i network Win Me to a computer that has linux and another that has 98 well the 98 is no problem but the linux well i have an idea but i am rusty with linux. No i have rusted out. Would you make... (1 Reply)
Discussion started by: pydyer
1 Replies
3. IP Networking
Does anyone know where can i find advanced and basic information about setting up a WLAN using bluetooth. The operating systems are mandrake 9.0 and windows 2000?
Thank you in advance!:) (3 Replies)
Discussion started by: SolidSnake
3 Replies
4. HP-UX
Can someone please point me in the correct direction for setting up a wireless card using HP-UX 11iV1? I know its different depending on the type of card I have, but im looking for a direction.
Thanks! (0 Replies)
Discussion started by: nickwinnie
0 Replies
5. Solaris
I can't or i don't know how to put up a network and internet on sun solaris 10. I looked and found some stuff on forums around net but I'm missing a few files. Like, "defaultrouter", "resolve.conf", ping is not working ( host unreachable), my card is "lo0" when I use ifconfig -a comand. Should I... (8 Replies)
Discussion started by: salvor_hardin
8 Replies
6. UNIX for Advanced & Expert Users
hi everyone
this is dipendra, i am interested in networking,i know simple socket programming . and now i am wonder to get in to audio socket. i have no clue how to build audio socket.so i am looking if u can provide me a link regarding the audio socket building tutorials. (1 Reply)
Discussion started by: dipendra_regmi
1 Replies
7. IP Networking
Can anybody help me regarding networking using c language
i know how to capture the packets and to verify it`s protocol destination and source ip etc.
Can anybody help me to direct a packet coming to an ip to some other ip of my choice ........
Hope reply ... (0 Replies)
Discussion started by: Sannair
0 Replies
8. Solaris
What am I doing wrong, I configure interfaces ce1,ce,2 and ce3 but when I reboot the server they lose the configuration and I have to reset them?
ifconfig ce1 plumb
ifconfig ce2 plumb
ifconfig ce1 155.216.13.72 netmask 255.255.255.240
ifconfig ce2 155.216.13.73 netmask 255.255.255.240... (5 Replies)
Discussion started by: Kjons76
5 Replies
9. IP Networking
hi
From mt windows machine I can ping a LINUX machine but there is no arp entry for the same LINUX on my windows.
How is it possible and what can I do to add the arp entry as I need it.
thanks (1 Reply)
Discussion started by: leghorn
1 Replies
NDIS(4) BSD Kernel Interfaces Manual NDIS(4)
NAME
ndis -- NDIS miniport driver wrapper
SYNOPSIS
options NDISAPI
device ndis
device wlan
DESCRIPTION
The ndis driver is a wrapper designed to allow binary Windows(R) NDIS miniport network drivers to be used with FreeBSD. The ndis driver is
provided in source code form and must be combined with the Windows(R) driver supplied with your network adapter. The ndis driver uses the
ndisapi kernel subsystem to relocate and link the Windows(R) binary so that it can be used in conjunction with native code. The ndisapi sub-
system provides an interface between the NDIS API and the FreeBSD networking infrastructure. The Windows(R) driver is essentially fooled
into thinking it is running on Windows(R). Note that this means the ndis driver is only useful on x86 machines.
To build a functional driver, the user must have a copy of the driver distribution media for his or her card. From this distribution, the
user must extract two files: the .SYS file containing the driver binary code, and its companion .INF file, which contains the definitions for
driver-specific registry keys and other installation data such as device identifiers. These two files can be converted into a kernel module
file using the ndisgen(8) utility. This file contains a binary image of the driver plus registry key data. When the ndis driver loads, it
will create sysctl(3) nodes for each registry key extracted from the .INF file.
The ndis driver is designed to support mainly Ethernet and wireless network devices with PCI, PCMCIA and USB bus attachments. (Cardbus
devices are also supported as a subset of PCI.) It can support many different media types and speeds. One limitation however, is that there
is no consistent way to learn if an Ethernet device is operating in full or half duplex mode. The NDIS API allows for a generic means for
determining link state and speed, but not the duplex setting. There may be driver-specific registry keys to control the media setting which
can be configured via the sysctl(8) command.
DIAGNOSTICS
ndis%d: watchdog timeout A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge
the transmission before a timeout expired.
SEE ALSO
altq(4), arp(4), netintro(4), ng_ether(4), ifconfig(8), ndis_events(8), ndiscvt(8), ndisgen(8), wpa_supplicant(8)
NDIS 5.1 specification, http://www.microsoft.com.
HISTORY
The ndis device driver first appeared in FreeBSD 5.3.
AUTHORS
The ndis driver was written by Bill Paul <wpaul@windriver.com>.
BSD March 14, 2010 BSD