Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting

Re: results of iwconfig etc. Re: configuring madwifi

From: Jaime Tarrant <jaime.tarrant(at)gmail.com>
Date: Mon Feb 18 2008 - 08:44:49 EST


westniles46@comcast.net wrote:
> Hi Everyone,
>
> Attached are the results of ifconfig, iwconfig, and iwlist ath0 scan. Maybe someone can see something in there.
>
> Also, the wireless used to work under windows a little while ago, but I suppose it could have broken recently.
>
> David
>
> -------------- Original message ----------------------
> From: "roberto viana" <viana10@gmail.com>

>> i have a laptop with a wireless atheros and the madwifi driver is run
>> correctly, during the configuration process i have any problem because i
>> unknow very well the system.
>> I can try help you, if you describe more details about your problem.
>>
>> what is the result of the command # ifconfig ?
>>
>> the wireless is 'up'?
>>
>> excuse-me for my bad english, i am brazilian
>> thanks
>>
>>
>> 2008/2/17, Bob Proulx :
>>> westniles46@comcast.net wrote:
>>>> I'm struggling with wireless on my nc6000 laptop. I followed the
>>>> newbie instructions on www.madwifi.org.
>>> This is an old write-up I did for my nc4000.  Taking the vintage of
>>> the write-up for Sarge into consideration the instructions there might
>>> help you.
>>>
>>>   
http://www.proulx.com/~bob/nc4000/
>>>
>>>> Installation went well, the
>>>> blue light turns on. Then when I type "wlist ath0 scan", the return
>>>> is "ath0 no scan results" even though I a next to my wireless router
>>>> at home. I'm using WEP encrytion and typed "iwconfig ath0 key
>>>> xxxxxxxxxx" with my real key.
>>>>
>>>> I think I'm configuring the wireless incorrectly, but I cannot find
>>>> a thread.
>>> I am just going to quote directly from my old page on the subject.  I
>>> am sure things have changed since then.  You might need to make
>>> adjustments to these old Sarge instructions.
>>>
>>>   Getting the wireless running consists of the following for me. These
>>>   are all done as root. Of course if you have a closed access point you
>>>   will need to set the SSID to match instead of to "any". This is the
>>>   "coffee shop" setting.
>>>
>>>       modprobe ath_pci
>>>       iwconfig ath0 mode managed rate auto rts off frag off key off enc
>>> off
>>>       iwconfig ath0 txpower auto  # seems to power up transmitter
Do you need help?X
>>> iwconfig ath0 essid any # seems to power up transmitter >>> ifconfig ath0 up # initiates active scan for access point >>> sleep 2 # give time to settle >>> iwlist ath0 scanning >>> shorewall start >>> dhclient ath0 >>> >>> Initially iwconfig shows the txpower off. But after this txpower is on >>> (0 db). Unloading the module seems to power off the transmitter. I am >>> still experimenting with this. >>> >>> ifconfig ath0 down >>> rmmod ath_pci >>> rmmod ath_hal >>> rmmod wlan >>> >>>> Can anyone help? New to debian, new to madwifi. Please excuse me if >>>> I should post to madwifi.org instead. >>> I think this is quite a good topic for debian-laptop. >>> >>> Bob >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.6 (GNU/Linux) >>> >>> iD8DBQFHuLGW0pRcO8E2ULYRAim8AJ9NX6IVt9TSdNdBrOCj1lD2hyxR5wCfVALn >>> BQ612f8/gfnr75TiHYWD2pc= >>> =dvuK >>> -----END PGP SIGNATURE----- >>> >>>

>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Re: configuring madwifi
> From:
> "roberto viana" <viana10@gmail.com>
> Date:
> Sun, 17 Feb 2008 22:47:59 +0000
> To:
> debian-laptop@lists.debian.org
>
> To:
> debian-laptop@lists.debian.org
>
>
> i have a laptop with a wireless atheros and the madwifi driver is run
> correctly, during the configuration process i have any problem because i
> unknow very well the system.
> I can try help you, if you describe more details about your problem.
>
> what is the result of the command # ifconfig ?
>
> the wireless is 'up'?
>
> excuse-me for my bad english, i am brazilian
> thanks
>
>
> 2008/2/17, Bob Proulx <bob@proulx.com <mailto:bob@proulx.com>>:
>
> westniles46@comcast.net <mailto:westniles46@comcast.net> wrote:
> > I'm struggling with wireless on my nc6000 laptop. I followed the
> > newbie instructions on www.madwifi.org <http://www.madwifi.org>.
>
> This is an old write-up I did for my nc4000. Taking the vintage of
> the write-up for Sarge into consideration the instructions there might
> help you.
>
> http://www.proulx.com/~bob/nc4000/
>
> > Installation went well, the
> > blue light turns on. Then when I type "wlist ath0 scan", the return
> > is "ath0 no scan results" even though I a next to my wireless router
> > at home. I'm using WEP encrytion and typed "iwconfig ath0 key
> > xxxxxxxxxx" with my real key.
> >
> > I think I'm configuring the wireless incorrectly, but I cannot find
> > a thread.
>
> I am just going to quote directly from my old page on the subject. I
> am sure things have changed since then. You might need to make
> adjustments to these old Sarge instructions.
>
> Getting the wireless running consists of the following for me. These
> are all done as root. Of course if you have a closed access point you
> will need to set the SSID to match instead of to "any". This is the
> "coffee shop" setting.
>
> modprobe ath_pci
> iwconfig ath0 mode managed rate auto rts off frag off key off
> enc off
> iwconfig ath0 txpower auto # seems to power up transmitter
> iwconfig ath0 essid any # seems to power up transmitter
> ifconfig ath0 up # initiates active scan for access
> point
> sleep 2 # give time to settle
> iwlist ath0 scanning
> shorewall start
> dhclient ath0
>
> Initially iwconfig shows the txpower off. But after this txpower is on
> (0 db). Unloading the module seems to power off the transmitter. I am
> still experimenting with this.
>
> ifconfig ath0 down
> rmmod ath_pci
> rmmod ath_hal
> rmmod wlan
>
> > Can anyone help? New to debian, new to madwifi. Please excuse me if
> > I should post to madwifi.org <http://madwifi.org> instead.
>
> I think this is quite a good topic for debian-laptop.
>
> Bob
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHuLGW0pRcO8E2ULYRAim8AJ9NX6IVt9TSdNdBrOCj1lD2hyxR5wCfVALn
> BQ612f8/gfnr75TiHYWD2pc=
> =dvuK
> -----END PGP SIGNATURE-----
>
>

It may be worth checking if there is a firewall configuration on the local interfering - as it sounds like the module is loading properly.

If a firewall such as firestarter has been previously installed for the wired interface (eth1), then ath0 may not be permitted to talk at all. Atleast in the case of firestarter - you have to manually tell it when you change interfaces in its preferences, i.e. the wireless interface ath0 needs to be configured as the internet facing interface instead of eth1.

To assist debugging, I would recommend getting three consoles open. The first two being to display diagnostics info.

Console 1: type: tail -f /var/log/messages -- you will see link activity prefixed with ADDRCONF - (not ready, ready, etc), keep an eye out for anything that looks like packets being blocked, or anything else that may be related.

Console 2: type: iwevent
-- This will tell you what wireless events take place. setting the ESSID, etc.

Console 3: this will generate messages in the other two consoles. type: ifdown eth1
ifdown ath0
ifup ath0

  • This should theoretically bring up the ath0 interface on its own, without any chance of the wired interface interfering with routes, etc. Do this with no network cable plugged in.

You'll see the system activity in the other two consoles - there might be some clue as to what the issue is there?

-- 
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Received on Mon Feb 18 08:46:19 2008
Do you need more help?X

This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 06:50:37 EDT


Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library