[ltp] Cisco Aironet 350 Mini PCI on an R40 running SuSE 9

[Mike Evans]

Thanks for all the advice.

Well, I've had some success.  I'm not sure what did it (possible setting 
my router's authentication to "open") but I can now:
1) see my router (get it's MAC)
2) authenticate my key
3) grab an IP via DHCP
4) ping the router and boxes in my network

When I try to ping an outside IP, I get
connetc: Network is unreachable

I've disabled iptables on the laptop and I can't see anything in the 
Router's setup that would be restricting it from passing packets (and 
booting into Win XP reveals that the wireless does work on that side).

I feel like I'm so close to getting this to work... any final pieces of 
advice?

m


Ivarsson, Torbjorn (T) wrote:

>>-----Original Message-----
>>From: Mike Evans [mailto:mike@public.arl.arizona.edu]
>>Sent: Thursday, December 18, 2003 12:18 PM
>>
>>    
>>
>>>Ivarsson, Torbjorn (T) wrote 
>>>I believe you shouldn't have to specify the channel, the essid
>>>should be enough... And if you see the AP's MAC, then... there you go.
>>>
>>>I have to make the card request an IP from the AP by using the command:
>>>	dhclient
>>>      
>>>
>>  
>>My dist doesn't have dhclient, so I've been using ifdown and
>>ifup... they work with eth0 and on eth1 (for grabbing an IP only)
>>at work.
>>    
>>
>
>Well, you could always download the program (search Google) and try it. The if* commands are scripts that are run, on Mandrake they are in /etc/sysconfig/network-scripts (I believe). Those scripts should invoke some command that get the IP address from the AP. Look into those scripts and you may find another command than dhclient.
>
>  
>
>>>Do you get any error messages when you "can't connect"? The
>>>problem I had was that my firewall didn't allow me to reach
>>>any DNS servers or any internet connections for that matter.
>>>      
>>>
>> 
>>No error messages... if I try to ping my router I get a "no
>>connection" sor something of that sort.
>>
>>Are you speaking of your Router's firewall, or the firewall on
>>your thinkpad?  I guess I have no idea whether SuSE 9 is running
>>a firewall by default or not... I haven't found a GUI
>>configurator... but I could see how it might have eth1 locked
>>down (since it didn't exist when I installed).
>>    
>>
>
>That's what happened to me, eth0 worked, but eth1 didn't. I couldn't even ping other computers under that router (possibly due to blocked lo interface). I don't know how SuSE works, but it'll use iptables as the firewall for Linux (if your router has a firewall you shouldn't have to run one in Linux - I believe).
>
>There are interfaces to configure iptables, such as Shorewall and Guarddog. If you want to remove the firewall, do the following:
>	iptables --flush
>	iptables --delete-chain
>
>If you can connect to the internet after this, you probably have a firewall-configuration issue. AFAIK: if you don't have a firewall and your card has an IP address, then you should have connectivity.
>
>  
>
>>Any ideas?
>>    
>>
>
>Honestly, I don't really know anything about Linux and its configuration possibilities... But I'm an happy amatuer who likes to experiment - though it can be frustrating when it doesn't work.
>
>BTW: try not to use RichText or HTML when composing messages to this list.
>
>T.
>  
>