ONBOOT='yes' BOOTPROTO='dhcp' BROADCAST='' IPADDR='' MTU='' NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='JNkJ.x2u1_foDyv7' USERCONTROL='yes' WIRELESS_AP='2WIRE783' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='6' WIRELESS_CLIENT_CERT='' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='2WIRE782' WIRELESS_FREQUENCY='' WIRELESS_KEY='open' WIRELESS_KEY_0='h:8956231064' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:03.0'
Assuming that the above information is correct, try typing the following as root: iwconfig essid 2WIRE783 mode managed enc 8956231064 power off dhcpcd eth1 (replace eth1 with whatever adapter your wireless is using) If that works than we're really close and I think we can get you working pretty easy. The are a couple of errors in the above config, but the commands I gave you will bypass and let us know that the card is working, which I think it is. ;) Cheers, Daniel
Daniel Hatfield wrote:
ONBOOT='yes' BOOTPROTO='dhcp' BROADCAST='' IPADDR='' MTU='' NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='JNkJ.x2u1_foDyv7' USERCONTROL='yes' WIRELESS_AP='2WIRE783' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='6' WIRELESS_CLIENT_CERT='' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='2WIRE782' WIRELESS_FREQUENCY='' WIRELESS_KEY='open' WIRELESS_KEY_0='h:8956231064' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:03.0'
Assuming that the above information is correct, try typing the following as root:
iwconfig essid 2WIRE783 mode managed enc 8956231064 power off
dhcpcd eth1 (replace eth1 with whatever adapter your wireless is using)
If that works than we're really close and I think we can get you working pretty easy. The are a couple of errors in the above config, but the commands I gave you will bypass and let us know that the card is working, which I think it is. ;)
Cheers, Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Daniel, If I type in the command I get the below error. iwconfig essid 2WIRE783 mode managed enc 8956231064 power off Error: unreconized wireless request "2WIRE783" If I change "any" with "2WIRE783" Error: unreconized wireless request "any" Are we typing the command in correctly? Jim
jim wrote:
iwconfig essid 2WIRE783 mode managed enc 8956231064 power off Error: unreconized wireless request "2WIRE783"
If I change "any" with "2WIRE783"
Error: unreconized wireless request "any"
Are we typing the command in correctly?
You are missing the device name iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 power off ^^^^ -- Guðlaugur Jóhannesson http://www.hi.is/~gudlaugu Tel: 849 8405
Guðlaugur Jóhannesson wrote:
jim wrote:
iwconfig essid 2WIRE783 mode managed enc 8956231064 power off Error: unreconized wireless request "2WIRE783"
If I change "any" with "2WIRE783"
Error: unreconized wireless request "any"
Are we typing the command in correctly?
You are missing the device name iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 power off ^^^^
Thank you for the correction. I ran that command and the wireless card still won't connect jim
jim wrote:
Guðlaugur Jóhannesson wrote:
You are missing the device name iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 power off ^^^^ Thank you for the correction. I ran that command and the wireless card still won't connect
Try to add "open" after the network key iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 open power off -- Guðlaugur Jóhannesson http://www.hi.is/~gudlaugu Phone: +354 849 8405
Guðlaugur Jóhannesson wrote:
jim wrote:
Guðlaugur Jóhannesson wrote:
You are missing the device name iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 power off ^^^^
Thank you for the correction. I ran that command and the wireless card still won't connect
Try to add "open" after the network key iwconfig eth? essid 2WIRE783 mode managed enc 8956231064 open power off
Adding 'open' did the job but getting /etc/sysconfig/network/ifcfg-wlan setup properly seems to be a problem. I can get on the internet when I run the above command line. I deleted the /etc/sysconfig/network/ifcfg-wlan to regenerate a new one through Yast but yast won't let me, because it say's Error: Hardware configuration bus-pci-0000:02:03.0 already exist Choose a different one , I can't go any further inYast to generate a new /etc/sysconfig/network/ifcfg-wlan file. There has got to be another file in Suse that helps generate ifcfg-wlan where is it. Because the old settings keep coming up in Yast . Oh! How I do miss how simple is was to setup ipw2100 in Fedora4 , I could erase the ifcfg-wlan file regenerate it in the Network Gui. Thanks Guy jim
jim wrote:
Adding 'open' did the job but getting /etc/sysconfig/network/ifcfg-wlan setup properly seems to be a problem. I can get on the internet when I run the above command line. I deleted the /etc/sysconfig/network/ifcfg-wlan to regenerate a new one through Yast but yast won't let me, because it say's Error: Hardware configuration bus-pci-0000:02:03.0 already exist Choose a different one , I can't go any further inYast to generate a new /etc/sysconfig/network/ifcfg-wlan file.
Here is my config file adopted to your parameters. You could try that BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter' UNIQUE='JNkJ.x2u1_foDyv7' USERCONTROL='yes' WIRELESS_AP='2WIRE783' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CHANNEL='6' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='2WIRE782' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='8956231064 open' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:03.0'
There has got to be another file in Suse that helps generate ifcfg-wlan where is it. Because the old settings keep coming up in Yast .
Have you looked at ifcfg-eth-bus-pci-0000:02:03.0 ? Just a guess -- Guðlaugur Jóhannesson http://www.hi.is/~gudlaugu Phone: +354 849 8405
Guðlaugur Jóhannesson wrote:
jim wrote:
Adding 'open' did the job but getting /etc/sysconfig/network/ifcfg-wlan setup properly seems to be a problem. I can get on the internet when I run the above command line. I deleted the /etc/sysconfig/network/ifcfg-wlan to regenerate a new one through Yast but yast won't let me, because it say's Error: Hardware configuration bus-pci-0000:02:03.0 already exist Choose a different one , I can't go any further inYast to generate a new /etc/sysconfig/network/ifcfg-wlan file.
Here is my config file adopted to your parameters. You could try that
BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter' UNIQUE='JNkJ.x2u1_foDyv7' USERCONTROL='yes' WIRELESS_AP='2WIRE783' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CHANNEL='6' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='2WIRE782' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='8956231064 open' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:03.0'
There has got to be another file in Suse that helps generate ifcfg-wlan where is it. Because the old settings keep coming up in Yast .
Have you looked at ifcfg-eth-bus-pci-0000:02:03.0 ? Just a guess
ifcfg-eth-bus-pci-0000:02:03.0 file doesn't exist on my laptop Thank you for the ifcfg-wlan file. Jim
Guðlaugur Jóhannesson wrote:
jim wrote:
Adding 'open' did the job but getting /etc/sysconfig/network/ifcfg-wlan setup properly seems to be a problem. I can get on the internet when I run the above command line. I deleted the /etc/sysconfig/network/ifcfg-wlan to regenerate a new one through Yast but yast won't let me, because it say's Error: Hardware configuration bus-pci-0000:02:03.0 already exist Choose a different one , I can't go any further inYast to generate a new /etc/sysconfig/network/ifcfg-wlan file.
Here is my config file adopted to your parameters. You could try that
BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter' UNIQUE='JNkJ.x2u1_foDyv7' USERCONTROL='yes' WIRELESS_AP='2WIRE783' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CHANNEL='6' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='2WIRE782' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='8956231064 open' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:03.0'
There has got to be another file in Suse that helps generate ifcfg-wlan where is it. Because the old settings keep coming up in Yast .
Have you looked at ifcfg-eth-bus-pci-0000:02:03.0 ? Just a guess
It wouldn't accept the encryption key until you removed the 'open', then yast would accept the key number but as ASCII. Well where back to square one, for some reason the command line , command won't connect the card anymore "Network Unreachable" Thanks very much for your help. Jim-
On Friday 21 October 2005 02:17, jim wrote:
It wouldn't accept the encryption key until you removed the 'open', then yast would accept the key number but as ASCII. Well where back to square one, for some reason the command line , command won't connect the card anymore "Network Unreachable"
When I use a Netgear MA521 with SUSE 9.3 (via ndiswrapper), it gets set up with security mode open, but will only work (ie show a green connection light) if that is changed to restricted: iwconfig wlan0 key restricted s:[ASCII_key] Apologies if this is way off-beam. -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - Meddalwedd Rhydd yn Gymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD
Kevin Donnelly wrote:
On Friday 21 October 2005 02:17, jim wrote:
It wouldn't accept the encryption key until you removed the 'open', then yast would accept the key number but as ASCII. Well where back to square one, for some reason the command line , command won't connect the card anymore "Network Unreachable"
When I use a Netgear MA521 with SUSE 9.3 (via ndiswrapper), it gets set up with security mode open, but will only work (ie show a green connection light) if that is changed to restricted: iwconfig wlan0 key restricted s:[ASCII_key]
Apologies if this is way off-beam.
Thanks for your help Kenny, but that comes up with a error: SET failed on device eth0 ; Operation not supported. If I use wlan0 instead of eth0 I get the error: No such device. It is so weird as to why this seems to be a problem in Suse and not Fedora4. Thanks Jim
FWIW :: had similar problems on a dv1000 laptop. In the end I had to rename wlan0 to eth1 manually ( Yast didn't seem able to name anything anything that would work ) then I instaled netgo for switching between work and home ( static at work dhcp at home ) and all has been fine since.
Francesco Scaglioni wrote:
FWIW :: had similar problems on a dv1000 laptop. In the end I had to rename wlan0 to eth1 manually
How do I do this ? because I have to re configure the NIC's at every boot they have changed themselves .... now eth0 is the wireless card .. And a weird thing .... after yesterday I got it all working at startup this morning I had to spend 1 hour trying to connect again to the AP .... and I've seen that even if I set YaST to manual IP address to the wlan card, it showed always the dhcp option enabled. i had to manually change ifcfg-wlan-id-00\:04\:23\:5a\:3c\:f1 to static to get the card work .... it's driving me insane... -- .~. Nicola -=KOOLINUS=- Losito /v\ http://www.koolinus.net // \\ /( )\ Linux Registered User #293182 ^^ ^^ icq:62837984 * Jabber-ID:koolinus@jabber.linux.it
I just renamed the wirelss config file in /etc/sysconfig/network to ifcfg-eth-eht1. Then I use the netgo software to switch between sites. Set both NICs to manual start then netgo will switch between dhcp wlan at home and fixed ip on cat5 at work. HTH F
On Thu, 2005-10-27 at 10:49 +0100, Francesco Scaglioni wrote:
I just renamed the wirelss config file in /etc/sysconfig/network to ifcfg-eth-eht1. Then I use the netgo software to switch between sites. Set both NICs to manual start then netgo will switch between dhcp wlan at home and fixed ip on cat5 at work.
Speaking of NetGo will this package be included in future releases? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Sounds similar to the problem that I had. on a dv1000 laptop. IN the end I had to manually rename wlan0 to eth1 ( YaST didn't seem able to name anything toanything that worked ) then installed netgo for switching between profiles ( dhcp at home, static at work ) and all has been fine since.
participants (7)
-
Daniel Hatfield -
Francesco Scaglioni -
Guðlaugur Jóhannesson -
jim -
Ken Schneider -
Kevin Donnelly -
Nicola -kOoLiNuS- Losito