06-27-2005
Quote:
Originally Posted by woofie
been awhile since I've done this so could be wrong. But a probe_all (?) from the OBP would also should what is connected.
I think show_nets is what you are thinking of.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Our shops server runs SCO Openserver 5 release 5. It has two network cards in it (one on 10.0.0.6 and one on 90.0.0.99). When I run scoadmin and look at the network settings it show both my 3com network cards and a loop back driver http://theentertainer.com/james/untitled.jpg
Can anyone tell... (1 Reply)
Discussion started by: potter
1 Replies
2. Solaris
Hi,
I'm looking for a command to be able to disable a network card under the boot PROM.
I need it to force my Jumpstart to use the Ethernet card of my server (V880) instead of my fiber card (gem0).
Thanks,
Fabien (6 Replies)
Discussion started by: unclefab
6 Replies
3. AIX
The title speaks for itself. I have never attempted this but understand there is a way to use two network cards (en0 and en1) with the same IP address so as to load balance the traffic flow through both cards. Anyone know the answer? (4 Replies)
Discussion started by: johnf
4 Replies
4. Solaris
Hi all,
I have a server running with Solaris and I have 2 Pci cards installed on this server (since a while), 1 with 4 coppers connections output and one with a Fiber network connection output.
Today, this server is using the on board network connection (Ce0).
How can I find the other... (7 Replies)
Discussion started by: unclefab
7 Replies
5. Solaris
Hi All,
Hope you are all doing good.
In MY unix box i have 2 network cards. I want to know what if one network card fails. Does the second one will automatically take all the traffic or how it is supposed to work. Also in my logs i am seeing below errors . Can you throw some light of this qfe... (3 Replies)
Discussion started by: Krrishv
3 Replies
6. Solaris
Hi all
I hate networking, I hate everything to do with it. Its something I do in anger in one contract, then forget. This is more of a question / than a problem.
So, on a solaris 10 server, using older qfe cards, Ive got a sun truck with 4 nics (qfe0,3,4,7), and a ipmp pair (hemo0,qfe1).... (2 Replies)
Discussion started by: sbk1972
2 Replies
7. Programming
Hello
I have a problem with retreiving network interface list using IOCTLs. I have 4 interfaces:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope... (1 Reply)
Discussion started by: xyzt
1 Replies
8. Hardware
Hello everybody,
I'm having troubles with Slackware 13.1 and network cards.
I have one on-board Ethernet card (which is recognized and works okay) and a PCI Ethernet card (which is also recognized, but doesn't appear in 'ifconfig -a'). If i run a 'lspci', i can see the kernel recognized the... (5 Replies)
Discussion started by: semash!
5 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
I have just setup a webserver running on a linux box. This server has 2 ethernet cards and only 1 is in used now. eg. 192.168.10.1 is my server IP. All users from 192.168.10.X can access my webserver. However, users from another LAN 10.10.10.X are not able to access my webserver. They... (0 Replies)
Discussion started by: jackma
0 Replies
10. Solaris
Hello All
I am trying to get a list of process or applications runninging on the network only. I should emphasize that im not interested in the application or process if its not using the network.
I tried the good old netstat comand, but im not able to figure out how to list the running... (8 Replies)
Discussion started by: busi386
8 Replies
AN(4) BSD Kernel Interfaces Manual AN(4)
NAME
an -- Aironet Communications 4500/4800 wireless network adapter driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device an
device wlan
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_an_load="YES"
DESCRIPTION
The an driver provides support for Aironet Communications 4500 and 4800 wireless network adapters and variants, including the following:
o Aironet Communications 4500 and 4800 series
o Cisco Aironet 340 and 350 series
o Xircom Wireless Ethernet Adapter
Support for these devices include the ISA, PCI and PCMCIA varieties. The Aironet 4500 series adapters operate at 1 and 2Mbps while the
Aironet 4800 series and Cisco adapters can operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core
PCMCIA modules and all have the same programming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the
host as normal ISA and PCI devices and do not require any PCCARD support.
The PCMCIA Aironet cards require PC Card support, including the kernel pccard(4) driver. ISA cards can either be configured to use ISA Plug
and Play or to use a particular I/O address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for
Plug and Play.) The an driver has Plug and Play support and will work in either configuration, however when using a hard-wired I/O address
and IRQ, the driver configuration and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be
automatically probed and attached.
All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power manage-
ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it
can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or "auto" (the NIC automati-
cally chooses the best speed).
By default, the an driver configures the Aironet card for infrastructure operation.
For more information on configuring this device, see ifconfig(8).
DIAGNOSTICS
an%d: init failed The Aironet card failed to become ready after an initialization command was issued.
an%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM.
an%d: device timeout The Aironet card failed to generate an interrupt to acknowledge a transmit command.
SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), wlan(4), ancontrol(8), ifconfig(8)
HISTORY
The an device driver first appeared in FreeBSD 4.0.
AUTHORS
The an driver was written by Bill Paul <wpaul@ee.columbia.edu>.
BSD
July 16, 2005 BSD