https://bugzilla.novell.com/show_bug.cgi?id=278619
------- Comment #2 from casualprogrammer@yahoo.com 2007-05-28 13:48 MST -------
This is interesting, as soon as I entered more WEP keys the connection was
lost. nm-applet was still indicating the WEP Network with its IP, while
iwconfig would show the essid of a nearby open network ( I have some 20
networks around here ) and claim association.
issuing #service network restart would have nm-applet trying to reconnect and
challenge me with the key-dialogue. None of the keys would work.
Switching back to ifup with YaST, then restarting network service again.
Issuing #iwconfig eth1 essid 'wepnetwork' key s:mykey, followed by ifup eth1
would connect immediately to the open network. ( This is how I am connected
now ).
Not sure how we get this in a state and sequence you may be able to follow.
tcpdump -ni eth1 shows (just the last few lines)
21:30:09.210103 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 1 win 365
21:30:09.211093 IP 192.168.182.54.3189 > 212.58.240.132.80: P 1:818(817) ack 1
win 365
21:30:09.357271 IP 212.58.240.132.80 > 192.168.182.54.3189: . ack 818 win 32711
21:30:09.360258 IP 212.58.240.132.80 > 192.168.182.54.3189: P 1:341(340) ack
818 win 32711
21:30:09.360337 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 341 win 432
21:30:09.363615 IP 212.58.240.132.80 > 192.168.182.54.3189: . 341:1781(1440)
ack 818 win 32711
21:30:09.363769 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 1781 win 613
21:30:09.500199 IP 212.58.240.132.80 > 192.168.182.54.3189: . 1781:3221(1440)
ack 818 win 32711
21:30:09.500346 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 3221 win 794
21:30:09.502982 IP 212.58.240.132.80 > 192.168.182.54.3189: P 3221:4661(1440)
ack 818 win 32711
21:30:09.505673 IP 212.58.240.132.80 > 192.168.182.54.3189: . 4661:6101(1440)
ack 818 win 32711
21:30:09.508422 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 4661 win 975
21:30:09.508407 IP 212.58.240.132.80 > 192.168.182.54.3189: P 6101:7541(1440)
ack 818 win 32711
21:30:09.509432 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 6101 win 1156
21:30:09.510414 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 7541 win 1337
21:30:09.643156 IP 212.58.240.132.80 > 192.168.182.54.3189: . 7541:8533(992)
ack 818 win 32711
21:30:09.643320 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 8533 win 1517
21:30:09.646286 IP 212.58.240.132.80 > 192.168.182.54.3189: . 8533:9973(1440)
ack 818 win 32711
21:30:09.650468 IP 212.58.240.132.80 > 192.168.182.54.3189: . 9973:11413(1440)
ack 818 win 32711
21:30:09.653238 IP 212.58.240.132.80 > 192.168.182.54.3189: . 11413:12853(1440)
ack 818 win 32711
21:30:09.655937 IP 212.58.240.132.80 > 192.168.182.54.3189: . 12853:14293(1440)
ack 818 win 32711
21:30:09.656578 IP 212.58.240.132.80 > 192.168.182.54.3189: P 14293:14701(408)
ack 818 win 32711
21:30:09.656945 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 9973 win 1698
21:30:09.657948 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 11413 win
1879
21:30:09.659115 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 12853 win
2060
21:30:09.660119 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14293 win
2241
21:30:09.661956 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14701 win
2421
21:30:14.365817 IP 212.58.240.132.80 > 192.168.182.54.3189: F 14701:14701(0)
ack 818 win 32711
21:30:14.402705 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14702 win
2421
21:30:23.180118 IP 192.168.182.54.3189 > 212.58.240.132.80: F 818:818(0) ack
14702 win 2421
21:30:23.313765 IP 212.58.240.132.80 > 192.168.182.54.3189: . ack 819 win 32711
21:30:38.196829 IP 192.168.182.54.26407 > 63.245.213.21.80: F 501:501(0) ack
709 win 7080
21:30:38.197806 IP 192.168.182.54.26406 > 63.245.213.21.80: F 535:535(0) ack
666 win 6650
21:30:38.253579 IP 63.245.213.21.80 > 192.168.182.54.26407: F 709:709(0) ack
502 win 8190
21:30:38.253734 IP 192.168.182.54.26407 > 63.245.213.21.80: . ack 710 win 7080
21:30:38.255211 IP 63.245.213.21.80 > 192.168.182.54.26406: F 666:666(0) ack
536 win 8190
21:30:38.255277 IP 192.168.182.54.26406 > 63.245.213.21.80: . ack 667 win 6650
1045 packets captured
1045 packets received by filter
0 packets dropped by kernel
The ip address is that of the open network.
While iwconfig eth1 shows:
iwconfig eth1
Warning: Driver for device eth1 has been compiled with version 22
of Wireless Extension, while this program supports up to version 21.
Some things may be broken...
eth1 IEEE 802.11b ESSID:">per aspera ad astra<" Nickname:"HERMES I"
Mode:Managed Frequency:2.432 GHz Access Point: 00:18:84:11:BB:51
Bit Rate:11 Mb/s Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Encryption key:3139-3432-3132-3237-2D6C-696E-69 Security mode:open
Power Management:off
Link Quality=19/92 Signal level=-72 dBm Noise level=-91 dBm
Rx invalid nwid:0 Rx invalid crypt:62 Rx invalid frag:2625
Tx excessive retries:99 Invalid misc:0 Missed beacon:0
which would be correct, only the ip should look more like 192.168.0.xx
ifstatus eth1 shows:
ifstatus eth1
eth1
eth1 configuration: wlan-id-00:02:2d:5c:f5:ef
eth1 DHCP client (dhcpcd) is running
IPADDR=192.168.182.54
NETMASK=255.255.255.0
GATEWAY=192.168.182.1
DOMAIN='key.chillispot.org'
DNS=192.168.0.25,192.168.0.25
DHCPSIADDR=0.0.0.0
DHCPCHADDR=00:02:2D:5C:F5:EF
REBINDTIME=525
eth1 is up
3: eth1: mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 00:02:2d:5c:f5:ef brd ff:ff:ff:ff:ff:ff
inet 192.168.182.54/24 brd 192.168.182.255 scope global eth1
inet6 fe80::202:2dff:fe5c:f5ef/64 scope link
valid_lft forever preferred_lft forever
eth1 IP address: 192.168.182.54/24
Configured routes for interface eth1:
default 192.168.0.1 - -
169.254.0.0 - 255.255.0.0 eth1
Active routes for interface eth1:
192.168.182.0/24 proto kernel scope link src 192.168.182.54
169.254.0.0/16 scope link
default via 192.168.182.1
1 of 2 configured routes for interface eth1 up
Please advise
--
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, or are watching someone who is.