Re: [newbie] Detecting WLAN Card -- FIXED --Just one new problem

2004-01-12 Thread Derek Jennings
On Monday 12 Jan 2004 5:21 pm, Marc Resnick wrote:
 - Original Message -
 From: Marc Resnick [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, January 12, 2004 11:15 AM
 Subject: Re: [newbie] Detecting WLAN Card

  - Original Message -
  From: Derek Jennings [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, January 11, 2004 10:56 PM
  Subject: Re: [newbie] Detecting WLAN Card
 
   On Monday 12 Jan 2004 1:57 am, [EMAIL PROTECTED] wrote:
   SNIP
  
Derek,
I've located the Prism2_cs module, exactly where you said it was.
That means I definitely have it. But when I launch the wizard to
setup the
 
  LAN,
 
therefore detecting network cards also, this module does not show up

 on

  the
 
list. This probably has to do with the problem.
   
When I do modprobe prism2_cs, nothing happens. This card definitely
 
  works,
 
because, as I said, it works fine on Windows XP.
   
I also checked Force No APIC in the CC, and nothing changed.
   
/etc/sysconfig/pcmcia contains PCMCIA = yes
   
I added the card to the config file also.
   
There must be something one of us is forgetting or doing wrong,

 because

  the
 
card works fine.
   
Thanks for all your help so far,
Marc
  
   I am not surprised you do not see prism2_cs appear in the driver list.
 
  Drivers
 
   for pcmcia cards are always autodetected.
  
  
   When you say nothing happens when you do a modprobe, that is actually
 
  quite
 
   positive. It implies the driver is loading, and is not being rejected.
   What do you see if you do
  
   lsmod | grep prism
  
   after the modprobe? That will tell us if the driver is loading.
  
   And what do you see if you do
  
   tail -n 30 /var/log/syslog   ? Any entries about pcmcia or prism?
  
   And
   iwconfig   ?
  
   There is one other thing I forgot to check.
   The pcmcia service has to be started. In a root terminal enter
   service pcmcia restart
   You should hear two beeps as it restarts, then do
   tail -n 30 /var/log/syslog again to see what it says.
  
   derek
  
   --
   --
   www.jennings.homelinux.net
   http://twiki.mdklinuxfaq.org
 
  Derek,
  To make it easier for you, I've posted some screenshots here(because the
  files are too big to send through the mailing group):
  http://www.freewebs.com/linuxss/ss1.png
  http://www.freewebs.com/linuxss/ss2.png
  http://www.freewebs.com/linuxss/ss3.png
  http://www.freewebs.com/linuxss/ss4.png
  http://www.freewebs.com/linuxss/ss5.png
 
  I gather from those that we got part of the name of the network card
  wrong when inserting it in the config file.
 
  Thanks,
  Marc
 
  -
 -

 --

  
 
   Want to buy your Pack or Services from MandrakeSoft?
   Go to http://www.mandrakestore.com

 Derek and all that have been following,
 Linux now detects my WLAN card after who know's what I did as wlan0. The
 only step remaining is to configure it to my network. I entered the
 Mandrake Control Center, and went to the Network settings to configure it.
 It still does not appear on the list, and is not detected when I run the
 wizard. The lights on the card illuminate when I do 'service pcmcia
 restart', and I recieve information about wlan0 when I enter 'iwconfig'. It
 also now appears on the hardware list. There must be some command that I
 don't know.

 Just a little more help,
 Marc


Great.
I was just thinking you might end up compiling the driver after all.
Setting up the driver is simply a matter of creating a text file called
/etc/sysconfig/network-scripts/ifcfg-wlan0

containing something like :-

DEVICE=wlan0
BOOTPROTO=static
IPADDR=192.168.1.43
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
WIRELESS_MODE=Managed
WIRELESS_ESSID=8848DBjennings
WIRELESS_RATE=11M
WIRELESS_ENC_KEY=s:my_key


If you need to get an IP address from DHCP then put
BOOTPROTO=dhcp and then you do not need an IPADDR

WIRELESS_MODE=Managed is for use with a wireless access point.
If you are running peer to peer (no wireless access point) use Ad-Hoc

The WIRELESS_ENC_KEY is what catches everyone out.  It can be ASCII like mine 
in which case it must be oreced3ed by 's:' or a Hex number in the format 
3456-789a-bc

See 'man iwconfig' for a full description of the parameters.

service network restart
will apply the parameters.
(so will ifup wlan0   / ifdown wlan0 )

Nearly there!

derek




--
www.jennings.homelinux.net
http://twiki.mdklinuxfaq.org


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Detecting WLAN Card -- FIXED --Just one new problem

2004-01-12 Thread Derek Jennings
SNIP
  Derek and all that have been following,
  Linux now detects my WLAN card after who know's what I did as wlan0. The
  only step remaining is to configure it to my network. I entered the
  Mandrake Control Center, and went to the Network settings to configure
  it. It still does not appear on the list, and is not detected when I run
  the wizard. The lights on the card illuminate when I do 'service pcmcia
  restart', and I recieve information about wlan0 when I enter 'iwconfig'.
  It also now appears on the hardware list. There must be some command that
  I don't know.
 
  Just a little more help,
  Marc

 Great.
 I was just thinking you might end up compiling the driver after all.
 Setting up the driver is simply a matter of creating a text file called
 /etc/sysconfig/network-scripts/ifcfg-wlan0

 containing something like :-

 DEVICE=wlan0
 BOOTPROTO=static
 IPADDR=192.168.1.43
 NETMASK=255.255.255.0
 NETWORK=192.168.1.0
 BROADCAST=192.168.1.255
 ONBOOT=yes
 WIRELESS_MODE=Managed
 WIRELESS_ESSID=8848DBjennings
 WIRELESS_RATE=11M
 WIRELESS_ENC_KEY=s:my_key


 If you need to get an IP address from DHCP then put
 BOOTPROTO=dhcp and then you do not need an IPADDR

 WIRELESS_MODE=Managed is for use with a wireless access point.
 If you are running peer to peer (no wireless access point) use Ad-Hoc

 The WIRELESS_ENC_KEY is what catches everyone out.  It can be ASCII like
 mine in which case it must be oreced3ed by 's:' or a Hex number in the
 format 3456-789a-bc

 See 'man iwconfig' for a full description of the parameters.

 service network restart
 will apply the parameters.
 (so will ifup wlan0   / ifdown wlan0 )

 Nearly there!

 derek


Oh and if there is also an eth0 on this box you will have to let Linux know 
which Interface to reach the Internet through.

In /etc/sysconfig/network  enter the line
GATEWAYDEV=wlan0

Then 'service network restart'

derek
-- 
--
www.jennings.homelinux.net
http://twiki.mdklinuxfaq.org


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Detecting WLAN Card -- FIXED --Just one new problem

2004-01-12 Thread Marc Resnick

- Original Message - 
From: Derek Jennings [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 12, 2004 12:49 PM
Subject: Re: [newbie] Detecting WLAN Card -- FIXED --Just one new problem


 On Monday 12 Jan 2004 5:21 pm, Marc Resnick wrote:
  - Original Message -
  From: Marc Resnick [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Monday, January 12, 2004 11:15 AM
  Subject: Re: [newbie] Detecting WLAN Card
 
   - Original Message -
   From: Derek Jennings [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Sunday, January 11, 2004 10:56 PM
   Subject: Re: [newbie] Detecting WLAN Card
  
On Monday 12 Jan 2004 1:57 am, [EMAIL PROTECTED] wrote:
SNIP
   
 Derek,
 I've located the Prism2_cs module, exactly where you said it was.
 That means I definitely have it. But when I launch the wizard to
 setup the
  
   LAN,
  
 therefore detecting network cards also, this module does not show
up
 
  on
 
   the
  
 list. This probably has to do with the problem.

 When I do modprobe prism2_cs, nothing happens. This card
definitely
  
   works,
  
 because, as I said, it works fine on Windows XP.

 I also checked Force No APIC in the CC, and nothing changed.

 /etc/sysconfig/pcmcia contains PCMCIA = yes

 I added the card to the config file also.

 There must be something one of us is forgetting or doing wrong,
 
  because
 
   the
  
 card works fine.

 Thanks for all your help so far,
 Marc
   
I am not surprised you do not see prism2_cs appear in the driver
list.
  
   Drivers
  
for pcmcia cards are always autodetected.
   
   
When you say nothing happens when you do a modprobe, that is
actually
  
   quite
  
positive. It implies the driver is loading, and is not being
rejected.
What do you see if you do
   
lsmod | grep prism
   
after the modprobe? That will tell us if the driver is loading.
   
And what do you see if you do
   
tail -n 30 /var/log/syslog   ? Any entries about pcmcia or prism?
   
And
iwconfig   ?
   
There is one other thing I forgot to check.
The pcmcia service has to be started. In a root terminal enter
service pcmcia restart
You should hear two beeps as it restarts, then do
tail -n 30 /var/log/syslog again to see what it says.
   
derek
   
--
--
www.jennings.homelinux.net
http://twiki.mdklinuxfaq.org
  
   Derek,
   To make it easier for you, I've posted some screenshots here(because
the
   files are too big to send through the mailing group):
   http://www.freewebs.com/linuxss/ss1.png
   http://www.freewebs.com/linuxss/ss2.png
   http://www.freewebs.com/linuxss/ss3.png
   http://www.freewebs.com/linuxss/ss4.png
   http://www.freewebs.com/linuxss/ss5.png
  
   I gather from those that we got part of the name of the network card
   wrong when inserting it in the config file.
  
   Thanks,
   Marc
  
 
 -
  -
 
  --
 
   
  
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
 
  Derek and all that have been following,
  Linux now detects my WLAN card after who know's what I did as wlan0. The
  only step remaining is to configure it to my network. I entered the
  Mandrake Control Center, and went to the Network settings to configure
it.
  It still does not appear on the list, and is not detected when I run the
  wizard. The lights on the card illuminate when I do 'service pcmcia
  restart', and I recieve information about wlan0 when I enter 'iwconfig'.
It
  also now appears on the hardware list. There must be some command that I
  don't know.
 
  Just a little more help,
  Marc
 

 Great.
 I was just thinking you might end up compiling the driver after all.
 Setting up the driver is simply a matter of creating a text file called
 /etc/sysconfig/network-scripts/ifcfg-wlan0

 containing something like :-

 DEVICE=wlan0
 BOOTPROTO=static
 IPADDR=192.168.1.43
 NETMASK=255.255.255.0
 NETWORK=192.168.1.0
 BROADCAST=192.168.1.255
 ONBOOT=yes
 WIRELESS_MODE=Managed
 WIRELESS_ESSID=8848DBjennings
 WIRELESS_RATE=11M
 WIRELESS_ENC_KEY=s:my_key


 If you need to get an IP address from DHCP then put
 BOOTPROTO=dhcp and then you do not need an IPADDR

 WIRELESS_MODE=Managed is for use with a wireless access point.
 If you are running peer to peer (no wireless access point) use Ad-Hoc

 The WIRELESS_ENC_KEY is what catches everyone out.  It can be ASCII like
mine
 in which case it must be oreced3ed by 's:' or a Hex number in the format
 3456-789a-bc

 See 'man iwconfig' for a full description of the parameters.

 service network restart
 will apply the parameters.
 (so will ifup wlan0   / ifdown wlan0 )

 Nearly there!

 derek




 --
 www.jennings.homelinux.net
 http://twiki.mdklinuxfaq.org




Well I think we both

Re: [newbie] Detecting WLAN Card -- FIXED --Just one new problem

2004-01-12 Thread Derek Jennings


 Well I think we both saw this coming, Derek. I got 5 errors after trying to
 restart the network. Error for wireless request Set Encode, Set ESSID, Set
 Mod, Set Bit Rate, Set ESSID. Then it say Determining IP information for
 wlan0...SIOCSIFFLAGS: No such device.

 Here is the ifcfg-wlan0 exactly how it up, and I believe it goes according
 to my network settings:
  DEVICE=wlan0
 BOOTPROTO=dhcp
 NETMASK=255.255.255.0
 NETWORK=192.168.1.1
 BROADCAST=192.168.1.255
 ONBOOT=yes
 WIRELESS_MODE=Managed
 WIRELESS_ESSID=linksys
 WIRELESS_RATE=11M

 I removed the encyption key because I'm positive that I don't have one. If
 all of these values are defined, why am I receiving these errors?
 --Marc

Bear in mind Marc that I do not have one of these cards myself, so we are both 
learning as we go.

I have downloaded the source code for wlan-ng and see this text in the README 
file

NOTE:  linux-wlan-ng does not fully implement the wireless extensions
   interface.  This means that you can't use iwconfig and its kin to 
   set things up.  Instead, read on!

As of linux-wlan-ng 0.1.16-pre5, the configuration and launch scripts have
been largely re-written.  pcmcia/rc/hotplug now all use a common library 
of routines and use the same set of configuration files.

Now, everything relevant exists in /etc/wlan/*

/etc/wlan/wlan.conf:

This file maps between wlan devices and network IDs, and contains
the names of all devices that should be initialized by the hotplug
and rc scripts.

/etc/wlan/wlancfg-*

These files are per-network configurations.  This makes it easy to 
switch between different SSIDs and the various settings they may
require, like WEP keys and whatnot.

The bare minimum you need to do to configure your system after a fresh driver
install:

0)  Nothing whatsoever.  out-of-the-box, the driver will attempt to associate
with any access point within range.

However, we highly recommend setting up a configuration specifically for
your network, using the following method:

0)  This example assumes your network name/SSID is MyHomeNetwork
1)  cp /etc/wlan/wlancfg-DEFAULT /etc/wlan/wlancfg-MyHomeNetwork
2)  edit /etc/wlan/wlan.conf and change the SSID_wlan0 line to:
SSID_wlan0=MyHomeNetwork
3)  edit /etc/wlan/wlancfg-MyHomeNetwork, and make any necessary changes 
necessary to support your network, such as WEP and whatnot.

--
FOR PCMCIA USERS:
A)  Edit /etc/pcmcia/network.opts file to set up your IP settings. 
Note: for a station, the SSID you're connecting to will be appended to the 
current pcmcia scheme name.  You can use this to have different
IP setups for different wireless LANs you connect to (e.g. home vs. work).

Note2:  This only applies if you are using a stock pcmcia-cs 
package.  Most (if not all) distros use their own mechanisms for 
configuring pcmcia network interfaces, and thus 
/etc/pcmcia/network.opts may not even be present.

B)  Restart pcmcia-cs with the command:

/etc/rc.d/init.d/pcmcia restart

C) Insert the card.  For most cards, a solid LED indicates that the 
SSID you specified was found, a bss was joined, and the firmware 
completed the authenticate and associate processes.

D) Run ifconfig and route to determine if your IP and route settings are
listed as you wanted them.  It's also a good idea to look at the file
/etc/resolv.conf to see if your nameserver address has been set up 
correctly.

It looks like although Mandrake supplies the prism2_cs driver, the scripts to 
configure it are not supplied. I will send the scripts direct to you.

derek



-- 
--
www.jennings.homelinux.net
http://twiki.mdklinuxfaq.org


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com