On 28/10/05, ken 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 ) 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) 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.

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

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, Senior Software Architect MultiAd Information Technologies dmartin@multiad.com Phone: 309.690.5362

On Fri, 2005-10-28 at 22:00 +0100, 'o-Dzin Tridral wrote:

On 28/10/05, David Martin 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

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