Sponsored Content
Full Discussion: Odd WLAN Device Problem
Operating Systems Linux Odd WLAN Device Problem Post 100550 by deckard on Tuesday 28th of February 2006 10:26:09 AM
Old 02-28-2006
Odd WLAN Device Problem

I'm trying to help convert my boss over to Linux. He has an HP/Compaq PC on which he installed Fedora Core 4 on. It's got a Linksys wireless card in it and we're using the NDIS wrapper to load the Windows driver for the chipset on that card. 'iwconfig' sees the card. We can configure the card. And when he has his wired NIC plugged in, I can actually ping both his wired AND his WIRELESS IP addresses. But as soon as he disconnects the cable, I lose contact with his wireless NIC.

Even stranger, I was actually able to ssh into his box via the wireless IP address, and do an ifdown eth0 and remain connected (as long as his wired NIC was plugged in). If I do an 'ifconfig' when his eth0 is down all I see is 'wlan0' and 'lo'. So it would SEEM that the WLAN card is working but is somehow realy being routed through his wired NIC. It doesn't make sense. I've tried configuring his system so that the wired NIC doesn't come up at boot, but then he gets no access (even though 'iwconfig' says it sees the access point). I've tried manually forcing the system to use wlan0 to get to it's default route but it can't. Oddly, if I change the encryption key for the wlan0 card, it losses contact with the access point and displays all zeros for the AP Mac address, but as soon as I put the right key back in... it gets the AP MAC address back!

This is one of the strangest issues I've ever run into and I can't seem to figure out what's causing it. Any ideas? (NOTE: The AP is a Cisco AP, not Linksys) The NIC itself appears to be using a Broadcom chip:

05:04.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

Last edited by deckard; 02-28-2006 at 12:07 PM..
 

10 More Discussions You Might Find Interesting

1. BSD

WLAN PCI Cards

Hi! I just wanted to know what network cards are supported in FreeBSD. I have looked at the list of supported cards but I can't find any of them in the stores. Is the list not updated, I would really preciate info about where (in EU, Sweden) I can buy them. /Peter (2 Replies)
Discussion started by: Barfly.se
2 Replies

2. Linux

odd telnet problem

Hey, I've got a RH9 box running telnet-server 0.17-25. Now i don't know what the problem is and i've been reading all night trying to find somthing like it. I am able to open a telnet session on the box using localhost and 10.10.10.6(machines address) but if i try to do it from another... (7 Replies)
Discussion started by: byblyk
7 Replies

3. Solaris

block device problem

Hi ...... I have file system problem when i try to mount get the following message : mount: /dev/rdsk/c1t4d0s7 not a block device .... I run fsck it's ok ,,,, after run newfs -N /dev/dsk/c1t4d0s7 and fsck -o b=535952 /dev/dsk/c1t4d0s7 .............it's ok ........ At the and when i try... (2 Replies)
Discussion started by: tt155
2 Replies

4. UNIX for Dummies Questions & Answers

odd ftp problem

we migrated from a system with HPUX B.11.0 to HPUX 11.23 i64 the new server is the same IP as the old server. the old server is renumbered to something else to avoid conflict. on the old system, we had a user named "ftp" . There is one person who daily will ftp files to the host using this... (15 Replies)
Discussion started by: LisaS
15 Replies

5. Linux

UNIX command for Getting IP addresss of different hosts in WLAN

Is thre any command by which i can get the IP addresses of different machines present in a Wireless Local Network Area. (2 Replies)
Discussion started by: vasurake
2 Replies

6. Cybersecurity

SSH login via wlan

Hi Is it totally safe to login via SSH through a wlan that is not encrypted? Is there anything to think about when doing it? (1 Reply)
Discussion started by: hjalle
1 Replies

7. IP Networking

How to access others machine in my WLAN

Here is the thing. I've got a TP link router (TL-WR541G) and 3 PCs accessing to Internet through it. 2 Desktop PCs (1 with Debian and 1 WinXP) 1 laptop (with Ubuntu). In my router (192.168.1.1) I can see the MAC and IP of all machines assigned (DHCP) by the router. But when I ping to them... (3 Replies)
Discussion started by: funyotros
3 Replies

8. IP Networking

Radvd wlan problems

Hi all, I am trying to get radvd to broadcast router advertisements on a wireless interface (wlan0). The wireless interface is running an ad-hoc wireless network. However, for some reason, radvd will say that wlan0 not running and refuse to start. The only way I can get radvd to broadcast... (0 Replies)
Discussion started by: abxccd
0 Replies

9. Shell Programming and Scripting

odd problem in read lines from file

Hi, I wrote a small program to read lines from a file and count the lines. The program is as below: filename=$1 count=0 cat $filename | while read -r line do printf "%5d:%s\n" $count "$line" count=$((count + 1)) done echo " $count " After I run the program, the result is... (4 Replies)
Discussion started by: jianma
4 Replies

10. Shell Programming and Scripting

WLAN receiving DHCP-IP Address doesn't work

Hey guys, I run my raspberry pi with a TP-Link Wlan-USB stick. The stick works out of the box with the pi-modded debian. But eventhough the automatic connection to one of the saved WLAN-networks in the file /etc/wpa_supplicant/wpa_supplicant.conf works, my PI doesn't request or receive an... (4 Replies)
Discussion started by: zitronenschwarz
4 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
All times are GMT -4. The time now is 06:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy