Attachment 56240 Details for Bug 131503

Discussion on the Suse mailing list

wireless.txt (text/plain), 28.34 KB, created by o-Dzin Tridral on 2005-11-02 11:32:07 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: o-Dzin Tridral

Created: 2005-11-02 11:32:07 UTC

Size: 28.34 KB

patch

obsolete

>Google Mail 	* 'o-Dzin Tridral <tridral@gmail.com> *
>
>------------------------------------------------------------------------
>*Wireless ... again*
>12 messages
>------------------------------------------------------------------------
>* 'o-Dzin Tridral <tridral@gmail.com> * 	* 27 October 2005 21:51 *
>To: suse-linux-e@suse.com, opensuse@opensuse.org
>Dear all,
>
>I've read (and been part of) a number of threads of discussion relating
>to automatically starting the wireless connection on boot.  A fair
>number of people seem to have this problem, and thesymptoms seem to be
>the same - the system recognises that there's a wrieles card but doesn't
>properly bring up the interface.  The only way to get this running is to
>take some action - ifdown/ifup, Yast or NetGo. There seems to be no
>certain solution (that I've seen)  to get the interface to start
>automatically.  (I couldn't even get 'static' to work - but that might
>just be me!)
>
>I'm entirely new to Suse.  Is this a known bug? is there a
>workaround/solution? Did Suse behave like this in earlier versions?
>
>(Failing all else, is there a way to put ifdown/ifup at the end of the
>boot process?  Would that help?)
>
>Thanks for any help and advice (and for all the help and advice already
>given).
>
>best regards,
>
>'o-Dzin
>
>
>
>
>------------------------------------------------------------------------
>* ken <gebser@speakeasy.net> * 	* 28 October 2005 09:07 *
>Reply-To: gebser@speakeasy.net
>To: opensuse@opensuse.org, suse-linux-e@suse.com
>'o-Dzin Tridral wrote:
>> Dear all,
>>
>> I've read (and been part of) a number of threads of discussion relating to
>> automatically starting the wireless connection on boot. A fair number of
>> people seem to have this problem, and thesymptoms seem to be the same
>- the
>> system recognises that there's a wrieles card but doesn't properly
>bring up
>> the interface. The only way to get this running is to take some action -
>> ifdown/ifup, Yast or NetGo. There seems to be no certain solution
>(that I've
>> seen) to get the interface to start automatically. (I couldn't even get
>> 'static' to work - but that might just be me!)
>>
>> I'm entirely new to Suse. Is this a known bug? is there a
>> workaround/solution? Did Suse behave like this in earlier versions?
>>
>> (Failing all else, is there a way to put ifdown/ifup at the end of the
>boot
>> process? Would that help?)
>>
>> ....
>
>I would think that ifup and ifdown are already being run on boot and
>shutdown respectively.  I wouldn't add them in anywhere until I found
>out whether or not this was the case.
>
>Perhaps more importantly, when asking for help, provide some information
>about the problem, the hardware and software used, what you've tried and
>what happened, what error messages resulted, what log files you examined
>and what you found or didn't find there, and so on.
>
>hth,
>ken
>
>--
>Check the headers for your unsubscription address
>For additional commands send e-mail to suse-linux-e-help@suse.com
><mailto:suse-linux-e-help@suse.com>
>Also check the archives at http://lists.suse.com
>Please read the FAQs: suse-linux-e-faq@suse.com
><mailto:suse-linux-e-faq@suse.com>
>
>
>------------------------------------------------------------------------
>* 'o-Dzin Tridral <tridral@gmail.com> * 	* 28 October 2005 17:11 *
>To: opensuse@opensuse.org, suse-linux-e@suse.com
>
>
>On 28/10/05, *ken* <gebser@speakeasy.net <mailto:gebser@speakeasy.net>>
>wrote:
>
>
>
>    I would think that ifup and ifdown are already being run on boot and
>    shutdown respectively.  I wouldn't add them in anywhere until I found
>    out whether or not this was the case.
>
>    Perhaps more importantly, when asking for help, provide some
>    information
>    about the problem, the hardware and software used, what you've tried and
>    what happened, what error messages resulted, what log files you examined
>    and what you found or didn't find there, and so on.
>
>    hth,
>    ken
>
>
>
>Thank you for taking the time to reply.  The details are below.  I'd be
>grateful if anyone could point me at a solution!
>
>many thanks,
>
>'o-Dzin
>
>In summary
>1. Installed Suse 10.0 and ipw-firmware
>2. Tried NetGo
>3. Renamed ifcfg-wlan-id-00:12:f0:73:7d:a7 to be ifcfg-eth1
>4. The whole story from booting to getting the network up
>5. Posted the contents of  /etc/sysconfig/network
>6. Tried calling the ifcfg file ifcgfg-wlan0
>
>
>In detail
>
>1. Installed Suse 10.0 and ipw-firmware
>
>(ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/ipw-firmware-5-6.noarch.rpm
><ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/ipw-firmware-5-6.noarch.rpm>)
>configured the 2200 via Yast.
>
>Found that I needed to  carry out the configuration again after each
>reboot. 
>
>
>2. Tried NetGo
>
>Although this was a useful way of starting the wireless interface it
>didn't start it on boot.
>(http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo
><http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo>)
>
>
>3. Renamed ifcfg-wlan-id-00:12:f0:73:7d:a7 to be ifcfg-eth1
>
>Noted: The system 'thinks' the interface is up - that's what it tells me
>if I try 'ifup eth1'.  Instead if I say
>'ifdown eth1' first, followed by 'ifup eth1' everything comes up fine.
>
>
>4. The whole story from booting to getting the network up
>
>boot
>
>----------
>
>iwconfig
>eth1      IEEE 802.11g  ESSID:"xxxxxx"
>          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:06:25:FF:C6:89
>          Bit Rate=54 Mb/s   Tx-Power=20 dBm
>          Retry limit:7   RTS thr:off   Fragment thr:off
>          Encryption key:off
>          Power Management:off
>          Link Quality=79/100  Signal level=-50 dBm  Noise level=-83 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:4
>
>ifconfig
>eth1      Link encap:Ethernet  HWaddr 00:12:F0:73:7D:A7
>          inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link
>          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:68 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:1 errors:0 dropped:15 overruns:0 carrier:1
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>          Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff
>
>----------
>
>Most things ok, but no IP address
>Can't browse, etc.
>Try to bring up the interface
>The system things it's already running
>
>----------
>
>ifup eth1
>    eth1      device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>    eth1      configuration: wlan-id-00:12:f0:73:7d:a7
>    eth1      warning: wpa_supplicant already running on interface
>DHCP client is already running on eth1
>
>----------
>
>Take the interface down
>
>----------
>
>ifdown eth1
>    eth1      device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>    eth1      configuration: wlan-id-00:12:f0:73:7d:a7
>
>----------
>
>iwconfig unchanged
>ifconfig gone
>
>----------
>
>iwconfig
>eth1      IEEE 802.11g  ESSID:"xxxxxx"
>          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:06:25:FF:C6:89
>          Bit Rate=54 Mb/s   Tx-Power=20 dBm
>          Retry limit:7   RTS thr:off   Fragment thr:off
>          Encryption key:off
>          Power Management:off
>          Link Quality=80/100  Signal level=-49 dBm  Noise level=-84 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:3
>
>ifconfig
>(no eth1)
>
>----------
>
>Bring up the wireless interface
>
>----------
>
>
>ifup eth1
>    eth1      device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>    eth1      configuration: wlan-id-00:12:f0:73:7d:a7
>    eth1      starting wpa_supplicant
>Starting DHCP Client Daemon on eth1... . . . . . IP/Netmask:
>xxx.xxx.xxx.xxx / 255.255.255.0 <http://255.255.255.0>
><http://255.255.255.0>
>
>----------
>
>Everything comes up ok
>
>----------
>
>iwconfig
>eth1      IEEE 802.11g  ESSID:"xxxxxx"
>          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:06:25:FF:C6:89
>          Bit Rate=54 Mb/s   Tx-Power=20 dBm
>          Retry limit:7   RTS thr:off   Fragment thr:off
>          Encryption key:57FA-8FC4-F8   Security mode:open
>          Power Management:off
>          Link Quality=77/100  Signal level=-52 dBm  Noise level=-83 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:1
>
>ifconfig
>eth1      Link encap:Ethernet  HWaddr 00:12:F0:73:7D:A7
>          inet addr:192.168.1.104 <http://192.168.1.104>
><http://192.168.1.104>  Bcast xxxxxx.xxx.xxx  Mask:255.255.255.0
><http://255.255.255.0> <http://255.255.255.0>
>          inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link
>          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:20 errors:0 dropped:18 overruns:0 carrier:1
>          collisions:0 txqueuelen:1000
>          RX bytes:760 (760.0 b)  TX bytes:2157 (2.1 Kb)
>          Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff
>
>----------
>
>Everything ok
>
>----------
>
>
>5. Posted the contents of  /etc/sysconfig/network
>
>drwxr-xr-x  6 root root  368 2005-10-23 22:40 .
>drwxr-xr-x  7 root root 1584 2005-10-19 23:27 ..
>-rw-r--r--  1 root root 6979 2005-09-09 17:15 config
>-rw-r--r--  1 root root 6707 2005-10-19 23:34 dhcp
>-rw-r--r--  1 root root  141 2005-09-09 17:15 ifcfg-lo
>-rw-r--r--  1 root root 5779 2005-09-09 17:15 ifcfg.template
>-rw-------  1 root root  686 2005-10-21 23:36
>ifcfg-wlan-id-00:12:f0:73:7d:a7
>drwxr-xr-x  2 root root   48 2005-09-09 17:27 if-down.d
>-rw-r--r--  1 root root  239 2005-09-09 17:15 ifroute-lo
>drwxr-xr-x  2 root root   88 2005-10-19 22:55 if-up.d
>drwx------  2 root root   48 2005-09-09 17:27 providers
>drwxr-xr-x  2 root root 1336 2005-10-19 22:55 scripts
>-rw-r--r--  1 root root 5469 2005-10-19 22:54 wireless
>
>
>6. Tried calling the ifcfg file ifcgfg-wlan0
>
>I tried calling it ifcfg-wlan0 and the interface didn't come up.  It
>wouldn't come up when I did the down/up thing either.  Then I renamed it
>ifcfg-eth1.  It still wouldn't come up on boot but it would come up if I
>took it down and up again.  So just the same as when it had the long name.
>
>
>------------------------------------------------------------------------
>* David Martin <dmartin@multi-ad.com> * 	* 28 October 2005 19:55 *
>To: 'o-Dzin Tridral <tridral@gmail.com>
>Cc: opensuse@opensuse.org, suse-linux-e@suse.com
>I am having the exact same problem.  Of note, if I disable the
>encryption key and open my wireless network up everything seems to work
>just fine.  It seems to give up quickly on validating my auth key and
>acquiring an IP address.  It's definately a bug.
>
>
>'o-Dzin Tridral wrote:
>
>>On 28/10/05, ken <gebser@speakeasy.net <mailto:gebser@speakeasy.net>>
>wrote:
>>
>>
>>>
>>>I would think that ifup and ifdown are already being run on boot and
>>>shutdown respectively. I wouldn't add them in anywhere until I found
>>>out whether or not this was the case.
>>>
>>>Perhaps more importantly, when asking for help, provide some information
>>>about the problem, the hardware and software used, what you've tried and
>>>what happened, what error messages resulted, what log files you examined
>>>and what you found or didn't find there, and so on.
>>>
>>>hth,
>>>ken
>>>
>>>
>>
>>
>>
>>Thank you for taking the time to reply. The details are below. I'd be
>>grateful if anyone could point me at a solution!
>>
>>many thanks,
>>
>>'o-Dzin
>>
>>In summary
>>1. Installed Suse 10.0 and ipw-firmware
>>2. Tried NetGo
>>3. Renamed ifcfg-wlan-id-00:12:f0:73:7d:a7 to be ifcfg-eth1
>>4. The whole story from booting to getting the network up
>>5. Posted the contents of /etc/sysconfig/network
>>6. Tried calling the ifcfg file ifcgfg-wlan0
>>
>>
>>In detail
>>
>>1. Installed Suse 10.0 and ipw-firmware
>>
>>(
>>ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/ipw-firmware-5-6.noarch.rpm
><ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/ipw-firmware-5-6.noarch.rpm>
>>)
>>configured the 2200 via Yast.
>>
>>Found that I needed to carry out the configuration again after each reboot.
>>
>>
>>2. Tried NetGo
>>
>>Although this was a useful way of starting the wireless interface it didn't
>>start it on boot.
>>(http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo
><http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo>)
>>
>>
>>3. Renamed ifcfg-wlan-id-00:12:f0:73:7d:a7 to be ifcfg-eth1
>>
>>Noted: The system 'thinks' the interface is up - that's what it tells me if
>>I try 'ifup eth1'. Instead if I say
>>'ifdown eth1' first, followed by 'ifup eth1' everything comes up fine.
>>
>>
>>4. The whole story from booting to getting the network up
>>
>>boot
>>
>>----------
>>
>>iwconfig
>>eth1 IEEE 802.11g ESSID:"xxxxxx"
>>Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89
>>Bit Rate=54 Mb/s Tx-Power=20 dBm
>>Retry limit:7 RTS thr:off Fragment thr:off
>>Encryption key:off
>>Power Management:off
>>Link Quality=79/100 Signal level=-50 dBm Noise level=-83 dBm
>>Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>Tx excessive retries:0 Invalid misc:0 Missed beacon:4
>>
>>ifconfig
>>eth1 Link encap:Ethernet HWaddr 00:12:F0:73:7D:A7
>>inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link
>>UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
>>RX packets:68 errors:0 dropped:0 overruns:0 frame:0
>>TX packets:1 errors:0 dropped:15 overruns:0 carrier:1
>>collisions:0 txqueuelen:1000
>>RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff
>>
>>----------
>>
>>Most things ok, but no IP address
>>Can't browse, etc.
>>Try to bring up the interface
>>The system things it's already running
>>
>>----------
>>
>>ifup eth1
>>eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>>eth1 configuration: wlan-id-00:12:f0:73:7d:a7
>>eth1 warning: wpa_supplicant already running on interface
>>DHCP client is already running on eth1
>>
>>----------
>>
>>Take the interface down
>>
>>----------
>>
>>ifdown eth1
>>eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>>eth1 configuration: wlan-id-00:12:f0:73:7d:a7
>>
>>----------
>>
>>iwconfig unchanged
>>ifconfig gone
>>
>>----------
>>
>>iwconfig
>>eth1 IEEE 802.11g ESSID:"xxxxxx"
>>Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89
>>Bit Rate=54 Mb/s Tx-Power=20 dBm
>>Retry limit:7 RTS thr:off Fragment thr:off
>>Encryption key:off
>>Power Management:off
>>Link Quality=80/100 Signal level=-49 dBm Noise level=-84 dBm
>>Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>Tx excessive retries:0 Invalid misc:0 Missed beacon:3
>>
>>ifconfig
>>(no eth1)
>>
>>----------
>>
>>Bring up the wireless interface
>>
>>----------
>>
>>
>>ifup eth1
>>eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
>>eth1 configuration: wlan-id-00:12:f0:73:7d:a7
>>eth1 starting wpa_supplicant
>>Starting DHCP Client Daemon on eth1... . . . . . IP/Netmask:
>xxx.xxx.xxx.xxx/
>>255.255.255.0 <http://255.255.255.0> <http://255.255.255.0>
><http://255.255.255.0>
>>
>>----------
>>
>>Everything comes up ok
>>
>>----------
>>
>>iwconfig
>>eth1 IEEE 802.11g ESSID:"xxxxxx"
>>Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89
>>Bit Rate=54 Mb/s Tx-Power=20 dBm
>>Retry limit:7 RTS thr:off Fragment thr:off
>>Encryption key:57FA-8FC4-F8 Security mode:open
>>Power Management:off
>>Link Quality=77/100 Signal level=-52 dBm Noise level=-83 dBm
>>Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>Tx excessive retries:0 Invalid misc:0 Missed beacon:1
>>
>>ifconfig
>>eth1 Link encap:Ethernet HWaddr 00:12:F0:73:7D:A7
>>inet addr:192.168.1.104 <http://192.168.1.104> <http://192.168.1.104>
><http://192.168.1.104> Bcast
>>xxxxxx.xxx.xxx Mask:255.255.255.0 <http://255.255.255.0>
><http://255.255.255.0> <
>>http://255.255.255.0>
>>inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link
>>UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
>>RX packets:42 errors:0 dropped:0 overruns:0 frame:0
>>TX packets:20 errors:0 dropped:18 overruns:0 carrier:1
>>collisions:0 txqueuelen:1000
>>RX bytes:760 (760.0 b) TX bytes:2157 (2.1 Kb)
>>Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff
>>
>>----------
>>
>>Everything ok
>>
>>----------
>>
>>
>>5. Posted the contents of /etc/sysconfig/network
>>
>>drwxr-xr-x 6 root root 368 2005-10-23 22:40 .
>>drwxr-xr-x 7 root root 1584 2005-10-19 23:27 ..
>>-rw-r--r-- 1 root root 6979 2005-09-09 17:15 config
>>-rw-r--r-- 1 root root 6707 2005-10-19 23:34 dhcp
>>-rw-r--r-- 1 root root 141 2005-09-09 17:15 ifcfg-lo
>>-rw-r--r-- 1 root root 5779 2005-09-09 17:15 ifcfg.template
>>-rw------- 1 root root 686 2005-10-21 23:36
>>ifcfg-wlan-id-00:12:f0:73:7d:a7
>>drwxr-xr-x 2 root root 48 2005-09-09 17:27 if-down.d
>>-rw-r--r-- 1 root root 239 2005-09-09 17:15 ifroute-lo
>>drwxr-xr-x 2 root root 88 2005-10-19 22:55 if-up.d
>>drwx------ 2 root root 48 2005-09-09 17:27 providers
>>drwxr-xr-x 2 root root 1336 2005-10-19 22:55 scripts
>>-rw-r--r-- 1 root root 5469 2005-10-19 22:54 wireless
>>
>>
>>6. Tried calling the ifcfg file ifcgfg-wlan0
>>
>>I tried calling it ifcfg-wlan0 and the interface didn't come up. It
>>wouldn't come up when I did the down/up thing either. Then I renamed it
>>ifcfg-eth1. It still wouldn't come up on boot but it would come up if I
>>took it down and up again. So just the same as when it had the long name.
>>
>>
>>
>
>
>--
>David Martin, Senior Software Architect
>MultiAd Information Technologies
>dmartin@multiad.com <mailto:dmartin@multiad.com>
>Phone: 309.690.5362
>
>
>
>	*dmartin.vcf*
>1K Download </mail/?view=att&disp=attd&attid=0.1&th=1073892dbc8c66dd>
>
>------------------------------------------------------------------------
>* Syv Ritch <suse@911networks.com> * 	* 28 October 2005 19:08 *
>Reply-To: suse@911networks.com
>To: 'o-Dzin Tridral <tridral@gmail.com>
>Cc: opensuse@opensuse.org, suse-linux-e@suse.com
>'o-Dzin Tridral wrote:
>> On 28/10/05, ken <gebser@speakeasy.net <mailto:gebser@speakeasy.net>>
>wrote:
>>>
>>>
>>> I would think that ifup and ifdown are already being run on boot and
>>> shutdown respectively. I wouldn't add them in anywhere until I found
>>> out whether or not this was the case.
>>>
>>> Perhaps more importantly, when asking for help, provide some information
>>> about the problem, the hardware and software used, what you've tried and
>>> what happened, what error messages resulted, what log files you examined
>>> and what you found or didn't find there, and so on.
>>>
>>> hth,
>>> ken
>>
>>
>>
>> Thank you for taking the time to reply. The details are below. I'd be
>> grateful if anyone could point me at a solution!
>>
>> many thanks,
>>
>> 'o-Dzin
>>
>> In summary
>> 1. Installed Suse 10.0 and ipw-firmware
>> 2. Tried NetGo
>
> From netgo's FAQ:
>
>Q: Why does netGo only support WEP encryption and not WPA?
>
>netGo uses 'iwconfig' to set all the wireless settings, and
>'iwconfig' only supports WEP encryption at the moment. The only
>application that supports WPA encryption in Linux at the moment
>is (as far as I know) WPA Supplicant, and it only supports a few
>wlan cards. But, if you're using a wlan card that is supported by
>WPA Supplicant and you want to use WPA encryption you can use
>netGo's "Execute custom script" feature. Just create a script
>which calls the WPA Supplicant command to set your key.
>
>--
>Thanks
>http://www.911networks.com
>When the network has to work Cisco/Microsoft
>
>------------------------------------------------------------------------
>* Hans du Plooy <hansdp-lists@sagacit.com> * 	* 28 October 2005 20:18 *
>To: suse-linux-e@suse.com
>On Thursday 27 October 2005 23:51, 'o-Dzin Tridral wrote:
>> I've read (and been part of) a number of threads of discussion relating to
>> automatically starting the wireless connection on boot. A fair number of
>> people seem to have this problem, and thesymptoms seem to be the same
>- the
>> system recognises that there's a wrieles card but doesn't properly
>bring up
>> the interface.
>Is this in 9.3 or 10.0?  I had the problem in 9.3 that with my wireless card
>plugged in (Atheros PCMCIA based) the boot process would hang at starting
>network, until I eject the card, then it would continue normally.  Then I
>plug the card back in and it comes up automatically (I had it configured
>with
>"hotplug" option in yast).
>
>In 10.0 This seems to be remedied.
>
>Hans
>
>--
>Check the headers for your unsubscription address
>For additional commands send e-mail to suse-linux-e-help@suse.com
><mailto:suse-linux-e-help@suse.com>
>Also check the archives at http://lists.suse.com
>Please read the FAQs: suse-linux-e-faq@suse.com
><mailto:suse-linux-e-faq@suse.com>
>
>
>------------------------------------------------------------------------
>* 'o-Dzin Tridral <tridral@gmail.com> * 	* 28 October 2005 21:00 *
>To: David Martin <dmartin@multi-ad.com>
>Cc: opensuse@opensuse.org, suse-linux-e@suse.com
>On 28/10/05, *David Martin* <dmartin@multi-ad.com
><mailto:dmartin@multi-ad.com>> wrote:
>
>    I am having the exact same problem.  Of note, if I disable the
>    encryption key and open my wireless network up everything seems to work
>    just fine.  It seems to give up quickly on validating my auth key and
>    acquiring an IP address.  It's definately a bug. 
>
>
>I'd never thought of that.  It works for me.  Thank you.   I've  taken
>the key off and the interface works no problem.  Should I report the
>bug? How would I do that?
>
>Thanks for the advice.
>
>'o-Dzin
> 
>
>------------------------------------------------------------------------
>* Ken Schneider <suse-list@bout-tyme.net> * 	* 28 October 2005 21:53 *
>Reply-To: suse-linux-e@suse.com
>To: suse-linux-e@suse.com
>On Fri, 2005-10-28 at 22:00 +0100, 'o-Dzin Tridral wrote:
>> On 28/10/05, David Martin <dmartin@multi-ad.com
><mailto:dmartin@multi-ad.com>> wrote:
>> >
>> > I am having the exact same problem. Of note, if I disable the
>> > encryption key and open my wireless network up everything seems to work
>> > just fine. It seems to give up quickly on validating my auth key and
>> > acquiring an IP address. It's definately a bug.
>>
>>
>> I'd never thought of that. It works for me. Thank you. I've taken the key
>> off and the interface works no problem. Should I report the bug? How
>would I
>> do that?
>>
>> Thanks for the advice.
>>
>> 'o-Dzin
>
>Are you having problems with your email client. This is not the first
>time to receive a double post from you. I also noticed that you sent
>this to David and Cc'ed both lists. I believe David is on the list and
>therefore does not need it sent also to his personal address.
>If David is on both lists that you Cc: that means he received six copies
>of the same email. I am on both lists and received four copies of your
>same email. A little thought on how lists operate goes a long way.
>
>Also cross posting to many lists is not considered good list etiquette.
>--
>Ken Schneider
>UNIX  since 1989, linux since 1994, SuSE  since 1998
>
>
>--
>Check the headers for your unsubscription address
>For additional commands send e-mail to suse-linux-e-help@suse.com
><mailto:suse-linux-e-help@suse.com>
>Also check the archives at http://lists.suse.com
>Please read the FAQs: suse-linux-e-faq@suse.com
><mailto:suse-linux-e-faq@suse.com>
>
>
>------------------------------------------------------------------------
>* 'o-Dzin Tridral <tridral@gmail.com> * 	* 28 October 2005 22:29 *
>To: suse-linux-e@suse.com
>Dear Ken, David and list,
>
>I'm sorry.
>
>Sending direct to David was an accident.
>
>Sending to both lists springs from not being entirely sure which is most
>appropriate.  The same question has come up on both lists so I thought
>both were appropriate.
>
>I'm happy to be advised on how best to use the list without causing
>problems to people.
>
>best regards,
>
>'Ã¶-Dzin
>
>On 28/10/05, *Ken Schneider* <suse-list@bout-tyme.net
><mailto:suse-list@bout-tyme.net>> wrote:
>
>
>    Are you having problems with your email client. This is not the first
>    time to receive a double post from you. I also noticed that you sent
>    this to David and Cc'ed both lists. I believe David is on the list and
>    therefore does not need it sent also to his personal address.
>    If David is on both lists that you Cc: that means he received six copies
>    of the same email. I am on both lists and received four copies of your
>    same email. A little thought on how lists operate goes a long way.
>
>    Also cross posting to many lists is not considered good list etiquette.
>    --
>    Ken Schneider
>    UNIX  since 1989, linux since 1994, SuSE  since 1998
>
>
>    --
>    Check the headers for your unsubscription address
>    For additional commands send e-mail to suse-linux-e-help@suse.com
>    <mailto:suse-linux-e-help@suse.com>
>    Also check the archives at http://lists.suse.com
>    Please read the FAQs: suse-linux-e-faq@suse.com
>    <mailto:suse-linux-e-faq@suse.com>
>
>
>
>
>
>-- 
>'Ã¶-Dzin Tridral
>Caerdydd, Cymru
>www.spacious-passion.org <http://www.spacious-passion.org>
>
>------------------------------------------------------------------------
>* Ken Schneider <suse-list@bout-tyme.net> * 	* 28 October 2005 22:47 *
>Reply-To: suse-linux-e@suse.com
>To: suse-linux-e@suse.com
>On Fri, 2005-10-28 at 23:29 +0100, 'o-Dzin Tridral wrote:
>> Dear Ken, David and list,
>>
>> I'm sorry.
>>
>> Sending direct to David was an accident.
>>
>> Sending to both lists springs from not being entirely sure which is most
>> appropriate. The same question has come up on both lists so I thought both
>> were appropriate.
>>
>> I'm happy to be advised on how best to use the list without causing
>problems
>> to people.
>>
>> best regards,
>>
>> 'Ã¶-Dzin
>>
>Support questions should go to this list. Bug reports pertaining to the
>beta version of suse OSS should go to the opensuse list. Also top
>posting is not well received on either list.
>
>--
>Ken Schneider
>UNIX  since 1989, linux since 1994, SuSE  since 1998
>
>
>--
>Check the headers for your unsubscription address
>For additional commands send e-mail to suse-linux-e-help@suse.com
><mailto:suse-linux-e-help@suse.com>
>Also check the archives at http://lists.suse.com
>Please read the FAQs: suse-linux-e-faq@suse.com
><mailto:suse-linux-e-faq@suse.com>
>
>
>------------------------------------------------------------------------
>* Daniel Hatfield <daniel@n8ture4play.org> * 	* 28 October 2005 23:07 *
>Reply-To: opensuse@opensuse.org
>To: opensuse@opensuse.org
> > I am having the exact same problem. Of note, if I disable the
>> > encryption key and open my wireless network up everything seems to
>work
>> > just fine. It seems to give up quickly on validating my auth key and
>> > acquiring an IP address. It's definately a bug.
>
>There is a big issue with the IPW2200 firmware regarding encryption.
>One solution that often fixes peoples issues with this is as follows.  I
>think Suse may already have this set, but it is defiantly important.
>
>As su do the following at the command line (if not already present):
>
>1. pico /etc/modprobe.d/ipw2200
>2. Add a line that reads (without the quotes), "options ipw2200
>hwcrypto=0"
>3. Save the file.
>4. Restart your computer (just to keep it simple).
>
>Also, I've seen problems with these cards when Wireless Access Point is
>using a hidden ESSID.  Make sure yours isn't hidden.
>
>Good luck!
>Daniel
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org
><mailto:opensuse-unsubscribe@opensuse.org>
>For additional commands, e-mail: opensuse-help@opensuse.org
><mailto:opensuse-help@opensuse.org>
>
>------------------------------------------------------------------------
>* AgustÃ Dosaiguas FalcÃ³ <agusti@dosaiguas.net> * 	* 29 October 2005
>02:19 *
>To: suse-linux-e@suse.com
>A Divendres 28 Octubre 2005 21:55, David Martin va escriure:
>> I am having the exact same problem.  Of note, if I disable the
>> encryption key and open my wireless network up everything seems to work
>> just fine.  It seems to give up quickly on validating my auth key and
>> acquiring an IP address.  It's definately a bug.
>>
>
>I have this problem too and my wireless interface is an Intel PRO Wireless
>2200BG using the ipw-firmware too. So... it seems a bug, isn't it?
>
>--
>Check the headers for your unsubscription address
>For additional commands send e-mail to suse-linux-e-help@suse.com
><mailto:suse-linux-e-help@suse.com>
>Also check the archives at http://lists.suse.com
>Please read the FAQs: suse-linux-e-faq@suse.com
><mailto:suse-linux-e-faq@suse.com>
>
>
>------------------------------------------------------------------------

Actions: View

Attachments on bug 131503: 56240