Re: [SLE] new at wireless configuration

...

...

Ed Harrison 2/6/2006 02:18 >>> Most wireless router/modems have an option for DHCP--that's how the IP address gets assigned to the >card

In Yast>Network Devices>Network Card, you should see an ADD button on the bottom of "Network >Card Configuration Overview" screen. If you click this and select Device Type=wireless, the module >should be "ndiswrapper".

The way you manually installed it, YES, this means that ndiswrapper has installed the proper driver for a >device that is present on your system.

Ed Harrison, Linux User # 199533 SuSE10.0, Kernel 2.6.15 PolarBar Mailer 1.26

Ed, Ken, all, Sorry for the delay. I've been trying to figure out what is going wrong here with the wireless configuration. No way, I'm not able to get this Linksys card working. As stated before, it seems that ndiswrapper does well and the Windows driver is on place and the interface initializes on booting up. But the wireless card doesn't work. Any attempt of configuring it through YaST ends with an isolated box: the on board Ethernet card becomes no longer the default link and, for instance, a ping reports host no accessible even though the Ethernet interface is theoretically well linked wit Internet. Checking the PCMCIA box in YaST > Network Setup Method > Traditional Method > Add > Manual Network Card Configuration > Device Type: Wireless, module name is not available. When unchecked, I can enter ndiswrapper at Module Name. In any case, the wireless link led in the card remains off and I'm not able to connect to any of my access points. By the way: I do need static IP addresses in the private LAN, so DHCP – at least we create static leases- is not an option at this moment. Please, could you tell how to work out this issue? What system files become modified in the installation process? Here the output for a iwconfig command... -- citlali:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any Nickname:"citlali" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate=54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr=4096 B Fragment thr=4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -- And here the output for a ndiswrapper... -- citlali:~ # ndiswrapper -l Installed drivers: lstinds driver installed, hardware present -- Thank you so much in advance, Ricardo -- Ricardo Rodríguez XEN, Resources Management -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com