https://bugzilla.novell.com/show_bug.cgi?id=383083
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383083#c76
--- Comment #76 from Marius Tomaschewski
OK, I believe the (long) below should satisfy your requirements, please let me know if it doesn't.
Yes, it does, thanks for all your effort!
First step after configuring in Yast2 and doing rcnetwork start [...]
Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done eth0 device: Intel Corporation 82566MM Gigabit Network Connection (rev 03) No configuration found for eth0 unused pan0 No configuration found for pan0 unused wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) wlan0 is controlled by ifplugd command 'iwconfig wlan0 nick linux-7wiq' returned Error for wireless request "Set Nickname" (8B1C) : SET failed on device wlan0 ; Operation not supported. done Setting up service network . . . . . . . . . . . . . . done
linux-7wiq:/etc/sysconfig/network # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.29: icmp_seq=1 Destination Host Unreachable From 192.168.1.29 icmp_seq=1 Destination Host Unreachable From 192.168.1.29 icmp_seq=2 Destination Host Unreachable
linux-7wiq:/etc/sysconfig/network # ping 192.168.1.10 PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data. From 192.168.1.29: icmp_seq=1 Destination Host Unreachable From 192.168.1.29 icmp_seq=1 Destination Host Unreachable From 192.168.1.29 icmp_seq=2 Destination Host Unreachable From 192.168.1.29 icmp_seq=3 Destination Host Unreachable ^C [...]
OK, the link does not work using static configuration. OK. the static ip configuration looks good in the "ip addr show" and "ip route show" outputs.
linux-7wiq:/etc/sysconfig/network # dhcpcd-test wlan0 info, wlan0: hardware address = 00:1f:3b:70:4d:77 info, wlan0: broadcasting for a lease debug, wlan0: sending DHCP_DISCOVER with xid 0x540a6679 debug, wlan0: waiting for 10 seconds debug, wlan0: sending DHCP_DISCOVER with xid 0x540a6679 debug, wlan0: sending DHCP_DISCOVER with xid 0x540a6679 debug, wlan0: sending DHCP_DISCOVER with xid 0x540a6679 err, wlan0: timed out info, wlan0: exiting
And dhcp client is also not able to find any dhcp server.
Still seems like a DHCP related issue to me.
No, it isn't. The dhcp client just send discover requests and does not get any answer from dhcp server. When you take a look into the messages where dhclient got an leases for eth0 interface - it needed >40 seconds for. Was the router off or still booting? My linksys (fritzbox similary) answers immediately: # time dhcpcd-test -d eth1 info, eth1: hardware address = 00:17:31:ca:a5:a5 info, eth1: broadcasting for a lease debug, eth1: sending DHCP_DISCOVER with xid 0x38bb4db8 debug, eth1: waiting for 10 seconds debug, eth1: got a packet with xid 0x38bb4db8 info, eth1: offered 172.16.0.1 from 172.16.0.250 [...] real 0m0.040s user 0m0.000s sys 0m0.012s Not even one second.
linux-7wiq:/home/quentinj # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:"Getalife" Mode:Managed Frequency:2.442 GHz Access Point: 00:1D:7E:AA:1D:4A Bit Rate=54 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Link Quality=100/100 Signal level=-42 dBm Noise level=-94 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Output of dmesg:
[...] Please attach it as file next time ;-)
I stopped at the using Netowrk manager part as I think that's just a duplicate using an alternate method?
Yes, similar. Was in the messages you've provided too :-) It looks for me, that you sometimes have an association, but it also breaks away again in same second. Jul 15 18:44:47 linux-7wiq kernel: wlan0: RX authentication from 00:1d:7e:aa:1d:4a (alg=0 transaction=2 status=0) Jul 15 18:44:47 linux-7wiq kernel: wlan0: authenticated ^^^^^^^^^^^^^ Jul 15 18:44:47 linux-7wiq kernel: wlan0: associate with AP 00:1d:7e:aa:1d:4a Jul 15 18:44:47 linux-7wiq kernel: wlan0: RX AssocResp from 00:1d:7e:aa:1d:4a (capab=0x421 status=0 aid=1) Jul 15 18:44:47 linux-7wiq kernel: wlan0: associated ^^^^^^^^^^ Jul 15 18:44:47 linux-7wiq kernel: wlan0: switched to short barker preamble (BSSID=00:1d:7e:aa:1d:4a) Jul 15 18:44:47 linux-7wiq kernel: wlan0 (WE) : Wireless Event too big (366) Jul 15 18:44:47 linux-7wiq kernel: wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 Jul 15 18:44:47 linux-7wiq kernel: wlan0: disassociate(reason=3) ^^^^^^^^^^^^^^^^^^^^^^ Jul 15 18:44:47 linux-7wiq kernel: wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 Jul 15 18:44:47 linux-7wiq kernel: wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 Jul 15 18:44:47 linux-7wiq kernel: wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 Jul 15 18:44:47 linux-7wiq avahi-daemon[3015]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.29. Jul 15 18:44:47 linux-7wiq avahi-daemon[3015]: New relevant interface wlan0.IPv4 for mDNS. Jul 15 18:44:47 linux-7wiq avahi-daemon[3015]: Registering new address record for 192.168.1.29 on wlan0.IPv4. The avahi daemon was able to join the multicast group, but please notice that all this messages was printed in same second. Jul 15 18:44:47 linux-7wiq SuSEfirewall2: SuSEfirewall2 not active Jul 15 18:45:30 linux-7wiq syslog-ng[2293]: last message repeated 3 times Jul 15 18:47:11 linux-7wiq dhcpcd[14765]: wlan0: hardware address = 00:1f:3b:70:4d:77 Jul 15 18:47:11 linux-7wiq dhcpcd[14765]: wlan0: broadcasting for a lease Jul 15 18:47:11 linux-7wiq dhcpcd[14765]: wlan0: sending DHCP_DISCOVER with xid 0x540a6679 [...] Jul 15 18:47:21 linux-7wiq dhcpcd[14765]: wlan0: timed out Jul 15 18:47:21 linux-7wiq dhcpcd[14765]: wlan0: exiting Jul 15 18:48:59 linux-7wiq dhcpcd[14769]: wlan0: hardware address = 00:1f:3b:70:4d:77 [...] Jul 15 18:49:02 linux-7wiq dhcpcd[14769]: wlan0: sending DHCP_DISCOVER with xid 0x8ea2a80 Jul 15 18:49:09 linux-7wiq syslog-ng[2293]: last message repeated 2 times Jul 15 18:49:09 linux-7wiq dhcpcd[14769]: wlan0: timed out Jul 15 18:49:09 linux-7wiq dhcpcd[14769]: wlan0: exiting The dhcpcd test was in a time, where there was no association... Another snippet: Jul 15 18:27:51 linux-7wiq kernel: wlan0: authenticated Jul 15 18:27:51 linux-7wiq kernel: wlan0: associate with AP 00:1d:7e:aa:1d:4a Jul 15 18:27:51 linux-7wiq kernel: wlan0: RX AssocResp from 00:1d:7e:aa:1d:4a (capab=0x431 status=0 aid=1) Jul 15 18:27:51 linux-7wiq kernel: wlan0: associated Jul 15 18:27:51 linux-7wiq kernel: wlan0: switched to short barker preamble (BSSID=00:1d:7e:aa:1d:4a) Jul 15 18:27:51 linux-7wiq kernel: wlan0 (WE) : Wireless Event too big (366) Jul 15 18:27:51 linux-7wiq kernel: wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 Jul 15 18:27:51 linux-7wiq kernel: wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 Jul 15 18:27:51 linux-7wiq kernel: wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 Jul 15 18:27:51 linux-7wiq kernel: wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 Jul 15 18:27:51 linux-7wiq kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 15 18:27:51 linux-7wiq kernel: iwl4965: Microcode SW error detected. Restarting 0x82000000. Jul 15 18:27:51 linux-7wiq kernel: iwl4965: Error setting Tx power (-5). Jul 15 18:27:51 linux-7wiq kernel: iwl4965: Error sending REPLY_PHY_CALIBRATION_CMD: time out after 500ms. Jul 15 18:27:52 linux-7wiq kernel: iwl4965: Error sending REPLY_QOS_PARAM: time out after 500ms. Jul 15 18:27:52 linux-7wiq avahi-daemon[3015]: Registering new address record for fe80::21f:3bff:fe70:4d77 on wlan0.*. Jul 15 18:27:53 linux-7wiq kernel: wlan0: No ProbeResp from current AP 00:1d:7e:aa:1d:4a - assume out of range Jul 15 18:27:53 linux-7wiq kernel: iwl4965: Error sending REPLY_RXON_ASSOC: [...] (In reply to comment #69 from Helmut Schaa)
(In reply to comment #66 from Quentin Jackson)
Any word on what might be done about this, or are we stuck and don't know what's causing it?
To me it looks like the wireless connection can be set up correctly, only the DHCP request seems to fail. But I have absolutely no idea why.
Btw. iwl4965 and DHCP works fine for my setup here.
Maybe Marius has an idea? :)
Yes, the driver has a problem. Neither static nor dhcp configuration works. There was an association, but for 1 second or something like this. There is some driver problem - it clearly reports "Microcode SW error detected.". Quentin: Does the hardware still works on Windows? Maybe the firmware is corrupt... Sorry, but I can't do anything from dhcp / sysconfig side here => Helmut. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.