install 'iw', there is a new dependency.

*** This bug has been marked as a duplicate of bug 539669 ***

This is by no means a duplicate of bug 539669, the iwl is working perfectly well, the access point can be logged into and configured. Only Internet access is not possible. iw _is_ installed properly.

OK, sorry.

Can you reset the logs using logrotate -f /etc/logrotate.conf 
and provide /var/log/boot.msg and /var/log/messages, please?

(In reply to comment #3)
> OK, sorry.
> 
> Can you reset the logs using logrotate -f /etc/logrotate.conf

reboot

> and provide /var/log/boot.msg and /var/log/messages, please?

Another change is, that the iwl3945 driver is mapped to wpa_supplicant
'wext' driver now by default. In the ifcfg-file the driver can be set
with the new
     WIRELESS_WPA_DRIVER=wext
variable.

Before, it was:
    WIRELESS_WPA_DRIVER=unsupported
    PREFER_WPA_SUPPLICANT=no

so when WIRELESS_AUTH_MODE in your ifcfg-file isn't set to
    wpa-*|WPA-*|psk|PSK|eap|EAP

or in another words, you are using WEP, the wpa_supplicant is used
by default, not old style setup using iwconfig & co.

Can you provide the /var/run/wpa_supplicant-$INTERFACE.conf, and
the /etc/sysconfig/network/ifcfg-$INTERFACE file too?

Of course without keys or other secrets, replace them with XXXXXXXXX.

Files as per comment #3&4 follow in a minute
Regarding #5 I am not sure whether we are in sync already, I'll try to be more precise.

1. Using NetworkManager all is fine.
2. Using Traditional Method ifup also works nice, to the extent that iwl3945 can "talk" to the AP (Fritz!Box), i.e wpa_supplicant is up and running, credentials (WPA2-PSK) are exchanged, and an IP is issued.
3. I can start Firefox, enter 192.168.178.1 (IP of AP) and get connected to the administrative Interface of the Fritz!Box
4. If I enter _any_ IP external to my network, I get a page not found.

So I assume we are talking a DNS / Routing issue here, rather than iwl3945

Created attachment 320923 [details]
/var/log/boot.msg & /var/log/messages after logreset

Created attachment 320924 [details]
configuration files wlan0 as requested

This may be same problem / reason as in bug 544195. The NetworkManager 
seems to write /etc/resolv.conf itself in last time instead to always
use netconfig and as result netconfig refuses to write it then:

Oct  3 08:42:20 workstation6l dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Oct  3 08:42:20 workstation6l dns-resolver: You can find my version in /etc/resolv.conf.netconfig

[...]
Oct  3 08:42:25 workstation6l ifup-dhcp:     wlan0     Starting DHCP4+DHCP6 client
Oct  3 08:42:28 workstation6l dhcpcd[7822]: wlan0: offered 192.168.178.22 from 192.168.178.1
Oct  3 08:42:28 workstation6l dhcpcd[7822]: wlan0: checking 192.168.178.22 is available on attached networks
Oct  3 08:42:29 workstation6l ifup-dhcp: . 
Oct  3 08:42:29 workstation6l dhcpcd[7822]: wlan0: leased 192.168.178.22 for 864000 seconds
Oct  3 08:42:29 workstation6l dhcpcd[7822]: wlan0: adding IP address 192.168.178.22/24
Oct  3 08:42:29 workstation6l dhcpcd[7822]: wlan0: adding default route via 192.168.178.1 metric 0
Oct  3 08:42:29 workstation6l dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Oct  3 08:42:29 workstation6l dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Oct  3 08:42:29 workstation6l dhcpcd-hook: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Oct  3 08:42:29 workstation6l dhcpcd-hook: You can find my version in /etc/resolv.conf.netconfig ...
Oct  3 08:42:45 workstation6l ifup-dhcp: . 
Oct  3 08:42:47 workstation6l ifup-dhcp:  
Oct  3 08:42:47 workstation6l ifup-dhcp:     wlan0     IP address: 192.168.178.22/24
Oct  3 08:42:47 workstation6l ifup-dhcp:     wlan0     DHCP6 continues in background
[...]

Above log shows, that the default route should be there (the "ip route
show" output would provide this info) and that the /etc/resolv.conf may
be not correct due to the NetworkManager changes, that may point to old
DNS servers.

Please call
    mv -f /etc/resolv.conf           /etc/resolv.conf.nm
    mv -f /etc/resolv.conf.netconfig /etc/resolv.conf
does it fix the problem?

When not, please provide /etc/resolv.conf* and the /var/run/netconfig
files as well as the "ip route show" and "netconfig update -v" outputs.

Yes, this fixes it, thanks for reacting so fast :-)

Actually it might interest you what's in resolv.conf, here you go:

workstation6l:~ # cat /etc/resolv.conf.nm
# Generated by NetworkManager

Empty :-(

workstation6l:~ # cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
search ac fritz.box
nameserver 192.168.178.1

(In reply to comment #10)
> Yes, this fixes it, thanks for reacting so fast :-)

You and your reports are always welcome!

(In reply to comment #11)
> Actually it might interest you what's in resolv.conf, here you go:
> 
> workstation6l:~ # cat /etc/resolv.conf.nm
> # Generated by NetworkManager
> 
> Empty :-(

Yes, see bug 544195 :-(

Resolving as duplicate of bug 544195.

*** This bug has been marked as a duplicate of bug 544195 ***