Where can I get the ndiswrapper from ? Thank you, Maura On Tue, 11 Apr 2006, Jerry Feldman wrote:

On Tuesday 11 April 2006 4:38 pm, Maura Edeweiss Monville wrote:

...

My laptop has got the following wire and wireless cards:

CLEVO/KAPOK RTL-8169 Gigabit Ethernet Configured with DHCP. Intel PRO/Wireless 2915ABG MiniPCI Adapter Configured with DHCP.

We could successfully connect to the wire network although we were not successful with the wireless connection here at FNAL. Since all laptops running Windows can easily use the wireless network in here, we are wondering whether we are missing some parameters setup in the card configuration procedure. Please, can someone help with that ? Some of the wireless cards do not have native Linux drivers. In most cases you can use the Linux ndiswrapper and the Windows drivers. There are some good instructions on how to do it. I had to do this with my new laptop. Here is a short description. http://en.opensuse.org/SDB:Ndiswrapper

Note that for some reason, on my 64-bit system ndiswrapper.ko was not set up in /lib/modules/..., but I have a few suggested solutions that should work on my system since I do have the Windows drivers.

-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-- 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

It should be on your SuSE release. If not, http://sourceforge.net/projects/ndiswrapper/ You will also need to find the appropriate Windows drivers. You will need the .sys and .inf files, but that should be on the cd that you got with the MiniPCI adapter. Most likely, the Intel drivers will be on an upcoming SUSE release. On Tuesday 11 April 2006 5:01 pm, Maura Edeweiss Monville wrote:

Where can I get the ndiswrapper from ? Thank you, Maura

On Tue, 11 Apr 2006, Jerry Feldman wrote:

...

On Tuesday 11 April 2006 4:38 pm, Maura Edeweiss Monville wrote:

...

My laptop has got the following wire and wireless cards:

CLEVO/KAPOK RTL-8169 Gigabit Ethernet Configured with DHCP. Intel PRO/Wireless 2915ABG MiniPCI Adapter Configured with DHCP.

We could successfully connect to the wire network although we were not successful with the wireless connection here at FNAL. Since all laptops running Windows can easily use the wireless network in here, we are wondering whether we are missing some parameters setup in the card configuration procedure. Please, can someone help with that ?

Some of the wireless cards do not have native Linux drivers. In most cases you can use the Linux ndiswrapper and the Windows drivers. There are some good instructions on how to do it. I had to do this with my new laptop. Here is a short description. http://en.opensuse.org/SDB:Ndiswrapper

Note that for some reason, on my 64-bit system ndiswrapper.ko was not set up in /lib/modules/..., but I have a few suggested solutions that should work on my system since I do have the Windows drivers.

-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-- 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

-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

It looks like the card came with own module "ipw2200" which is in the /lib/modules/. In fact I get the following: mauede@linux:~> lsmod ipw2200 142088 0 This module is known to YAST as well. We get an IP address but still we cannot connect: mauede@linux:~> /sbin/ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:8D:40:71 inet addr:10.225.95.44 Bcast:10.225.95.255 Mask:255.255.255.0 inet6 addr: fe80::212:f0ff:fe8d:4071/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14263 errors:0 dropped:7 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1262375 (1.2 Mb) TX bytes:4399 (4.2 Kb) Interrupt:201 Base address:0xe000 Memory:80000000-80000fff Can someone help? Thanks, Maura On Tue, 11 Apr 2006, Jerry Feldman wrote:

On Tuesday 11 April 2006 4:38 pm, Maura Edeweiss Monville wrote:

...

My laptop has got the following wire and wireless cards:

CLEVO/KAPOK RTL-8169 Gigabit Ethernet Configured with DHCP. Intel PRO/Wireless 2915ABG MiniPCI Adapter Configured with DHCP.

We could successfully connect to the wire network although we were not successful with the wireless connection here at FNAL. Since all laptops running Windows can easily use the wireless network in here, we are wondering whether we are missing some parameters setup in the card configuration procedure. Please, can someone help with that ? Some of the wireless cards do not have native Linux drivers. In most cases you can use the Linux ndiswrapper and the Windows drivers. There are some good instructions on how to do it. I had to do this with my new laptop. Here is a short description. http://en.opensuse.org/SDB:Ndiswrapper

Note that for some reason, on my 64-bit system ndiswrapper.ko was not set up in /lib/modules/..., but I have a few suggested solutions that should work on my system since I do have the Windows drivers.

-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-- 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

How can I switch it on ? Is it a manual switch ? It's packed in my laptop. If it was a cdesktop I'd open the cabinet but I do not dare do that. Maura On Tue, 11 Apr 2006, Alfredo Cole wrote:

El Martes, 11 de Abril de 2006 15:14, Maura Edeweiss Monville escribió:

...

It looks like the card came with own module "ipw2200" which is in the /lib/modules/. In fact I get the following:

mauede@linux:~> lsmod ipw2200 142088 0

This module is known to YAST as well. We get an IP address but still we cannot connect:

mauede@linux:~> /sbin/ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:8D:40:71 inet addr:10.225.95.44 Bcast:10.225.95.255 Mask:255.255.255.0 inet6 addr: fe80::212:f0ff:fe8d:4071/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14263 errors:0 dropped:7 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1262375 (1.2 Mb) TX bytes:4399 (4.2 Kb) Interrupt:201 Base address:0xe000 Memory:80000000-80000fff

Can someone help? Thanks, Maura

I think you need to switch it on. My HP has a switch for it. I wound up using Linuxant driver (http://www.linuxant.com/company/) but it is commercial.

Regards.

-- Alfredo Cole-Tuckler

-- 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

Thank you. Your argument makes sense. I'll try your suggestion tomorrow as I get at the lab. Regards, Maura On Wed, 12 Apr 2006, Joe Morris (NTM) wrote:

Maura Edeweiss Monville wrote:

...

It looks like the card came with own module "ipw2200" which is in the /lib/modules/. In fact I get the following:

mauede@linux:~> lsmod ipw2200 142088 0

This module is known to YAST as well. We get an IP address but still we cannot connect:

If you got an IP, your wireless is turned on, and it is working (i.e. communicating with your wireless router.

...

mauede@linux:~> /sbin/ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:8D:40:71 inet addr:10.225.95.44 Bcast:10.225.95.255 Mask:255.255.255.0 inet6 addr: fe80::212:f0ff:fe8d:4071/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14263 errors:0 dropped:7 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1262375 (1.2 Mb) TX bytes:4399 (4.2 Kb) Interrupt:201 Base address:0xe000 Memory:80000000-80000fff

Can someone help?

It sounds like you do not have a gateway. What is the output of /sbin/route -n? If it shows no gateway, it is probably because of a misconfiguration of your ethernet card and wireless. Since you can only have one gateway, dhcp probably is setup on the ethernet to get the address and gateway. Try setting both network adapters to STARTMODE=ifplugd (IIRC). I believe this will, if the ethernet is not plugged in, will allow the dhcp client to assign the gateway for the adapter that is actually working at the time. HTH

-- Joe Morris Registered Linux user 231871

-- 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

Maura Edeweiss Monville wrote:

Here is the answer to your question:

mauede@linux:~> /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 131.225.92.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 131.225.94.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 131.225.92.200 0.0.0.0 UG 0 0 0 eth0

OK, as I suspected, the gateway is setup by DHCP running on eth0. Is your ethernet also still plugged in?

How and where (YAST ?) can I set both network adapters to STARTMODE=ifplugd (IIRC) ?

OK, go to Yast, Network Devices, Network Card, Hit Change in the section of Already Configured Devices, Click on your devices and the Edit, Go to Advanced, Detailed Settings, and choose Device Activation at Cable Connection. You can check by going to System, etc/sysconfig Editor, Hardware, Network, <adapter ID>, STARTMODE. Just this last weekend I reinstalled 9.3 on my daughter's laptop, and noticed the same. Even though ifplugd is not a listed choice, that was what her ethernet was set to, and I was wanting ifplugd to control both, and that fixed this exact problem for hers. HTH. -- Joe Morris Registered Linux user 231871

Maura Edeweiss Monville wrote:

It looks like the card came with own module "ipw2200" which is in the /lib/modules/. In fact I get the following:

mauede@linux:~> lsmod ipw2200 142088 0

This module is known to YAST as well. We get an IP address but still we cannot connect:

mauede@linux:~> /sbin/ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:8D:40:71 inet addr:10.225.95.44 Bcast:10.225.95.255 Mask:255.255.255.0 inet6 addr: fe80::212:f0ff:fe8d:4071/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14263 errors:0 dropped:7 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1262375 (1.2 Mb) TX bytes:4399 (4.2 Kb) Interrupt:201 Base address:0xe000 Memory:80000000-80000fff

Can someone help? Thanks, Maura

On Tue, 11 Apr 2006, Jerry Feldman wrote:

...

On Tuesday 11 April 2006 4:38 pm, Maura Edeweiss Monville wrote:

...

My laptop has got the following wire and wireless cards:

CLEVO/KAPOK RTL-8169 Gigabit Ethernet Configured with DHCP. Intel PRO/Wireless 2915ABG MiniPCI Adapter Configured with DHCP.

We could successfully connect to the wire network although we were not successful with the wireless connection here at FNAL. Since all laptops running Windows can easily use the wireless network in here, we are wondering whether we are missing some parameters setup in the card configuration procedure. Please, can someone help with that ?

Some of the wireless cards do not have native Linux drivers. In most cases you can use the Linux ndiswrapper and the Windows drivers. There are some good instructions on how to do it. I had to do this with my new laptop. Here is a short description. http://en.opensuse.org/SDB:Ndiswrapper

Note that for some reason, on my 64-bit system ndiswrapper.ko was not set up in /lib/modules/..., but I have a few suggested solutions that should work on my system since I do have the Windows drivers.

-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-- 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

Do you have wpa or wep active. If so, you will need to put in the appropriate information, the keys for their respective item. Otherwise it will never connect. I have the same problem when I run windows. -- Joseph Loo jloo@acm.org

On Wednesday 12 April 2006 4:56 am, Maura Edeweiss Monville wrote:

What is a wpa and a wep ? Sorry for my ignorance ... I do not run ftp or ssh servers. I do not know if I've answered your question. Let's go back to basics. Your ifconfig shows you have an ip address. Check netstat -nr to get a picture of the routing table. Since you appear to be doing DHCP, your gateway should already be set up for you.

The next thing is to check to see if your name server table has been set up. Just cat /etc/resolv.conf. That should be updated when DHCP established the connection. The next thing to do assuming both of these check out is to ping another host on the network. Most of the time, the gateway should be able to be pinged. WPA and WEP are encryption techniques. You should find out from the network admin if the wireless connection is open or encrypted, and if encrypted, get the encryption method and the keys from the admin. To set things up, go into YaST/network card, and edit your card. Automatic setup via DHCP should be selected. Then go into Host Name and Server Change Host Name via DHCP and Update Name Servers and Search list via DHCP should be selected. This will cause the /etc/resolv.conf to be written when you connect to your DHCP server. Click on Ok, then click on next. At some point, you should see a screen that establishes the wireless mode. You want the mode to be managed. You may or may not want to put an ESSID in. (This depends on your site). You should also be able to select encryption. In general, you will not even get an IP address if you are not encrypted and are trying to connect through an encrypted network. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9