Bugzilla – Bug 374307
ipw3945 no internet access although AP can be reached
Last modified: 2008-05-02 08:21:42 UTC
After clean installing from alpha3 DVD & update from factory internet access is not possible with ipw3945 configured for ifup method. Firewall is disabled, the AP can be reached and browsed. 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-173 YaST GUI: yast2-qt-2.16.33-6 OS: openSUSE 11.0 (i586) Alpha3 VERSION = 11.0 Kernel: 2.6.25-rc6-git5-10-pae rpm -qa | grep iwl3945 | sort iwl3945-ucode-2.14.1.5-38 rpm -qa | grep dhc | sort dhcp-3.0.6-66 dhcpcd-1.3.22pl4-312 dhcp-client-3.0.6-66 rpm -qa | grep fire | sort beagle-firefox-0.3.3-21 SuSEfirewall2-3.6_SVNr184-19 yast2-firewall-2.15.8-80
Hello, can you send me yast2 logs after you configurate your wifi card in yast ? If unsure look on: http://en.opensuse.org/Bugs/YaST Thanks!
Closing NORESPONSE, due to missing information for more than 10 days.
Again, closing bugs doesn't make them go away. If people don't answer for 10 days they probably have different priorities than you do. If you want to do something helpful, please go ahead and check out all bugs waiting for response from assignee for more then ten days.
Created attachment 210798 [details] yast2logs after configuring network multiple times
You have to specify a comment on this change. Please explain your change.
(In reply to comment #3 from Casual J. Programmer) > Again, closing bugs doesn't make them go away. If people don't answer for 10 > days they probably have different priorities than you do. Yes, they don't. But in most cases its impossible to debug them without the information. Therefore we can not fix them. On the other hand the reporter always can REOPEN the bug with the information and we will continue with debugging (just like in this case).
Could you please verify if the iwl3945-module is loaded using 'lsmod | grep iwl3945'? Some more output I'd like to see: - dmesg - iwconfig both after issuing 'rcnetwork restart' Thanks.
This might be a re occurrence of Bug 366506 actually. And definitely I reported it also as Bug 384660 :-( Fact is that the NIC connects to the AP and the AP can be logged into. Further Internet access is not possible under normal conditions. Only after ifdown eth0 dhclient wlan0 does the connection finally work. Shutting eth0 off in yast2 lan does not help. I added both commands to /etc/init.d/boot.local and am in business again. Bug 384660 contains the relevant yast2 logs. I am attaching dmesg and iwconfig to this one as requested.
Created attachment 211555 [details] dmesg.txt
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=2352 B Encryption key:0B79-AAAF-A76F-0B59-42A9-DBD3-4B83-E9C0 [2] Link Quality=92/100 Signal level=-39 dBm Noise level=-80 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Does it work with NetworkManager? If yes, attache please (or just check) /etc/sysconfig/network/ifcfg-* files >> Firewall is disabled, the AP can be reached and browsed. What you mean with that? From other machines, from 10.2, from NetworkManager?
NetworkManager does not work either, see Bug 345147 "Firewall is disabled, the AP can be reached and browsed" I did think this was pretty precise, apparently I am wrong. I disabled the Firewall to make sure it's not getting in the way. The AP I use to connect to the Internet ( a FRITZ!Box Fon WLAN 7050 (UI), Firmware-Version 14.04.33 ) can be reached by typing its IP address in the Navigation Tool Bar and logged into OK as well as its contents browsed. This is also most probably a duplicate of Bug 384660.
In case this is the same machine (I suppose so), configuration done by YaST is correct. The problem is with driver/dhcpcd/sysconfig/whatever. Marked as duplicate *** This bug has been marked as a duplicate of bug 384660 ***