07-15-2008
does iwconfig return any "wireless extensions" for eth1. If so your just usue usual iwconfig eth1 essid XXXX followed by dhclient eth1.
The fact that the driver doesn't call it wlan0 is meaningless.
10 More Discussions You Might Find Interesting
1. 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
2. Linux
Hello everybody:
Can you help me, I have installed the Kubunto on my laptop, my wireless connection it is with an Linksys WPC54G adapter.
I tried with several tools to use it but just do not work.
Please help me!!! (2 Replies)
Discussion started by: GEIER
2 Replies
3. Red Hat
Anybody, let me know major differences between RHEL 3 & 4 . (2 Replies)
Discussion started by: sakthi_13
2 Replies
4. Linux
Hi,
I've installed wireless card and I didn't receive any error in the installation process.
Now I want to use it but I can't make internet to work.
if I check my card with iwconfig I get the following message
wlan0 IEEE 802.11g ESSID:"Alice-34376718"
Mode:Managed ... (2 Replies)
Discussion started by: aneuryzma
2 Replies
5. Red Hat
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies
6. Red Hat
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies
7. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
8. Red Hat
Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
Discussion started by: jstone4646
3 Replies
9. UNIX for Dummies Questions & Answers
I know this question might have been asked a lot but couldn't find anything that worked. From a windows machine 'A' I can only SSH into Linux server 'B' from where I can SSH into another Linux server 'C'. I need to be able to run GUI interfaces on server C which run on my Windows machine. I... (3 Replies)
Discussion started by: hr.prasan
3 Replies
10. Red Hat
Hi
We have RHEL 6.7 on an HP physical server and want to install RHEL 7 (not upgrade) on top of it by means of virtualization. Is it possible to install/configure RHEV/KVM virtualization on base RHEL 6.7 OS instance and then install RHEL 7 as a VM guest on it? If yes, could you please guide me... (1 Reply)
Discussion started by: magnus29
1 Replies
LEARN ABOUT REDHAT
iwevent
IWEVENT(8) Linux Programmer's Manual IWEVENT(8)
NAME
iwevent - Display Wireless Events generated by drivers and setting changes
SYNOPSIS
iwevent
DESCRIPTION
iwevent display Wireless Events received through the RTNetlink socket. Each line display the specific Wireless Event which describe what
has happened on the specified wireless interface.
This command doesn't take any arguments.
DISPLAY
There is two classes of Wireless Events.
The first class is events related to a change of wireless settings on the interface (typically done through iwconfig or a script calling
iwconfig). Only settings that could result in a disruption of connectivity are reported. The events currently reported are changing one of
the following setting :
Network ID
ESSID
Frequency
Mode
Encryption
All those events will be generated on all wireless interfaces by the kernel wireless subsystem (but only if the driver has been converted
to the new driver API).
The second class of events are events generated by the hardware, when something happens or a task has been finished. Those events include :
New Access Point/Cell address
The interface has joined a new Access Point or Ad-Hoc Cell, or lost its association with it. This is the same MAC address that is
reported by iwconfig.
Scan request completed
A scanning request has been completed, results of the scan are available (see iwlist).
Tx packet dropped
A packet directed at this address has been dropped because the interface believes this node doesn't answer anymore. An early indica-
tion that the node may have left the cell or gone out of range.
Custom driver event
Event specific to the driver. Please check the driver documentation.
Registered node
The interface has successfully registered a new wireless client/peer. Will be generated mostly when the interface act as an Access
Point (mode master).
Expired node
The registration of the client/peer on this interface has expired. Will be generated mostly when the interface act as an Access
Point (mode master).
Only some of those events will be generated on some wireless interfaces by the wireless driver, and their support depend on the specific
hardware/driver combination. Please refer to driver documentation for details.
AUTHOR
Jean Tourrilhes - jt@hpl.hp.com
SEE ALSO
iwconfig(8), ifconfig(8), iwspy(8), iwpriv(8).
net-tools 25 January 2002 IWEVENT(8)