![](https://seccdn.libravatar.org/avatar/4b75083608cd94d8d90072b6bbdd803d.jpg?s=120&d=mm&r=g)
I too am unable to get this to work on 2 laptops: dell latitude D600 and ibm t42. I tried to use the ipw2100 rpm from Suse 9.3. This installed with no problems but was not able to ping internal or external. I use 128bit static wep hex. Also use MAC authentication and both laptops MAC address is registered with my AP. I can right click kinternet->wireless connection then click scan tab->start scan; enter in the 128bit hex key and click connect and will always say "authenticated successfully" but can not ping anything internal or external. Anybody gotten the wireless to work. Chris -----Original Message----- From: Carlos [mailto:dubbsix@yahoo.com] Sent: Thursday, August 11, 2005 7:29 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Problems with wireless devices? Try no encryption -- as a test. Is your authentication type set as open or shared? --- robbinsc@email.arizona.edu wrote:
Quoting Carlos
: Yes - AP is using 128bit hex WEP. I've set the key a few times, but I can't figure where the problem is....I'll give no encryption a go.
Is the AP setup using any encryption?
--- robbinsc@email.arizona.edu wrote:
I'm having a lot of trouble getting my wireless card to work with my wireless AP. I have one of the famous-for-not-releasing-drivers Broadcom chipsets (specifically the Dell Truemobile 1300 (B/G) ). I tried using ndiswrapper, but I had little success. The driver installed properly, and everything else worked fine, but I couldn't get SuSE to ping the router and get an IP address. I tried a few restarts, but nothing happened. I started over again, this time using Linuxant's Driverloader package. The problem remains the same. I've set the configuration quite a few times, both within YaST and by using iwconfig. I've also tried using ifdown to stop eth1 and then restart it and dhcp with ifup. Is this a known bug, or am I doing something wrong? I can confirm the AP is working fine, because the other computers on my network are reporting no problems. The weird thing is - if I execute KWifiManager, the AP is seen, the ESSID displayed, and the signal is reported as 100% (which makes sense, as I'm seated right next to the router), but it can't detect the MAC of the AP, and it says that it's disconnected.
Thanks for the help.
-Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
![](https://seccdn.libravatar.org/avatar/ced15a38e5d3f1b425e118547840a1a6.jpg?s=120&d=mm&r=g)
Quoting "Christopher S. Arnold"
I too am unable to get this to work on 2 laptops: dell latitude D600 and ibm t42. I tried to use the ipw2100 rpm from Suse 9.3. This installed with no problems but was not able to ping internal or external. I use 128bit static wep hex. Also use MAC authentication and both laptops MAC address is registered with my AP. I can right click kinternet->wireless connection then click scan tab->start scan; enter in the 128bit hex key and click connect and will always say "authenticated successfully" but can not ping anything internal or external. Anybody gotten the wireless to work.
Chris
-----Original Message----- From: Carlos [mailto:dubbsix@yahoo.com] Sent: Thursday, August 11, 2005 7:29 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Problems with wireless devices?
Try no encryption -- as a test.
Is your authentication type set as open or shared?
--- robbinsc@email.arizona.edu wrote:
Quoting Carlos
: Yes - AP is using 128bit hex WEP. I've set the key a few times, but I can't figure where the problem is....I'll give no encryption a go.
Is the AP setup using any encryption?
--- robbinsc@email.arizona.edu wrote:
I'm having a lot of trouble getting my wireless card to work with my wireless AP. I have one of the famous-for-not-releasing-drivers Broadcom chipsets (specifically the Dell Truemobile 1300 (B/G) ). I tried using ndiswrapper, but I had little success. The driver installed properly, and everything else worked fine, but I couldn't get SuSE to ping the router and get an IP address. I tried a few restarts, but nothing happened. I started over again, this time using Linuxant's Driverloader package. The problem remains the same. I've set the configuration quite a few times, both within YaST and by using iwconfig. I've also tried using ifdown to stop eth1 and then restart it and dhcp with ifup. Is this a known bug, or am I doing something wrong? I can confirm the AP is working fine, because the other computers on my network are reporting no problems. The weird thing is - if I execute KWifiManager, the AP is seen, the ESSID displayed, and the signal is reported as 100% (which makes sense, as I'm seated right next to the router), but it can't detect the MAC of the AP, and it says that it's disconnected.
Thanks for the help.
-Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
When you boot, and the network portion of the boot runs, do you get a bunch of errors in /var/log/messages that read something like: linux ifstatus: Interface <wireless device> not available I get a whole load of these, and by then it has run out of time, and then the network does not load at all. I haven't had any luck with any sort of WEP keys yet, but I don't know what's next to do....Is this worth posting a bug for? -Chris
participants (2)
-
Christopher S. Arnold
-
robbinsc@email.arizona.edu