P.S. I prefer "ifup" over NetworkManager as connection is made on boot and tasks can be accomplished independent of somebody being logged in.

issuing dhclient in this situation returns:

Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0_rename: unknown hardware address type 801
wmaster0_rename: unknown hardware address type 801
Bind socket to interface: No such device

If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.

If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server@isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.

Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.

exiting.

(In reply to comment #1 from Casual J. Programmer)
> P.S. I prefer "ifup" over NetworkManager as connection is made on boot and
> tasks can be accomplished independent of somebody being logged in.

You don't need to use the NetworkManager, just configure your network
card with YaST2. Please provide the network configuration files, e.g.
using:

    grep -v '^$' /etc/sysconfig/network/ifcfg-* | grep -v ifcfg-lo

and output of

    iwconfig

but replace all WLAN keys, passwords, etc. with KKKKKK first (!!!).

Further, please provide the output of

    ip addr show ; ip route show ; ip link show

and the/var/lib/dhcpcd/dhcpcd-*.info and /var/lib/dhcp/dhclient.leases
files (when you are using dhcp and they exists) and / or call the

    dhcpcd-test <interface>

script.

grep -v '^$' /etc/sysconfig/network/ifcfg-* | grep -v ifcfg-lo
/etc/sysconfig/network/ifcfg-eth0:BOOTPROTO='dhcp'
/etc/sysconfig/network/ifcfg-eth0:BROADCAST=''
/etc/sysconfig/network/ifcfg-eth0:ETHTOOL_OPTIONS=''
/etc/sysconfig/network/ifcfg-eth0:IPADDR=''
/etc/sysconfig/network/ifcfg-eth0:MTU=''
/etc/sysconfig/network/ifcfg-eth0:NAME='PRO/100 VE Network Connection'
/etc/sysconfig/network/ifcfg-eth0:NETMASK=''
/etc/sysconfig/network/ifcfg-eth0:NETWORK=''
/etc/sysconfig/network/ifcfg-eth0:REMOTE_IPADDR=''
/etc/sysconfig/network/ifcfg-eth0:STARTMODE='auto'
/etc/sysconfig/network/ifcfg-eth0:USERCONTROL='no'
/etc/sysconfig/network/ifcfg-wlan0:BOOTPROTO='dhcp'
/etc/sysconfig/network/ifcfg-wlan0:BROADCAST=''
/etc/sysconfig/network/ifcfg-wlan0:ETHTOOL_OPTIONS=''
/etc/sysconfig/network/ifcfg-wlan0:IPADDR=''
/etc/sysconfig/network/ifcfg-wlan0:MTU='1500'
/etc/sysconfig/network/ifcfg-wlan0:NAME='PRO/Wireless 3945ABG Network Connection'
/etc/sysconfig/network/ifcfg-wlan0:NETMASK=''
/etc/sysconfig/network/ifcfg-wlan0:NETWORK=''
/etc/sysconfig/network/ifcfg-wlan0:REMOTE_IPADDR=''
/etc/sysconfig/network/ifcfg-wlan0:STARTMODE='auto'
/etc/sysconfig/network/ifcfg-wlan0:USERCONTROL='no'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_AP=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_AUTH_MODE='psk'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_BITRATE='auto'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_CA_CERT=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_CHANNEL=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_CLIENT_CERT=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_CLIENT_KEY=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_CLIENT_KEY_PASSWORD=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_DEFAULT_KEY='0'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_EAP_AUTH=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_EAP_MODE=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_ESSID='>manus manum lavat<'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_FREQUENCY=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY_0=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY_1=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY_2=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY_3=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_KEY_LENGTH='128'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_MODE='Managed'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_NICK=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_NWID=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_PEAP_VERSION=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_POWER='yes'
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_WPA_ANONID=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_WPA_IDENTITY=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_WPA_PASSWORD=''
/etc/sysconfig/network/ifcfg-wlan0:WIRELESS_WPA_PSK='KKKKKK'

iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0_rename  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:">manus manum lavat<"  
          Mode:Managed  Frequency:2.422 GHz  Access Point: 00:04:0E:A4:4F:A7   
          Bit Rate=54 Mb/s   Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Encryption key:KKKKKK [2]
          Link Quality=92/100  Signal level=-39 dBm  Noise level=-76 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ip addr show ; ip route show ; ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:16:36:34:25:66 brd ff:ff:ff:ff:ff:ff
3: wmaster0_rename: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ieee80211 qlen 1000
    link/ieee802.11 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.33/24 brd 192.168.0.255 scope global wlan0
    inet6 fe80::213:2ff:fe18:12ac/64 scope link 
       valid_lft forever preferred_lft forever
192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.33 
169.254.0.0/16 dev wlan0  scope link 
127.0.0.0/8 dev lo  scope link 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:16:36:34:25:66 brd ff:ff:ff:ff:ff:ff
3: wmaster0_rename: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ieee80211 qlen 1000
    link/ieee802.11 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff

dhcpcd-test wlan0
dhcpcd: MAC address = 00:13:02:18:12:ac

Created attachment 198733 [details]
/var/lib/dhcp

Created attachment 198734 [details]
/var/lib/dhcpcd

Actually, as I just found out, when NetworkManager is enabled and the dhcp address is refreshed manually by issuing dhclient then internet access is blocked too, although the applet shows a proper connection.

Only after service network restart is connectivity reestablished.

(In reply to comment #7 from Casual J. Programmer)
> Actually, as I just found out, when NetworkManager is enabled and the dhcp
> address is refreshed manually by issuing dhclient then internet access is
> blocked too, although the applet shows a proper connection.

I don't know what the applet exactly shows...

The "ip addr/link show" in comment #4 shows "NO-CARRIER", but the IP
address is set by dhcpc client:

3: wmaster0_rename: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ieee80211
qlen 1000
    link/ieee802.11 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc
           ^^^^^^^^^^
           ||||||||||

pfifo_fast qlen 1000
    link/ether 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.33/24 brd 192.168.0.255 scope global wlan0
         ^^^^^^^^^^^^^^^
         |||||||||||||||

    inet6 fe80::213:2ff:fe18:12ac/64 scope link 
       valid_lft forever preferred_lft forever


There are no filter rules active? Please call "SuSEfirewall2 stop"
and check with:

for t in $(cat /proc/net/ip_tables_names) ; do iptables -t $t -L -nv ; done


If there are no filter rules set, it may be also some driver problem
(this would explain the NO-CARRIER flag).


> Only after service network restart is connectivity reestablished.

After a restart the network works? Can you attach a "ip addr show"
when the network is working?

Reassigning to wireless maintainer, but it may be also a duplicate of
e.g. Bug #354141 (wmaster0_rename)...

For network working:

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:16:36:34:25:66 brd ff:ff:ff:ff:ff:ff
3: wmaster0_rename: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ieee80211 qlen 1000
    link/ieee802.11 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:13:02:18:12:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.33/24 brd 192.168.0.255 scope global wlan0
    inet6 fe80::213:2ff:fe18:12ac/64 scope link 
       valid_lft forever preferred_lft forever

For network blocked after dhclient:

#SuSEfirewall2 stopSuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules unloaded.

#for t in $(cat /proc/net/ip_tables_names) ; do iptables -t $t -L -nv ; done
Chain PREROUTING (policy ACCEPT 116K packets, 144M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 115K packets, 144M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 92134 packets, 9233K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 92190 packets, 9244K bytes)
 pkts bytes target     prot opt in     out     source               destination         
Chain PREROUTING (policy ACCEPT 1184 packets, 202K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 3744 packets, 231K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 3744 packets, 231K bytes)
 pkts bytes target     prot opt in     out     source               destination         
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

As described in bug #354141 please remove the file /etc/udev/rules.d/70-persistent-net.rules and reboot.

Does the issue still show up?

Yes, it does.

1. Delete /etc/udev/rules.d/70-persistent-net.rules ( copy attached )
2. set network access to ifup with yast2 lan
3. /etc/udev/rules.d/70-persistent-net.rules has been recreated, but is empty
4. reboot
5. Network connection established according to Network Monitor 2.12.1 (applet in taskbar) see screenshot
6. wget reports network access not possible.
7. checking /etc/udev/rules.d/70-persistent-net.rules it's there again
8. delete /etc/udev/rules.d/70-persistent-net.rules again
9. service network restart
10. same as 5.

Created attachment 199778 [details]
screenshot of Network Monitor applet

Created attachment 199779 [details]
Screenshot of output from dhclient

Ok, thanks.

Next step:
- Run "rcnetwork stop"
- Try to configure your wireless connection using plain wpa_supplicant.
That is write a wpa_supplicant.conf and run "wpa_supplicant -dd -iwlan0 -Dwext -c wpa_supplicant.conf" to get the wireless connection up.
- Afterwards try to get an IP by running "dhcpcd wlan0".

If you need help for creating the wpa_supplicant.conf just ask :)

OK, wpa_supplicant.conf created from wpa_gui:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1

network={
	ssid=">manus manum lavat<"
	psk="my completely secret password"
	proto=RSN
	key_mgmt=WPA-PSK
	pairwise=CCMP
}

issuing 

 wpa_supplicant -dd -iwlan0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf

connects to the AP

dhcpcd wlan0

does nothing (visible) stays away for a minute or so then prompt is back.

According to wpa_gui the connection to the AP is made, see screenshot

Created attachment 199798 [details]
screenshot of wpa_gui

Would you please attach the wpa_supplicant output?

Here you go: reran wpa_supplicant with option -f in the above context. /var/log/wpa_supplicant.log attached

Created attachment 199816 [details]
/var/log/wpa_supplicant.log for test case

Not sure if this is significant for the situation:

There is a file /etc/dbus-1/system.d/wpa_supplicant.conf, containing:

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy user="root">
                <allow own="fi.epitest.hostap.WPASupplicant"/>

                <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
                <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
        </policy>
        <policy context="default">
                <deny own="fi.epitest.hostap.WPASupplicant"/>
                <deny send_destination="fi.epitest.hostap.WPASupplicant"/>
                <deny send_interface="fi.epitest.hostap.WPASupplicant"/>
        </policy>
</busconfig>

As far as I know, we don't deal with hostap here ??

Strange, the log states that the association with bssid 00:00:00:00:00:00 was made which is obviously not correct.

1) Please attach the output of "hwinfo --wlan"
2) Please attach the output of "iwevent wlan0" while wpa_supplicant is trying to establish the connection.

Thanks.

hwinfo --wlan
07: PCI 100.0: 0282 WLAN controller                             
  [Created at pci.301]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4222
  Unique ID: y9sn.xDGkhUDfcCA
  Parent ID: z8Q3.ZbAWgKMCoE3
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 3945ABG Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4222 "PRO/Wireless 3945ABG Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1001 
  Revision: 0x02
  Driver: "iwl3945"
  Driver Modules: "iwl3945"
  Device File: wlan0
  Device Files: wlan0, wmaster0
  Features: WLAN
  Memory Range: 0xda000000-0xda000fff (rw,non-prefetchable)
  IRQ: 219 (no events)
  HW Address: 00:13:02:18:12:ac
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 34 36 38 40 42 44 46 48 52 56 60 64 100 104 108 112 116 120 124
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.17 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v00008086d00004222sv00008086sd00001001bc02sc80i00"
  Driver Info #0:
    Driver Status: iwl3945 is active
    Driver Activation Cmd: "modprobe iwl3945"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #20 (PCI bridge)

Created attachment 199830 [details]
output from iwevent > /tmp/iwevent.log

Thanks so far.

Due to comments #20 and #24 I guess its a driver-issue. Let's see if I can spent some time on reproducing this issue soon.

Not sure whether your assumption is correct:

NetworkManager: uses wpa_supplicant and iwl3945 driver ( now in kernel ) and works

IfUp: uses wpa_supplicant and iwl3946 driver and does not work

It is kind of hard for me to see how the driver could be the culprit.

Here is output from iwevent while NetworkManager is running for comparison, starts out connected to >manus manum lavat< reconnects to FON_UMC711 reconnects to >manus manum lavat<

iwevent
Waiting for Wireless Events from interfaces...
12:14:19.923594   wlan0    New Access Point/Cell address:Not-Associated
12:14:19.924254   wlan0    Set ESSID:off/any
12:14:19.924635   wlan0    Set Encryption key:off
12:14:23.196276   wlan0    Scan request completed
12:14:23.197520   wlan0    Set Mode:Managed
12:14:23.198874   wlan0    Set Frequency:2.432 GHz (Channel 5)
12:14:23.199276   wlan0    Set ESSID:"FON_UMC711"
12:14:23.207711   wlan0    Custom driver event:ASSOCINFO(ReqIEs=000a464f4e5f554d43373131010802040b160c12182432043048606cdd070050f202000100 RespIEs=010882848b0c1296182432043048606cdd180050f20201018e0002a3400027a4000042435e0062322f00dd0900037f01010000ff7f)
12:14:23.207751   wlan0    New Access Point/Cell address:00:18:84:11:BB:51
12:15:32.921518   wlan0    Set ESSID:off/any
12:15:32.921629   wlan0    New Access Point/Cell address:Not-Associated
12:15:32.927526   wlan0    Custom driver event:ASSOCINFO(ReqIEs=000a464f4e5f554d43373131010802040b160c12182432043048606cdd070050f202000100 RespIEs=010882848b0c1296182432043048606cdd180050f20201018e0002a3400027a4000042435e0062322f00dd0900037f01010000ff7f)
12:15:32.927565   wlan0    New Access Point/Cell address:00:18:84:11:BB:51
12:15:32.948990   wlan0    Set Encryption key:off
12:15:32.953507   wlan0    New Access Point/Cell address:Not-Associated
12:15:35.249898   wlan0    Set ESSID:off/any
12:15:35.249977   wlan0    Set Encryption key:off
12:15:35.260808   wlan0    Custom driver event:ASSOCINFO(ReqIEs=000a464f4e5f554d43373131010802040b160c12182432043048606cdd070050f202000100 RespIEs=010882848b0c1296182432043048606cdd180050f20201018e0002a3400027a4000042435e0062322f00dd0900037f01010000ff7f)
12:15:35.260853   wlan0    New Access Point/Cell address:00:18:84:11:BB:51
12:15:35.260873   wlan0    New Access Point/Cell address:Not-Associated
12:15:40.485142   wlan0    Scan request completed
12:15:40.486028   wlan0    Set Mode:Managed
12:15:40.486726   wlan0    Set Frequency:2.432 GHz (Channel 5)
12:15:40.487100   wlan0    Set ESSID:"FON_UMC711"
12:15:40.497073   wlan0    Custom driver event:ASSOCINFO(ReqIEs=000a464f4e5f554d43373131010802040b160c12182432043048606cdd070050f202000100 RespIEs=010882848b0c1296182432043048606cdd180050f20201018e0002a3400027a4000042435e0062322f00dd0900037f01010000ff7f)
12:15:40.497152   wlan0    New Access Point/Cell address:00:18:84:11:BB:51
12:15:53.100371   wlan0    Set ESSID:off/any
12:15:53.100659   wlan0    New Access Point/Cell address:Not-Associated
12:15:53.106592   wlan0    Custom driver event:ASSOCINFO(ReqIEs=000a464f4e5f554d43373131010802040b160c12182432043048606cdd070050f202000100 RespIEs=010882848b0c1296182432043048606cdd180050f20201018e0002a3400027a4000042435e0062322f00dd0900037f01010000ff7f)
12:15:53.106630   wlan0    New Access Point/Cell address:00:18:84:11:BB:51
12:15:53.126832   wlan0    Set Encryption key:off
12:15:53.128651   wlan0    New Access Point/Cell address:Not-Associated
12:15:53.446008   wlan0    Scan request completed
12:15:53.446704   wlan0    Set Mode:Managed
12:15:53.449200   wlan0    Set Frequency:2.422 GHz (Channel 3)
12:15:53.449600   wlan0    Set ESSID:">manus manum lavat<"
12:15:53.457728   wlan0    Custom driver event:ASSOCINFO(ReqIEs=00133e6d616e7573206d616e756d206c617661743c010802040b160c12182432043048606c30140100000fac040100000fac040100000fac020000 RespIEs=010882848b960c12182432043048606c)
12:15:53.457770   wlan0    New Access Point/Cell address:00:04:0E:A4:4F:A7

(In reply to comment #26 from Casual J. Programmer)
> NetworkManager: uses wpa_supplicant and iwl3945 driver ( now in kernel ) and
> works

Oh, missed that info. Thanks for clarification.

This has changed after update from factory:

ifup wlan0
    wlan0     device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
    wlan0     warning: WPA configured but may be unsupported
    wlan0     warning: by this device
    wlan0     starting wpa_supplicant
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - Starting DHCP Client Daemon on wlan0... . . . . . IP/Netmask: 192.168.0.33 / 255.255.255.0 

So the ipw3945 gets an IP address almost instantaneously, yet connection to network is still not possible 

wget http://192.168.0.1 results in:

 wget http://192.168.0.1
--09:03:58--  http://192.168.0.1/
           => `index.html'
Connecting to 192.168.0.1:80... failed: No route to host.

Now at:

Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome2-SuSE-10.3-167
YaST GUI: yast2-qt-2.16.33-2
OS:       openSUSE 11.0 (i586) Alpha2 VERSION = 11.0
Kernel:   2.6.25-rc4-git1-2-default

rpm -qa | grep Net | sort

NetworkManager-0.7.0-36
NetworkManager-glib-0.7.0-36
NetworkManager-gnome-0.7.0-34
perl-Net-Daemon-0.43-38
perl-Net-DNS-0.63-4
perl-Net-IP-1.25-15
perl-Net_SSLeay-1.30-102

rpm -qa | grep net | sort

gnet-2.0.7-207
gnome-netstatus-2.12.1-142
gnome-netstatus-lang-2.12.1-142
gnome-nettool-2.20.0-70
libdnet1-1.11-88
libnetpbm10-10.26.44-44
netcat-1.10-966
netcfg-11.0-19
netpbm-10.26.44-44
net-tools-1.60-675
telnet-1.2-102
xinetd-2.3.14-101
yast2-inetd-2.15.1-108
yast2-network-2.16.24-2

How about pinging 192.168.0.1?

ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.30: icmp_seq=22 Destination Host Unreachable
From 192.168.0.30 icmp_seq=22 Destination Host Unreachable
From 192.168.0.30 icmp_seq=23 Destination Host Unreachable
From 192.168.0.30 icmp_seq=24 Destination Host Unreachable
From 192.168.0.30 icmp_seq=26 Destination Host Unreachable
From 192.168.0.30 icmp_seq=27 Destination Host Unreachable
From 192.168.0.30 icmp_seq=28 Destination Host Unreachable
From 192.168.0.30 icmp_seq=30 Destination Host Unreachable
From 192.168.0.30 icmp_seq=31 Destination Host Unreachable
From 192.168.0.30 icmp_seq=32 Destination Host Unreachable

After replugging the ethernet cable:

64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=1006 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=7.52 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=0.784 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=0.852 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=1.00 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=0.821 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=0.805 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=0.779 ms
^C
--- 192.168.0.1 ping statistics ---
40 packets transmitted, 8 received, +10 errors, 80% packet loss, time 39032ms
rtt min/avg/max/mdev = 0.779/127.435/1006.918/332.420 ms, pipe 3

This seems to work properly again after updating from factory today.

Now at:

Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome2-SuSE-10.3-172
YaST GUI: yast2-qt-2.16.33-5
OS:       openSUSE 11.0 (i586) Alpha3 VERSION = 11.0
Kernel:   2.6.25-rc6-git3-9-pae

rpm -qa | grep ipw | sort

ipw-firmware-8-70

rpm -qa | grep iwl | sort

iwl3945-ucode-2.14.1.5-38

Please reopen this bug if the issue appears again.
Thanks for reporting :)

Due to comment #31 -> FIXED.

This fix is in the Messenger Linux Server 4.0.0 build 20160106092434.  Source revision 6405.