![](https://seccdn.libravatar.org/avatar/ced15a38e5d3f1b425e118547840a1a6.jpg?s=120&d=mm&r=g)
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
![](https://seccdn.libravatar.org/avatar/f8799dd9e8f3efceb5135595a9a051a9.jpg?s=120&d=mm&r=g)
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
![](https://seccdn.libravatar.org/avatar/ced15a38e5d3f1b425e118547840a1a6.jpg?s=120&d=mm&r=g)
Quoting Carlos
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
![](https://seccdn.libravatar.org/avatar/f8799dd9e8f3efceb5135595a9a051a9.jpg?s=120&d=mm&r=g)
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
![](https://seccdn.libravatar.org/avatar/ced15a38e5d3f1b425e118547840a1a6.jpg?s=120&d=mm&r=g)
I tried no encryption, and thus far all seems to work fine. I had encryption
set as a shared key to begin with.
I suppose this is okay for now - I can use MAC filtering on the router
until it
gets sorted out, or until I can figure out why the encryption isn't working.
Is there an explanation for this?
Quoting Carlos
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
participants (2)
-
Carlos
-
robbinsc@email.arizona.edu