[ltp] Cisco Aironet 350 Mini PCI on an R40 running SuSE 9
Mike Evans
linux-thinkpad@linux-thinkpad.org
Thu, 18 Dec 2003 08:47:39 -0700
This is a multi-part message in MIME format.
--------------000805090704070807000708
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Well, I figured out one problem I had... I compiled the driver on a
fresh SuSE install--later I ran Yast's update utility which installed a
new kernel. That's why the driver seemed to disappear on me.
I had some success yesterday. I found an AP at work, and was successful
in grabbing an IP via DHCP-- I still couldn't connect, as I didn't have
the WEP key (is that odd that I could get an IP?). But, it felt good.
Once home, I was excited to get everything working finally... I
re-compiled the driver, modprobed it, then:
iwconfig eth1 essid 'abode'
iwconfig eth1 key s:mypass
iwconfig commit
ifconfig eth1 up
ifup eth1
...nothing... it didn't grab an IP from my AP, but it does see it
(displays the AP's MAC) and has decent signal strength. The man page
for iwconfig doesn't say anything about 'iwconfig eth1 channel 11' so I
didn't make that change, but perhaps that's my problem? My AP is on
channel 11--guessing the default would be 1?
Does anyone have experience with kwifimanager? I'm thinking it might
make things easier for me...
Fabrice Bellet wrote:
>On Wed, Dec 17, 2003 at 08:23:53AM -0700, Mike Evans wrote:
>
>
>>I used 'iwconfig' to manually set all of my wlan settings. iwconfig
>>showed that the card had found my router and was reporting that I had
>>around 55/100 signal strength.
>>
>>
>
>Is your card associated to your access point ?
>/proc/driver/aironet/eth1/Status should report something like that in the
>first lines :
>
>Status: CFG ACT SYN LNK PRIV KEY WEP
>Mode: 3bf
>
>
>
>>But, still no internet connection.
>>
>>
>
>Is the network interface configured ?
>Does ifconfig report RX/TX packets ? Do these values increase ?
>
>
>
>>My next step was to use ifconfig (and later I manually created an
>>itcfg-eth1 in /etc/sysconfig/network) to try to get things working. It
>>worked pretty well, but every time I run iwconfig, it shows the (wrong)
>>settings I made in 'acu'.
>>
>>
>
>ACU and iwconfig both work on the same level : the wireless parameters
>configuration. That's the prerequise. So it is normal that ACU did overwrite
>the previous parameters defined with iwconfig.
>
>ifconfig (for a static IP configuration, or a DHCP client for a dynamic IP
>configuration) works at the network interface level. Once the wireless
>parameters are configured, the network interface needs to be configured too
>(its IP address, netmask, default route, and so on).
>
>
>
>>Any ideas on how to fix this without (yet) another fresh install?
>>
>>Anyone care to walk me through setting up a wireless connection
>>step-by-step?
>>
>>
>
>A very simple commandline-based wireless setup is the following
>(according everything is static) :
>
># wireless setup
>iwconfig eth1 essid your_essid
>iwconfig eth1 channel your_channel
>iwconfig eth1 key xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx
>
># network interface setup
>ifconfig eth1 x.x.x.x netmask y.y.y.y up
>route add default gw z.z.z.z
>
>Cheers,
>
>
--------------000805090704070807000708
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body>
Well, I figured out one problem I had... I compiled the driver on a
fresh SuSE install--later I ran Yast's update utility which installed a
new kernel. That's why the driver seemed to disappear on me.<br>
<br>
I had some success yesterday. I found an AP at work, and was
successful in grabbing an IP via DHCP-- I still couldn't connect, as I
didn't have the WEP key (is that odd that I could get an IP?). But, it
felt good.<br>
<br>
Once home, I was excited to get everything working finally... I
re-compiled the driver, modprobed it, then:<br>
iwconfig eth1 essid 'abode'<br>
iwconfig eth1 key s:mypass<br>
iwconfig commit<br>
ifconfig eth1 up<br>
ifup eth1<br>
<br>
...nothing... it didn't grab an IP from my AP, but it does see it
(displays the AP's MAC) and has decent signal strength. The man page
for iwconfig doesn't say anything about 'iwconfig eth1 channel 11' so I
didn't make that change, but perhaps that's my problem? My AP is on
channel 11--guessing the default would be 1?<br>
<br>
Does anyone have experience with kwifimanager? I'm thinking it might
make things easier for me...<br>
<br>
Fabrice Bellet wrote:<br>
<blockquote cite="mid20031218150826.GC9692@bellet.info" type="cite">
<pre wrap="">On Wed, Dec 17, 2003 at 08:23:53AM -0700, Mike Evans wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I used 'iwconfig' to manually set all of my wlan settings. iwconfig
showed that the card had found my router and was reporting that I had
around 55/100 signal strength.
</pre>
</blockquote>
<pre wrap=""><!---->
Is your card associated to your access point ?
/proc/driver/aironet/eth1/Status should report something like that in the
first lines :
Status: CFG ACT SYN LNK PRIV KEY WEP
Mode: 3bf
</pre>
<blockquote type="cite">
<pre wrap="">But, still no internet connection.
</pre>
</blockquote>
<pre wrap=""><!---->
Is the network interface configured ?
Does ifconfig report RX/TX packets ? Do these values increase ?
</pre>
<blockquote type="cite">
<pre wrap="">My next step was to use ifconfig (and later I manually created an
itcfg-eth1 in /etc/sysconfig/network) to try to get things working. It
worked pretty well, but every time I run iwconfig, it shows the (wrong)
settings I made in 'acu'.
</pre>
</blockquote>
<pre wrap=""><!---->
ACU and iwconfig both work on the same level : the wireless parameters
configuration. That's the prerequise. So it is normal that ACU did overwrite
the previous parameters defined with iwconfig.
ifconfig (for a static IP configuration, or a DHCP client for a dynamic IP
configuration) works at the network interface level. Once the wireless
parameters are configured, the network interface needs to be configured too
(its IP address, netmask, default route, and so on).
</pre>
<blockquote type="cite">
<pre wrap="">Any ideas on how to fix this without (yet) another fresh install?
Anyone care to walk me through setting up a wireless connection
step-by-step?
</pre>
</blockquote>
<pre wrap=""><!---->
A very simple commandline-based wireless setup is the following
(according everything is static) :
# wireless setup
iwconfig eth1 essid your_essid
iwconfig eth1 channel your_channel
iwconfig eth1 key xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx
# network interface setup
ifconfig eth1 x.x.x.x netmask y.y.y.y up
route add default gw z.z.z.z
Cheers,
</pre>
</blockquote>
<br>
</body>
</html>
--------------000805090704070807000708--