Re: wireless network problems
After many, many hours of trying to get my wireless card working with the bf24 kernel in debian woody, I think I've got to admit failure. (Another noob bites the dust!) The card stayed lit, and was correctly identified by both iwconfig eth1 and cardctl ident, but I couldn't connect to the internet. I also tried pump -i eth1 to no avail, and every configuration option I could think of in /etc/network/ interfaces, or in /etc/pcmcia/wireless.opts. I've uninstalled debian to remove the temptation to do any more tinkering. It's frustrating to have gotten so close--I can see what a great system debian provides, and I really admire the noncommercial quality of the project, not to mention the nice people on this list. Thanks to everyone who tried to help. (Although even now I'm looking forward to the release of sarge. Hmm, maybe I'll be able to get things working then... :-) ) For now, back to windows. arrgh. Tim Nate Duehr wrote: On Thursday, Jan 1, 2004, at 16:59 America/Denver, Matt Foster wrote: Quoting Marcus Crafter ([EMAIL PROTECTED]): Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt I really got the impression that Tim's card was an older Orinoco and from the stuff he posted from his system it was detected and working fine. There appears to have been this side thread (perhaps started by my early warning that the newer Orinoco cards use a new chipset) that won't die about using the drivers for the newer chipset. But just so Tim's not confused, I think from what I was reading his hardware setup is fine. Someone who has seen both cards in service could tell us more about whether or not the newer chipset still reports the old card name to the kernel and confuses it into loading the older driver. This is good info to get into the archives for newer card chipset owners, though! ps. Happy New Year to everyone :) 2004... here we come! -- Nate Duehr, [EMAIL PROTECTED]
Re: wireless network problems
After many, many hours of trying to get my wireless card working with the bf24 kernel in debian woody, I think I've got to admit failure. (Another noob bites the dust!) The card stayed lit, and was correctly identified by both iwconfig eth1 and cardctl ident, but I couldn't connect to the internet. I also tried pump -i eth1 to no avail, and every configuration option I could think of in /etc/network/ interfaces, or in /etc/pcmcia/wireless.opts. I've uninstalled debian to remove the temptation to do any more tinkering. It's frustrating to have gotten so close--I can see what a great system debian provides, and I really admire the noncommercial quality of the project, not to mention the nice people on this list. Thanks to everyone who tried to help. (Although even now I'm looking forward to the release of sarge. Hmm, maybe I'll be able to get things working then... :-) ) For now, back to windows. arrgh. Tim Nate Duehr wrote: On Thursday, Jan 1, 2004, at 16:59 America/Denver, Matt Foster wrote: Quoting Marcus Crafter ([EMAIL PROTECTED]): Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt I really got the impression that Tim's card was an older Orinoco and from the stuff he posted from his system it was detected and working fine. There appears to have been this side thread (perhaps started by my early warning that the newer Orinoco cards use a new chipset) that won't die about using the drivers for the newer chipset. But just so Tim's not confused, I think from what I was reading his hardware setup is fine. Someone who has seen both cards in service could tell us more about whether or not the newer chipset still reports the old card name to the kernel and confuses it into loading the older driver. This is good info to get into the archives for newer card chipset owners, though! ps. Happy New Year to everyone :) 2004... here we come! -- Nate Duehr, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Thursday, Jan 1, 2004, at 16:59 America/Denver, Matt Foster wrote: Quoting Marcus Crafter ([EMAIL PROTECTED]): Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt I really got the impression that Tim's card was an older Orinoco and from the stuff he posted from his system it was detected and working fine. There appears to have been this side thread (perhaps started by my early warning that the newer Orinoco cards use a new chipset) that won't die about using the drivers for the newer chipset. But just so Tim's not confused, I think from what I was reading his hardware setup is fine. Someone who has seen both cards in service could tell us more about whether or not the newer chipset still reports the old card name to the kernel and confuses it into loading the older driver. This is good info to get into the archives for newer card chipset owners, though! ps. Happy New Year to everyone :) 2004... here we come! -- Nate Duehr, [EMAIL PROTECTED]
Re: wireless network problems
On Thursday, Jan 1, 2004, at 16:59 America/Denver, Matt Foster wrote: Quoting Marcus Crafter ([EMAIL PROTECTED]): Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt I really got the impression that Tim's card was an older Orinoco and from the stuff he posted from his system it was detected and working fine. There appears to have been this side thread (perhaps started by my early warning that the newer Orinoco cards use a new chipset) that won't die about using the drivers for the newer chipset. But just so Tim's not confused, I think from what I was reading his hardware setup is fine. Someone who has seen both cards in service could tell us more about whether or not the newer chipset still reports the old card name to the kernel and confuses it into loading the older driver. This is good info to get into the archives for newer card chipset owners, though! ps. Happy New Year to everyone :) 2004... here we come! -- Nate Duehr, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Quoting Marcus Crafter ([EMAIL PROTECTED]): > Mate, you'll probably need to take a look at the madwifi project at sf.net > to get the Gold card working (assuming it's operating with the Atheros > chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine > with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt ps. Happy New Year to everyone :) -- Matt Foster [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mattfoster.clara.co.uk icq: 106411042 signature.asc Description: Digital signature
Re: wireless network problems
Quoting Marcus Crafter ([EMAIL PROTECTED]): > Mate, you'll probably need to take a look at the madwifi project at sf.net > to get the Gold card working (assuming it's operating with the Atheros > chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine > with this driver. One thing I would add about the madwifi drivers is that if you want them to work very well you'll need to check them out of cvs. The current tarballs on the site are old (old old). You might find the FAQ and wiki helpful. There are links from madwifi's sf page. have fun, matt ps. Happy New Year to everyone :) -- Matt Foster [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mattfoster.clara.co.uk icq: 106411042 signature.asc Description: Digital signature
Re: wireless network problems
I think I will give gnome a try. Thanks. Tim [EMAIL PROTECTED] wrote: Hi, Citát Tim Folger <[EMAIL PROTECTED]>: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. So now I'm about to reinstall woody. I'm Just a note on KDE... I have an instalation on an awfully slow machine and I do like to load to GNOME since it works more stable than KDE in my case, at least the applications will run :( if I need to use and KDE application I either do it from term window by calling it`s name lets say I want to modify a user ; after I log in as a root I call "kuser" command. Well, try gnome... ed. wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim Andy Firman wrote: Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? I have the same card. Are you using 40 or 128 bit encryption? Have you tried setting encryption manually? Such as: ~$ iwconfig eth1 enc 01234567890123456789123456 (for 128 bit encryption there are 26 characters needed and for the 40 bit encryption there are 10 characters needed...I think... so if you are using only 5 characters...that may be the problem) Also, have you played around with /etc/pcmcia/wireless.opts ? I don't use the interfaces file for the wireless settings like you do. All my configuration in in wireless.opts and the only thing in my interfaces file is this: auto eth1 iface eth1 inet dhcp One other thing, I remember vaguely having trouble with the bf24 kernel and wireless. Maybe you can try to do a custom kernel? Also what do you have for modules? This is what I have when I do lsmod: orinoco_cs 4724 1 orinoco37140 0 [orinoco_cs] hermes 6020 0 [orinoco_cs orinoco] Hope this gets you started in the right direction. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
I think I will give gnome a try. Thanks. Tim [EMAIL PROTECTED] wrote: Hi, Citát Tim Folger <[EMAIL PROTECTED]>: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. So now I'm about to reinstall woody. I'm Just a note on KDE... I have an instalation on an awfully slow machine and I do like to load to GNOME since it works more stable than KDE in my case, at least the applications will run :( if I need to use and KDE application I either do it from term window by calling it`s name lets say I want to modify a user ; after I log in as a root I call "kuser" command. Well, try gnome... ed. wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim Andy Firman wrote: Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? I have the same card. Are you using 40 or 128 bit encryption? Have you tried setting encryption manually? Such as: ~$ iwconfig eth1 enc 01234567890123456789123456 (for 128 bit encryption there are 26 characters needed and for the 40 bit encryption there are 10 characters needed...I think... so if you are using only 5 characters...that may be the problem) Also, have you played around with /etc/pcmcia/wireless.opts ? I don't use the interfaces file for the wireless settings like you do. All my configuration in in wireless.opts and the only thing in my interfaces file is this: auto eth1 iface eth1 inet dhcp One other thing, I remember vaguely having trouble with the bf24 kernel and wireless. Maybe you can try to do a custom kernel? Also what do you have for modules? This is what I have when I do lsmod: orinoco_cs 4724 1 orinoco37140 0 [orinoco_cs] hermes 6020 0 [orinoco_cs orinoco] Hope this gets you started in the right direction. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hello All, Happy ne year (I was sleeping ;-) ) And, - May the Source be with us ! Greetings Michelle Am 2003-12-31 17:11:39, schrieb Tim Folger: >Hi Marcel, Michelle, and Marcus, > >Thanks for the advice--I'll be taking another whack at getting the >network running this weekend and will let you know what happens. > >Happy 04, > >Tim > >Marcel Meckel wrote: > >>>You mentioned >>>dhcp packages that might have to be installed. Would you happen to know >>>what the packages are called? >>> >>> >> >>Try package pump, i had always problems with dhcpclient. Afterwards do >>pump -i eth1 and it should work. >> >>Happy New Year, >>Marcel.
Re: wireless network problems
Hello All, Happy ne year (I was sleeping ;-) ) And, - May the Source be with us ! Greetings Michelle Am 2003-12-31 17:11:39, schrieb Tim Folger: >Hi Marcel, Michelle, and Marcus, > >Thanks for the advice--I'll be taking another whack at getting the >network running this weekend and will let you know what happens. > >Happy 04, > >Tim > >Marcel Meckel wrote: > >>>You mentioned >>>dhcp packages that might have to be installed. Would you happen to know >>>what the packages are called? >>> >>> >> >>Try package pump, i had always problems with dhcpclient. Afterwards do >>pump -i eth1 and it should work. >> >>Happy New Year, >>Marcel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Marcel, Michelle, and Marcus, Thanks for the advice--I'll be taking another whack at getting the network running this weekend and will let you know what happens. Happy 04, Tim Marcel Meckel wrote: You mentioned dhcp packages that might have to be installed. Would you happen to know what the packages are called? Try package pump, i had always problems with dhcpclient. Afterwards do pump -i eth1 and it should work. Happy New Year, Marcel.
Re: wireless network problems
Hi Marcel, Michelle, and Marcus, Thanks for the advice--I'll be taking another whack at getting the network running this weekend and will let you know what happens. Happy 04, Tim Marcel Meckel wrote: You mentioned dhcp packages that might have to be installed. Would you happen to know what the packages are called? Try package pump, i had always problems with dhcpclient. Afterwards do pump -i eth1 and it should work. Happy New Year, Marcel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
> You mentioned > dhcp packages that might have to be installed. Would you happen to know > what the packages are called? Try package pump, i had always problems with dhcpclient. Afterwards do pump -i eth1 and it should work. Happy New Year, Marcel.
Re: wireless network problems
Hi Nate, If you were in Texas you weren't too far from me--I'm in New Mexico. Anyway, still no luck connecting with the network. My access point (an orinoco RG-1000) functions as a dhcp server, and hands out ip addresses to the two laptops I have at home on the network. (At least that's the way I think it works in Windows and in Xandros, a commercial debian derivative) I'm in windows right now, so I can't check the /etc/network/interfaces file, but I think the first line in the file is something like "inet eth1 dhcp" which was put there automatically during the network configuration stage of the installation. You mentioned dhcp packages that might have to be installed. Would you happen to know what the packages are called? During installation I configured pcmcia support , then installed wireless modules (orinoco and hermes), set the hostname, and configured the network using dhcp. All of this was done using the bf24 kernel with woody release 2. I've been wondering if I missed something during installation, which isn't unlikely because I've only been working with debian for a few weeks now (not to mention congenital blockheadedness). Happy new year, Tim Nate Duehr wrote: On Saturday 27 December 2003 09:53 pm, Tim Folger wrote: Hi Nate, Thanks for the quick reply. Here's what iwconfig produces: (I had to copy it by hand and reboot into windows) lo no wireless extensions eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Hi Tim, Sorry it's been a while since I replied, I was travelling to Texas for holidays. From reading this message and some of the follow-ups it sounds like the card is working perfectly and associating with the Access Point, and the problem is in either getting an IP address (DHCP problem, or dhcp packages not installed) or routing. How is it coming along, did you have any luck in getting it to talk to the rest of the network? Do you have a DHCP server somewhere on your network and do you have your network scripts set up to use DHCP, or were you planning to use a static address and set the router IP appropriately?
Re: wireless network problems
> You mentioned > dhcp packages that might have to be installed. Would you happen to know > what the packages are called? Try package pump, i had always problems with dhcpclient. Afterwards do pump -i eth1 and it should work. Happy New Year, Marcel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Nate, If you were in Texas you weren't too far from me--I'm in New Mexico. Anyway, still no luck connecting with the network. My access point (an orinoco RG-1000) functions as a dhcp server, and hands out ip addresses to the two laptops I have at home on the network. (At least that's the way I think it works in Windows and in Xandros, a commercial debian derivative) I'm in windows right now, so I can't check the /etc/network/interfaces file, but I think the first line in the file is something like "inet eth1 dhcp" which was put there automatically during the network configuration stage of the installation. You mentioned dhcp packages that might have to be installed. Would you happen to know what the packages are called? During installation I configured pcmcia support , then installed wireless modules (orinoco and hermes), set the hostname, and configured the network using dhcp. All of this was done using the bf24 kernel with woody release 2. I've been wondering if I missed something during installation, which isn't unlikely because I've only been working with debian for a few weeks now (not to mention congenital blockheadedness). Happy new year, Tim Nate Duehr wrote: On Saturday 27 December 2003 09:53 pm, Tim Folger wrote: Hi Nate, Thanks for the quick reply. Here's what iwconfig produces: (I had to copy it by hand and reboot into windows) lo no wireless extensions eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Hi Tim, Sorry it's been a while since I replied, I was travelling to Texas for holidays. From reading this message and some of the follow-ups it sounds like the card is working perfectly and associating with the Access Point, and the problem is in either getting an IP address (DHCP problem, or dhcp packages not installed) or routing. How is it coming along, did you have any luck in getting it to talk to the rest of the network? Do you have a DHCP server somewhere on your network and do you have your network scripts set up to use DHCP, or were you planning to use a static address and set the router IP appropriately? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Saturday 27 December 2003 09:53 pm, Tim Folger wrote: > Hi Nate, > > Thanks for the quick reply. Here's what iwconfig produces: (I had to > copy it by hand and reboot into windows) > > lo no wireless extensions > > eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal > level: -69dBm > Noise level:-96dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Hi Tim, Sorry it's been a while since I replied, I was travelling to Texas for holidays. From reading this message and some of the follow-ups it sounds like the card is working perfectly and associating with the Access Point, and the problem is in either getting an IP address (DHCP problem, or dhcp packages not installed) or routing. How is it coming along, did you have any luck in getting it to talk to the rest of the network? Do you have a DHCP server somewhere on your network and do you have your network scripts set up to use DHCP, or were you planning to use a static address and set the router IP appropriately? -- Nate Duehr, [EMAIL PROTECTED]
Re: wireless network problems
On Saturday 27 December 2003 09:53 pm, Tim Folger wrote: > Hi Nate, > > Thanks for the quick reply. Here's what iwconfig produces: (I had to > copy it by hand and reboot into windows) > > lo no wireless extensions > > eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal > level: -69dBm > Noise level:-96dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Hi Tim, Sorry it's been a while since I replied, I was travelling to Texas for holidays. From reading this message and some of the follow-ups it sounds like the card is working perfectly and associating with the Access Point, and the problem is in either getting an IP address (DHCP problem, or dhcp packages not installed) or routing. How is it coming along, did you have any luck in getting it to talk to the rest of the network? Do you have a DHCP server somewhere on your network and do you have your network scripts set up to use DHCP, or were you planning to use a static address and set the router IP appropriately? -- Nate Duehr, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Am 2003-12-30 19:05:08, schrieb Tim Folger: >Hi, > >I've been having trouble getting an orinoco gold card to work on my >laptop with woody using the bf24 kernel. I'm a newbie and am thinking >about taking the plunge and trying to compile a custom kernel. Does >anyone have any recommendations for a kernel that would best support >wireless networking with woody? > >Thanks, > >Tim Hello Tim, there is nothing special... If the Installer does not detect automaticly the PCMCIA, choose it manualy... and configure it. Use the bf24 Bootfloppies... The Lucent ORINOCO Cards are working while installing the Base... Even if I use a Toshiba t1950ct (486dx2/50 with 12 MB of memory) Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org.
Re: wireless network problems
Hi Tim, Hope all is well. Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. Kernel wise, you'll need any 2.4.x kernel (check the madwifi docs), with it's associated headers so you can build the necessary madwifi kernel modules. Hope that helps. Cheers, Marcus On Tue, Dec 30, 2003 at 07:05:08PM -0700, Tim Folger wrote: > Hi, > > I've been having trouble getting an orinoco gold card to work on my > laptop with woody using the bf24 kernel. I'm a newbie and am thinking > about taking the plunge and trying to compile a custom kernel. Does > anyone have any recommendations for a kernel that would best support > wireless networking with woody? > > Thanks, > > Tim > > Andy Firman wrote: > > >>eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > >>Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > >>Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > >>Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: > >>-69dBm > >>Noise level:-96dBm > >>Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > >>Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > >> > >>When I run cardctl ident I get: > >> > >>Socket 1: > >> Product info: "Lucent Technologies", "Wavelan/IEEE", > >>"Version 01.01", "" > >>function: 6 (network) > >> > >>I'm wondering if my problem could simply be something to do with > >>permissions. I noticed that in one of your earlier messages you could > >>run cardctl at a $ prompt, but I had to be root. Same thing for > >>iwconfig. I added myself to the dialout and dip groups, but still can't > >>connect to the internet. > >> > >> > > > >Looks like your card is seeing the access point. Good. > > > >What does ifconfig say? > > > >You need to be root to run iwconfig, cardctl, and ifconfig. > >I use sudo most of the time. > > > >If you are not getting an IP from the AP, then you can try giving > >yourself and IP manually such as: > > > >ifconfig eth1 192.168.1.5 > > > >then do this: > > > >route add default gateway 192.168.1.1 > > > >(assuming your RG is 192.168.1.1 and you on a standard > >private network 192.168.1.0/24) > > > >Then see if you can ping the AP. > > > >Like I said before, the Orinoco cards did not work well for me until > >I compiled a custom kernel. This may be a bit of a challenge for you, > >but once you learn how to do thisit will make things easier. > > > >http://newbiedoc.sourceforge.net/system/kernel-pkg.html > > > >Debian is not easy for beginners. But if you stick with it, > >you will be happy in the future. > > > > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- . ,,$, Marcus Crafter ;$' ':Computer Systems Engineer $: : ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$,_/\ &&:' 60327 Frankfurt Germany ' /( &&& \_' . &&&:
Re: wireless network problems
Am 2003-12-30 19:05:08, schrieb Tim Folger: >Hi, > >I've been having trouble getting an orinoco gold card to work on my >laptop with woody using the bf24 kernel. I'm a newbie and am thinking >about taking the plunge and trying to compile a custom kernel. Does >anyone have any recommendations for a kernel that would best support >wireless networking with woody? > >Thanks, > >Tim Hello Tim, there is nothing special... If the Installer does not detect automaticly the PCMCIA, choose it manualy... and configure it. Use the bf24 Bootfloppies... The Lucent ORINOCO Cards are working while installing the Base... Even if I use a Toshiba t1950ct (486dx2/50 with 12 MB of memory) Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Tim, Hope all is well. Mate, you'll probably need to take a look at the madwifi project at sf.net to get the Gold card working (assuming it's operating with the Atheros chipset). I've got the 802.11/a/b/g gold card (miniPCI) and it works fine with this driver. Kernel wise, you'll need any 2.4.x kernel (check the madwifi docs), with it's associated headers so you can build the necessary madwifi kernel modules. Hope that helps. Cheers, Marcus On Tue, Dec 30, 2003 at 07:05:08PM -0700, Tim Folger wrote: > Hi, > > I've been having trouble getting an orinoco gold card to work on my > laptop with woody using the bf24 kernel. I'm a newbie and am thinking > about taking the plunge and trying to compile a custom kernel. Does > anyone have any recommendations for a kernel that would best support > wireless networking with woody? > > Thanks, > > Tim > > Andy Firman wrote: > > >>eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > >>Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > >>Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > >>Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: > >>-69dBm > >>Noise level:-96dBm > >>Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > >>Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > >> > >>When I run cardctl ident I get: > >> > >>Socket 1: > >> Product info: "Lucent Technologies", "Wavelan/IEEE", > >>"Version 01.01", "" > >>function: 6 (network) > >> > >>I'm wondering if my problem could simply be something to do with > >>permissions. I noticed that in one of your earlier messages you could > >>run cardctl at a $ prompt, but I had to be root. Same thing for > >>iwconfig. I added myself to the dialout and dip groups, but still can't > >>connect to the internet. > >> > >> > > > >Looks like your card is seeing the access point. Good. > > > >What does ifconfig say? > > > >You need to be root to run iwconfig, cardctl, and ifconfig. > >I use sudo most of the time. > > > >If you are not getting an IP from the AP, then you can try giving > >yourself and IP manually such as: > > > >ifconfig eth1 192.168.1.5 > > > >then do this: > > > >route add default gateway 192.168.1.1 > > > >(assuming your RG is 192.168.1.1 and you on a standard > >private network 192.168.1.0/24) > > > >Then see if you can ping the AP. > > > >Like I said before, the Orinoco cards did not work well for me until > >I compiled a custom kernel. This may be a bit of a challenge for you, > >but once you learn how to do thisit will make things easier. > > > >http://newbiedoc.sourceforge.net/system/kernel-pkg.html > > > >Debian is not easy for beginners. But if you stick with it, > >you will be happy in the future. > > > > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- . ,,$, Marcus Crafter ;$' ':Computer Systems Engineer $: : ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$,_/\ &&:' 60327 Frankfurt Germany ' /( &&& \_' . &&&: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Tue, 30 Dec 2003, Tim Folger wrote: > I've been having trouble getting an orinoco gold card to work on my > laptop with woody using the bf24 kernel. I'm a newbie and am thinking > about taking the plunge and trying to compile a custom kernel. Does > anyone have any recommendations for a kernel that would best support > wireless networking with woody? Personally, I am very happy using the stock kernel from any kernel.org mirror. This just works, and makes it easier to use additional upstream patches. Specifically, it made it easy to integrate the HostAP driver into my system. This, in turn, made my wireless network card vastly more useful than it had previously been. The big secret is to install the Debian 'kernel-package' tool, which will build a nice .deb file from your kernel source tree. This allows you to retain all the package management while keeping the flexibility you had before. Daniel -- Even a modestly competent district attorney can get a grand jury to indict a ham sandwich. -- Sol Wachtler
Re: wireless network problems
Hi, I've been having trouble getting an orinoco gold card to work on my laptop with woody using the bf24 kernel. I'm a newbie and am thinking about taking the plunge and trying to compile a custom kernel. Does anyone have any recommendations for a kernel that would best support wireless networking with woody? Thanks, Tim Andy Firman wrote: eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future.
Re: wireless network problems
On Tue, 30 Dec 2003, Tim Folger wrote: > I've been having trouble getting an orinoco gold card to work on my > laptop with woody using the bf24 kernel. I'm a newbie and am thinking > about taking the plunge and trying to compile a custom kernel. Does > anyone have any recommendations for a kernel that would best support > wireless networking with woody? Personally, I am very happy using the stock kernel from any kernel.org mirror. This just works, and makes it easier to use additional upstream patches. Specifically, it made it easy to integrate the HostAP driver into my system. This, in turn, made my wireless network card vastly more useful than it had previously been. The big secret is to install the Debian 'kernel-package' tool, which will build a nice .deb file from your kernel source tree. This allows you to retain all the package management while keeping the flexibility you had before. Daniel -- Even a modestly competent district attorney can get a grand jury to indict a ham sandwich. -- Sol Wachtler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi, I've been having trouble getting an orinoco gold card to work on my laptop with woody using the bf24 kernel. I'm a newbie and am thinking about taking the plunge and trying to compile a custom kernel. Does anyone have any recommendations for a kernel that would best support wireless networking with woody? Thanks, Tim Andy Firman wrote: eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Andy, Thanks for the advice. Here's what ifconfig says: eth1 Linc encap :Ethernet HWaddr 00:02:2D:60:F9:E1 inet addr: 10.0.1.6 Bcast: 10.0.1.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 RX packets: 2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes: 5881 (5.7klB) TX bytes: 792 (792.0b) Tim Andy Firman wrote: eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future.
Re: wireless network problems
Hi Andy, Thanks for the advice. Here's what ifconfig says: eth1 Linc encap :Ethernet HWaddr 00:02:2D:60:F9:E1 inet addr: 10.0.1.6 Bcast: 10.0.1.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 RX packets: 2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes: 5881 (5.7klB) TX bytes: 792 (792.0b) Tim Andy Firman wrote: eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
> eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: > -69dBm > Noise level:-96dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > When I run cardctl ident I get: > > Socket 1: > Product info: "Lucent Technologies", "Wavelan/IEEE", > "Version 01.01", "" > function: 6 (network) > > I'm wondering if my problem could simply be something to do with > permissions. I noticed that in one of your earlier messages you could > run cardctl at a $ prompt, but I had to be root. Same thing for > iwconfig. I added myself to the dialout and dip groups, but still can't > connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future.
Re: wireless network problems
> eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" > Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 > Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off > Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: > -69dBm > Noise level:-96dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > When I run cardctl ident I get: > > Socket 1: > Product info: "Lucent Technologies", "Wavelan/IEEE", > "Version 01.01", "" > function: 6 (network) > > I'm wondering if my problem could simply be something to do with > permissions. I noticed that in one of your earlier messages you could > run cardctl at a $ prompt, but I had to be root. Same thing for > iwconfig. I added myself to the dialout and dip groups, but still can't > connect to the internet. Looks like your card is seeing the access point. Good. What does ifconfig say? You need to be root to run iwconfig, cardctl, and ifconfig. I use sudo most of the time. If you are not getting an IP from the AP, then you can try giving yourself and IP manually such as: ifconfig eth1 192.168.1.5 then do this: route add default gateway 192.168.1.1 (assuming your RG is 192.168.1.1 and you on a standard private network 192.168.1.0/24) Then see if you can ping the AP. Like I said before, the Orinoco cards did not work well for me until I compiled a custom kernel. This may be a bit of a challenge for you, but once you learn how to do thisit will make things easier. http://newbiedoc.sourceforge.net/system/kernel-pkg.html Debian is not easy for beginners. But if you stick with it, you will be happy in the future. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Nate, Thanks for the quick reply. Here's what iwconfig produces: (I had to copy it by hand and reboot into windows) lo no wireless extensions eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Tim Nate Duehr wrote: What does iwconfig show? On Sat, Dec 27, 2003 at 07:41:30PM -0700, Tim Folger wrote: Hi Nate, Andy, and other debian-laptop users, I reinstalled debian woody this weekend (I turned off encryption on the RG-1000 before installation) and during installation my orinoco gold card lit up, and I got a message during the network configuration stage of the installation that my network had been successfully set up. The card lights up when I boot, and stays lit up when I log into gnome, but I can't connect to the internet when I run galeon or any other internet application. When I run iwconfig eth1, the correct essid and nickname are displayed. I've edited /etc/pcmcia/wireless.opts with what I believe are the correct values (after deleting the specified four lines as instructed in that file to activate the wireless schemes). The values I've entered are: ESSID = "1ecb13" (network name required by the RG-1000) MODE = "Managed" RATE = "11M" CHANNEL = "10" For now I've commented out the encryption key setting, since I've turned encryption off. I've been hammering at this off and on for a few weeks, and am starting to think that maybe debian is a bit advanced for me, and that I should try a commercial distro. Thanks in advance for any advice. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun,
Re: wireless network problems
Hi Nate, Thanks for the quick reply. Here's what iwconfig produces: (I had to copy it by hand and reboot into windows) lo no wireless extensions eth1 IEEE 802.11-DS ESSID: 1ecb13: Nickname: "Folger" Mode: Managed Frequency: 2.412GHz Access Point: 00:02:2D:1E:CB:13 Bit Rate=11Mb/s Tx-Power=15dBm Sensitivity:1/3 RTS thr:off Fragment thr:2347B Encryption key: off Link Quality:27/92 Signal level: -69dBm Noise level:-96dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I run cardctl ident I get: Socket 1: Product info: "Lucent Technologies", "Wavelan/IEEE", "Version 01.01", "" function: 6 (network) I'm wondering if my problem could simply be something to do with permissions. I noticed that in one of your earlier messages you could run cardctl at a $ prompt, but I had to be root. Same thing for iwconfig. I added myself to the dialout and dip groups, but still can't connect to the internet. Tim Nate Duehr wrote: What does iwconfig show? On Sat, Dec 27, 2003 at 07:41:30PM -0700, Tim Folger wrote: Hi Nate, Andy, and other debian-laptop users, I reinstalled debian woody this weekend (I turned off encryption on the RG-1000 before installation) and during installation my orinoco gold card lit up, and I got a message during the network configuration stage of the installation that my network had been successfully set up. The card lights up when I boot, and stays lit up when I log into gnome, but I can't connect to the internet when I run galeon or any other internet application. When I run iwconfig eth1, the correct essid and nickname are displayed. I've edited /etc/pcmcia/wireless.opts with what I believe are the correct values (after deleting the specified four lines as instructed in that file to activate the wireless schemes). The values I've entered are: ESSID = "1ecb13" (network name required by the RG-1000) MODE = "Managed" RATE = "11M" CHANNEL = "10" For now I've commented out the encryption key setting, since I've turned encryption off. I've been hammering at this off and on for a few weeks, and am starting to think that maybe debian is a bit advanced for me, and that I should try a commercial distro. Thanks in advance for any advice. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Nate, Andy, and other debian-laptop users, I reinstalled debian woody this weekend (I turned off encryption on the RG-1000 before installation) and during installation my orinoco gold card lit up, and I got a message during the network configuration stage of the installation that my network had been successfully set up. The card lights up when I boot, and stays lit up when I log into gnome, but I can't connect to the internet when I run galeon or any other internet application. When I run iwconfig eth1, the correct essid and nickname are displayed. I've edited /etc/pcmcia/wireless.opts with what I believe are the correct values (after deleting the specified four lines as instructed in that file to activate the wireless schemes). The values I've entered are: ESSID = "1ecb13" (network name required by the RG-1000) MODE = "Managed" RATE = "11M" CHANNEL = "10" For now I've commented out the encryption key setting, since I've turned encryption off. I've been hammering at this off and on for a few weeks, and am starting to think that maybe debian is a bit advanced for me, and that I should try a commercial distro. Thanks in advance for any advice. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun,
Re: wireless network problems
Hi Nate, Andy, and other debian-laptop users, I reinstalled debian woody this weekend (I turned off encryption on the RG-1000 before installation) and during installation my orinoco gold card lit up, and I got a message during the network configuration stage of the installation that my network had been successfully set up. The card lights up when I boot, and stays lit up when I log into gnome, but I can't connect to the internet when I run galeon or any other internet application. When I run iwconfig eth1, the correct essid and nickname are displayed. I've edited /etc/pcmcia/wireless.opts with what I believe are the correct values (after deleting the specified four lines as instructed in that file to activate the wireless schemes). The values I've entered are: ESSID = "1ecb13" (network name required by the RG-1000) MODE = "Managed" RATE = "11M" CHANNEL = "10" For now I've commented out the encryption key setting, since I've turned encryption off. I've been hammering at this off and on for a few weeks, and am starting to think that maybe debian is a bit advanced for me, and that I should try a commercial distro. Thanks in advance for any advice. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Thanks Nate. I'll try setting it up this weekend and will post here to let you know how it went. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun,
Re: wireless network problems
Thanks Nate. I'll try setting it up this weekend and will post here to let you know how it went. Tim Nate Duehr wrote: On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: > The orinoco gold card is about a year old now, and it worked with > Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun, -- Nate Duehr <[EMAIL PROTECTED]>
Re: wireless network problems
On Tue, Dec 23, 2003 at 04:59:44PM -0700, Tim Folger wrote: > The orinoco gold card is about a year old now, and it worked with > Xandros, a commercial distro based on debian woody. That's a good sign. :-) I would definitely start by turning off the encryption on the RG-1000 temporarily to see if you can get a "normal" connection going, then turn it back on using the method mentioned where you can define a hex WEP key directly in the RG-1000. Once you do that, you can define the WEP key in hex on the Linux boxes, and other clients and you'll be all up and runnin'. Have fun, -- Nate Duehr <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hey Andy, Thanks again for all the pointers. I'll definitely study that newbie page at sourceforge. I did notice the information in wireless.opts about the RG-1000, and entered the correct essid. Maybe I'll try turning encryption off and see if that helps. Just before KDE failed I had also edited /etc/pcmcia/network.opts, entering "y" for dhcp. I wonder if that could have caused some kind of conflict? Maybe I should just stick with entering my network information in wireless.opts? I guess I should probably stick with stable until I know what I'm doing. Happy holidays, Tim Andy Firman wrote: On Tue, Dec 23, 2003 at 11:54:31AM -0700, Tim Folger wrote: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. No advice on that issue. Read the RG-1000 manual carefully. There are two ways to do the keys...alphanumeric and hex. I have always used the silver card. Not sure if that is an issue. And I am running Debian unstable just so you know... If it is brand new, it might be a newer chipset like Nate mentioned in another post. Try doing this command: "cardctl ident" This is what I get: [EMAIL PROTECTED]:~$ sudo cardctl ident Socket 0: no product info available Socket 1: product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", "" manfid: 0x0156, 0x0002 function: 6 (network) I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. Bummer. It should not have an effect on your desktop environment. I wonder what you did? The only section in wireless.opts that you need to mess with is this: (and by the way...do you see this in your wireless.opts???) - # Here are a few examples with a few Wireless LANs supported... # The matching is done on the first 3 bytes of the MAC address # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="Wavelan Network" MODE="Managed" #RATE="auto" KEY="s:secu1" # To set all four keys, use : # KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]" # For the RG 1000 Residential Gateway: The ESSID is the identifier on # the unit, and the default key is the last 5 digits of the same. # ESSID="084d70" # KEY="s:84d70" ;; - Now the only thing I need to do is change the ESSID="mycurrentssid" I don't run encryption at home...but when onsite with a client, I use the iwconfig command. But you see there is some comments on the RG 1000. Maybe you don't see that because you are using an older version??? So now I'm about to reinstall woody. I'm wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? That is way overkill. But if you are a newbie...then go for it. It is good practice learning the installer. I did it many, many times learning Debian. Now I can fix just about anything that breaks. (knock on wood) The kernel is another can of worms. If you study this page hard, and keep learning how to do the kernel, it becomes very easy using the kernel-package system. Very easy. http://newbiedoc.sourceforge.net/system/kernel-pkg.html I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim If you are brave, and this is just a practice machine, maybe you can try jumping right up to unstable. Good luck. Andy
Re: wireless network problems
The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. Nate Duehr wrote: On Tuesday 23 December 2003 11:54 am, Tim Folger wrote: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. Just as a side-note, Orinoco recently changed chipsets to one that currently does not have a Linux driver (without warning) from some reading I was doing on the web. How new is that Orinoco card? The old Gold and Silver cards do fine... if it's not one made recently... it should work okay.
Re: wireless network problems
Hey Andy, Thanks again for all the pointers. I'll definitely study that newbie page at sourceforge. I did notice the information in wireless.opts about the RG-1000, and entered the correct essid. Maybe I'll try turning encryption off and see if that helps. Just before KDE failed I had also edited /etc/pcmcia/network.opts, entering "y" for dhcp. I wonder if that could have caused some kind of conflict? Maybe I should just stick with entering my network information in wireless.opts? I guess I should probably stick with stable until I know what I'm doing. Happy holidays, Tim Andy Firman wrote: On Tue, Dec 23, 2003 at 11:54:31AM -0700, Tim Folger wrote: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. No advice on that issue. Read the RG-1000 manual carefully. There are two ways to do the keys...alphanumeric and hex. I have always used the silver card. Not sure if that is an issue. And I am running Debian unstable just so you know... If it is brand new, it might be a newer chipset like Nate mentioned in another post. Try doing this command: "cardctl ident" This is what I get: [EMAIL PROTECTED]:~$ sudo cardctl ident Socket 0: no product info available Socket 1: product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", "" manfid: 0x0156, 0x0002 function: 6 (network) I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. Bummer. It should not have an effect on your desktop environment. I wonder what you did? The only section in wireless.opts that you need to mess with is this: (and by the way...do you see this in your wireless.opts???) - # Here are a few examples with a few Wireless LANs supported... # The matching is done on the first 3 bytes of the MAC address # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="Wavelan Network" MODE="Managed" #RATE="auto" KEY="s:secu1" # To set all four keys, use : # KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]" # For the RG 1000 Residential Gateway: The ESSID is the identifier on # the unit, and the default key is the last 5 digits of the same. # ESSID="084d70" # KEY="s:84d70" ;; - Now the only thing I need to do is change the ESSID="mycurrentssid" I don't run encryption at home...but when onsite with a client, I use the iwconfig command. But you see there is some comments on the RG 1000. Maybe you don't see that because you are using an older version??? So now I'm about to reinstall woody. I'm wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? That is way overkill. But if you are a newbie...then go for it. It is good practice learning the installer. I did it many, many times learning Debian. Now I can fix just about anything that breaks. (knock on wood) The kernel is another can of worms. If you study this page hard, and keep learning how to do the kernel, it becomes very easy using the kernel-package system. Very easy. http://newbiedoc.sourceforge.net/system/kernel-pkg.html I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim If you are brave, and this is just a practice machine, maybe you can try jumping right up to unstable. Good luck. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
The orinoco gold card is about a year old now, and it worked with Xandros, a commercial distro based on debian woody. Nate Duehr wrote: On Tuesday 23 December 2003 11:54 am, Tim Folger wrote: Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. Just as a side-note, Orinoco recently changed chipsets to one that currently does not have a Linux driver (without warning) from some reading I was doing on the web. How new is that Orinoco card? The old Gold and Silver cards do fine... if it's not one made recently... it should work okay. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Tue, Dec 23, 2003 at 11:54:31AM -0700, Tim Folger wrote: > > Hi Andy, > > Thanks for your advice. My Orinoco gold card uses128-bit encryption, but > a wireless gateway I use (called the RG-1000, manufactured by Lucent) > specifies a five-character-long alphanumeric key for both computers on > my home network. So I'm not sure how I would go about converting that > to a 26-character key. If you have any advice I'd appreciate it. No advice on that issue. Read the RG-1000 manual carefully. There are two ways to do the keys...alphanumeric and hex. I have always used the silver card. Not sure if that is an issue. And I am running Debian unstable just so you know... If it is brand new, it might be a newer chipset like Nate mentioned in another post. Try doing this command: "cardctl ident" This is what I get: [EMAIL PROTECTED]:~$ sudo cardctl ident Socket 0: no product info available Socket 1: product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", "" manfid: 0x0156, 0x0002 function: 6 (network) > > I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, > but I must have messed something up: my card seemed to work--it lit > up--but KDE refused to load. Bummer. It should not have an effect on your desktop environment. I wonder what you did? The only section in wireless.opts that you need to mess with is this: (and by the way...do you see this in your wireless.opts???) - # Here are a few examples with a few Wireless LANs supported... # The matching is done on the first 3 bytes of the MAC address # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="Wavelan Network" MODE="Managed" #RATE="auto" KEY="s:secu1" # To set all four keys, use : # KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]" # For the RG 1000 Residential Gateway: The ESSID is the identifier on # the unit, and the default key is the last 5 digits of the same. # ESSID="084d70" # KEY="s:84d70" ;; - Now the only thing I need to do is change the ESSID="mycurrentssid" I don't run encryption at home...but when onsite with a client, I use the iwconfig command. But you see there is some comments on the RG 1000. Maybe you don't see that because you are using an older version??? > So now I'm about to reinstall woody. I'm > wondering if it would be worthwhile to do a very minimal installation, > and then upgrade to sarge or sid (using my painfully slow dial-up > connection)? Would a dist-upgrade also upgrade the kernel? That is way overkill. But if you are a newbie...then go for it. It is good practice learning the installer. I did it many, many times learning Debian. Now I can fix just about anything that breaks. (knock on wood) The kernel is another can of worms. If you study this page hard, and keep learning how to do the kernel, it becomes very easy using the kernel-package system. Very easy. http://newbiedoc.sourceforge.net/system/kernel-pkg.html > I can't do lsmod right now because I'm (arrgh) using Windows, but I > think during installation I installed the hermes and orinoco modules. > > I notice that in your /etc/network/interfaces file you have "auto eth1." > I thought I had read somewhere that including that line would interfere > with the pcmcia module, so I didn't' include it in my file. > Tim If you are brave, and this is just a practice machine, maybe you can try jumping right up to unstable. Good luck. Andy
Re: wireless network problems
On Tuesday 23 December 2003 11:54 am, Tim Folger wrote: > Hi Andy, > > Thanks for your advice. My Orinoco gold card uses128-bit encryption, > but a wireless gateway I use (called the RG-1000, manufactured by > Lucent) specifies a five-character-long alphanumeric key for both > computers on my home network. So I'm not sure how I would go about > converting that to a 26-character key. If you have any advice I'd > appreciate it. Just as a side-note, Orinoco recently changed chipsets to one that currently does not have a Linux driver (without warning) from some reading I was doing on the web. How new is that Orinoco card? The old Gold and Silver cards do fine... if it's not one made recently... it should work okay. -- Nate Duehr, [EMAIL PROTECTED]
Re: wireless network problems
On Tue, Dec 23, 2003 at 11:54:31AM -0700, Tim Folger wrote: > > Hi Andy, > > Thanks for your advice. My Orinoco gold card uses128-bit encryption, but > a wireless gateway I use (called the RG-1000, manufactured by Lucent) > specifies a five-character-long alphanumeric key for both computers on > my home network. So I'm not sure how I would go about converting that > to a 26-character key. If you have any advice I'd appreciate it. No advice on that issue. Read the RG-1000 manual carefully. There are two ways to do the keys...alphanumeric and hex. I have always used the silver card. Not sure if that is an issue. And I am running Debian unstable just so you know... If it is brand new, it might be a newer chipset like Nate mentioned in another post. Try doing this command: "cardctl ident" This is what I get: [EMAIL PROTECTED]:~$ sudo cardctl ident Socket 0: no product info available Socket 1: product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", "" manfid: 0x0156, 0x0002 function: 6 (network) > > I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, > but I must have messed something up: my card seemed to work--it lit > up--but KDE refused to load. Bummer. It should not have an effect on your desktop environment. I wonder what you did? The only section in wireless.opts that you need to mess with is this: (and by the way...do you see this in your wireless.opts???) - # Here are a few examples with a few Wireless LANs supported... # The matching is done on the first 3 bytes of the MAC address # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="Wavelan Network" MODE="Managed" #RATE="auto" KEY="s:secu1" # To set all four keys, use : # KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]" # For the RG 1000 Residential Gateway: The ESSID is the identifier on # the unit, and the default key is the last 5 digits of the same. # ESSID="084d70" # KEY="s:84d70" ;; - Now the only thing I need to do is change the ESSID="mycurrentssid" I don't run encryption at home...but when onsite with a client, I use the iwconfig command. But you see there is some comments on the RG 1000. Maybe you don't see that because you are using an older version??? > So now I'm about to reinstall woody. I'm > wondering if it would be worthwhile to do a very minimal installation, > and then upgrade to sarge or sid (using my painfully slow dial-up > connection)? Would a dist-upgrade also upgrade the kernel? That is way overkill. But if you are a newbie...then go for it. It is good practice learning the installer. I did it many, many times learning Debian. Now I can fix just about anything that breaks. (knock on wood) The kernel is another can of worms. If you study this page hard, and keep learning how to do the kernel, it becomes very easy using the kernel-package system. Very easy. http://newbiedoc.sourceforge.net/system/kernel-pkg.html > I can't do lsmod right now because I'm (arrgh) using Windows, but I > think during installation I installed the hermes and orinoco modules. > > I notice that in your /etc/network/interfaces file you have "auto eth1." > I thought I had read somewhere that including that line would interfere > with the pcmcia module, so I didn't' include it in my file. > Tim If you are brave, and this is just a practice machine, maybe you can try jumping right up to unstable. Good luck. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
On Tuesday 23 December 2003 11:54 am, Tim Folger wrote: > Hi Andy, > > Thanks for your advice. My Orinoco gold card uses128-bit encryption, > but a wireless gateway I use (called the RG-1000, manufactured by > Lucent) specifies a five-character-long alphanumeric key for both > computers on my home network. So I'm not sure how I would go about > converting that to a 26-character key. If you have any advice I'd > appreciate it. Just as a side-note, Orinoco recently changed chipsets to one that currently does not have a Linux driver (without warning) from some reading I was doing on the web. How new is that Orinoco card? The old Gold and Silver cards do fine... if it's not one made recently... it should work okay. -- Nate Duehr, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Ben, Thanks for the advice. As you can see from another post I just made to this list, I'm about to reinstall woody (probably this weekend.) When I'm up and running again I'll try your suggestion. Yes, I am connected to a hub--a wireless gateway made by Lucent called the RG-1000, which acts as a dhcp server, which is why I chose "managed" mode. I wonder if "auto" mode might work? Tim [EMAIL PROTECTED] wrote: Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc I beg to differ! I am using a pcmcia card in my asusand mys settings are all in /etc/network/interfaces -works fine for me! I presume you are connecting to a hub thus the managed network? try iwpriv eth1 force_reset to reset the card perhaps... Ben.
Re: wireless network problems
Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. So now I'm about to reinstall woody. I'm wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim Andy Firman wrote: Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? I have the same card. Are you using 40 or 128 bit encryption? Have you tried setting encryption manually? Such as: ~$ iwconfig eth1 enc 01234567890123456789123456 (for 128 bit encryption there are 26 characters needed and for the 40 bit encryption there are 10 characters needed...I think... so if you are using only 5 characters...that may be the problem) Also, have you played around with /etc/pcmcia/wireless.opts ? I don't use the interfaces file for the wireless settings like you do. All my configuration in in wireless.opts and the only thing in my interfaces file is this: auto eth1 iface eth1 inet dhcp One other thing, I remember vaguely having trouble with the bf24 kernel and wireless. Maybe you can try to do a custom kernel? Also what do you have for modules? This is what I have when I do lsmod: orinoco_cs 4724 1 orinoco37140 0 [orinoco_cs] hermes 6020 0 [orinoco_cs orinoco] Hope this gets you started in the right direction. Andy
Re: wireless network problems
Hi Ben, Thanks for the advice. As you can see from another post I just made to this list, I'm about to reinstall woody (probably this weekend.) When I'm up and running again I'll try your suggestion. Yes, I am connected to a hub--a wireless gateway made by Lucent called the RG-1000, which acts as a dhcp server, which is why I chose "managed" mode. I wonder if "auto" mode might work? Tim [EMAIL PROTECTED] wrote: Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc I beg to differ! I am using a pcmcia card in my asusand mys settings are all in /etc/network/interfaces -works fine for me! I presume you are connecting to a hub thus the managed network? try iwpriv eth1 force_reset to reset the card perhaps... Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Hi Andy, Thanks for your advice. My Orinoco gold card uses128-bit encryption, but a wireless gateway I use (called the RG-1000, manufactured by Lucent) specifies a five-character-long alphanumeric key for both computers on my home network. So I'm not sure how I would go about converting that to a 26-character key. If you have any advice I'd appreciate it. I also tried entering my wireless settings in /etc/pcmcia/wireless.opts, but I must have messed something up: my card seemed to work--it lit up--but KDE refused to load. So now I'm about to reinstall woody. I'm wondering if it would be worthwhile to do a very minimal installation, and then upgrade to sarge or sid (using my painfully slow dial-up connection)? Would a dist-upgrade also upgrade the kernel? I can't do lsmod right now because I'm (arrgh) using Windows, but I think during installation I installed the hermes and orinoco modules. I notice that in your /etc/network/interfaces file you have "auto eth1." I thought I had read somewhere that including that line would interfere with the pcmcia module, so I didn't' include it in my file. Tim Andy Firman wrote: Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? I have the same card. Are you using 40 or 128 bit encryption? Have you tried setting encryption manually? Such as: ~$ iwconfig eth1 enc 01234567890123456789123456 (for 128 bit encryption there are 26 characters needed and for the 40 bit encryption there are 10 characters needed...I think... so if you are using only 5 characters...that may be the problem) Also, have you played around with /etc/pcmcia/wireless.opts ? I don't use the interfaces file for the wireless settings like you do. All my configuration in in wireless.opts and the only thing in my interfaces file is this: auto eth1 iface eth1 inet dhcp One other thing, I remember vaguely having trouble with the bf24 kernel and wireless. Maybe you can try to do a custom kernel? Also what do you have for modules? This is what I have when I do lsmod: orinoco_cs 4724 1 orinoco37140 0 [orinoco_cs] hermes 6020 0 [orinoco_cs orinoco] Hope this gets you started in the right direction. Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc I beg to differ! I am using a pcmcia card in my asusand mys settings are all in /etc/network/interfaces -works fine for me! I presume you are connecting to a hub thus the managed network? try iwpriv eth1 force_reset to reset the card perhaps... Ben.
Re: wireless network problems
Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc I beg to differ! I am using a pcmcia card in my asusand mys settings are all in /etc/network/interfaces -works fine for me! I presume you are connecting to a hub thus the managed network? try iwpriv eth1 force_reset to reset the card perhaps... Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: > On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: > > I'm relatively new to Linux, and have installed debian woody with the > > bf2.4 kernel. I'm having trouble getting my orinoco wireless card to > > work. The card beeps during startup, and its green light flickers, but > > doesn't stay on. When I run iwconfig eth1 the output gives the correct > > essid and nickname, but says that the encryption key is turned off, even > > though I've specified a key in /etc/network/interfaces. Here's what > > I've entered in /etc/network/interfaces: > > > > iface eth1 inet dhcp > > wireless_essid (my network name) > > wireless_mode managed > > wireless_key (a combination of five numbers and letters) > > wireless_nick (computer's nickname) > > wireless_channel 10 > > > > Is there another parameter I need to enter to turn on wireless > > encryption? Or am I missing something else? > > I have the same card. > Are you using 40 or 128 bit encryption? > > Have you tried setting encryption manually? > > Such as: > ~$ iwconfig eth1 enc 01234567890123456789123456 > > (for 128 bit encryption there are 26 characters needed and for > the 40 bit encryption there are 10 characters needed...I think... > so if you are using only 5 characters...that may be the problem) > > Also, have you played around with /etc/pcmcia/wireless.opts ? > I don't use the interfaces file for the wireless settings > like you do. All my configuration in in wireless.opts > and the only thing in my interfaces file is this: > > auto eth1 > iface eth1 inet dhcp > > One other thing, I remember vaguely having trouble with the > bf24 kernel and wireless. Maybe you can try to do a custom kernel? > > Also what do you have for modules? > > This is what I have when I do lsmod: > > orinoco_cs 4724 1 > orinoco37140 0 [orinoco_cs] > hermes 6020 0 [orinoco_cs orinoco] > > Hope this gets you started in the right direction. > > Andy
Re: wireless network problems
Damn...just realized I sent this to debian-user by mistake on Sunday. See below for my response to your question. Sorry for the lateness On Sun, Dec 21, 2003 at 12:56:55PM -0500, wrote: > On Sat, Dec 20, 2003 at 07:54:54PM -0700, Tim Folger wrote: > > I'm relatively new to Linux, and have installed debian woody with the > > bf2.4 kernel. I'm having trouble getting my orinoco wireless card to > > work. The card beeps during startup, and its green light flickers, but > > doesn't stay on. When I run iwconfig eth1 the output gives the correct > > essid and nickname, but says that the encryption key is turned off, even > > though I've specified a key in /etc/network/interfaces. Here's what > > I've entered in /etc/network/interfaces: > > > > iface eth1 inet dhcp > > wireless_essid (my network name) > > wireless_mode managed > > wireless_key (a combination of five numbers and letters) > > wireless_nick (computer's nickname) > > wireless_channel 10 > > > > Is there another parameter I need to enter to turn on wireless > > encryption? Or am I missing something else? > > I have the same card. > Are you using 40 or 128 bit encryption? > > Have you tried setting encryption manually? > > Such as: > ~$ iwconfig eth1 enc 01234567890123456789123456 > > (for 128 bit encryption there are 26 characters needed and for > the 40 bit encryption there are 10 characters needed...I think... > so if you are using only 5 characters...that may be the problem) > > Also, have you played around with /etc/pcmcia/wireless.opts ? > I don't use the interfaces file for the wireless settings > like you do. All my configuration in in wireless.opts > and the only thing in my interfaces file is this: > > auto eth1 > iface eth1 inet dhcp > > One other thing, I remember vaguely having trouble with the > bf24 kernel and wireless. Maybe you can try to do a custom kernel? > > Also what do you have for modules? > > This is what I have when I do lsmod: > > orinoco_cs 4724 1 > orinoco37140 0 [orinoco_cs] > hermes 6020 0 [orinoco_cs orinoco] > > Hope this gets you started in the right direction. > > Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Thanks Jeff. I'll give that a shot. Tim Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc
Re: wireless network problems
Thanks Jeff. I'll give that a shot. Tim Jeff wrote: Tim Folger, 2003-Dec-20 19:54 -0700: Hi, I'm relatively new to Linux, and have installed debian woody with the bf2.4 kernel. I'm having trouble getting my orinoco wireless card to work. The card beeps during startup, and its green light flickers, but doesn't stay on. When I run iwconfig eth1 the output gives the correct essid and nickname, but says that the encryption key is turned off, even though I've specified a key in /etc/network/interfaces. Here's what I've entered in /etc/network/interfaces: iface eth1 inet dhcp wireless_essid (my network name) wireless_mode managed wireless_key (a combination of five numbers and letters) wireless_nick (computer's nickname) wireless_channel 10 Is there another parameter I need to enter to turn on wireless encryption? Or am I missing something else? Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wireless network problems
Tim Folger, 2003-Dec-20 19:54 -0700: > Hi, > > I'm relatively new to Linux, and have installed debian woody with the > bf2.4 kernel. I'm having trouble getting my orinoco wireless card to > work. The card beeps during startup, and its green light flickers, but > doesn't stay on. When I run iwconfig eth1 the output gives the correct > essid and nickname, but says that the encryption key is turned off, even > though I've specified a key in /etc/network/interfaces. Here's what > I've entered in /etc/network/interfaces: > > iface eth1 inet dhcp > wireless_essid (my network name) > wireless_mode managed > wireless_key (a combination of five numbers and letters) > wireless_nick (computer's nickname) > wireless_channel 10 > > Is there another parameter I need to enter to turn on wireless > encryption? Or am I missing something else? > > Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: wireless network problems
Tim Folger, 2003-Dec-20 19:54 -0700: > Hi, > > I'm relatively new to Linux, and have installed debian woody with the > bf2.4 kernel. I'm having trouble getting my orinoco wireless card to > work. The card beeps during startup, and its green light flickers, but > doesn't stay on. When I run iwconfig eth1 the output gives the correct > essid and nickname, but says that the encryption key is turned off, even > though I've specified a key in /etc/network/interfaces. Here's what > I've entered in /etc/network/interfaces: > > iface eth1 inet dhcp > wireless_essid (my network name) > wireless_mode managed > wireless_key (a combination of five numbers and letters) > wireless_nick (computer's nickname) > wireless_channel 10 > > Is there another parameter I need to enter to turn on wireless > encryption? Or am I missing something else? > > Thanks in advance for any ideas. If this is a PCMCIA card, then you have to specify these parameters in /etc/pcmcia/wireless.opts. Those settings in /etc/network/interfaces is for ISA/PCI based cards. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
