Quaker Fang writes: > # ifconfig ath2 > ath2: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 2 > inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255 > ether 0:f:b5:a8:6b:8c > --> flag <UP> seems not correct here, since it has never connected to > any AP until now.
"UP" has nothing to do with an AP connection. The "UP" flag is an administrative flag saying that IP can use the interface. It's the "RUNNING" flag that indicates whether the underlying connection exists. On a wired link, it tells you whether the cable is connected. On wireless, it tells you whether the AP is connected. In this case, it's not, because "RUNNING" is missing. It's unclear to me why "UP" is set, the address is 0, but "DHCP" is not set. That's a strange state, and I'm not sure what would cause it. (Meem recently changed dhcpagent so that it marks interfaces as "UP" while the address is still set to 0. This is part of the change to make DHCP use sockets rather than DLPI. But if that's what was setting "UP" here, then I'd expect that "DHCP" would be set.) > # dladm connect-wifi -e DWL-2000AP ath2 > # ifconfig ath2 dhcp > --> Timeout always, no success Well, that's not good. > Check output of snoop, there are "DHCPREQUEST" packets out, but no > response, looks like driver's problem, > but by wireless sniffer tool, in section of ieee80211 frame header, the > BSSID field is all zero, not BSSID of DWL-2000AP, Ouch! > this is not correct. This mean when ath2 connected to AP, driver calling > "mac_pdata_update()" has no effect > to IP's fastpath header, it keeps old one. The BSSID is in the fastpath header?! OK, I can see how that'd be related to a lack of communication. > # dladm connect-wifi -e ap7-3 ath2 > # ifconfig ath2 dhcp > --> Timeout always, since no reponse from DHCP server > By sniffer tool, we can see, BSSID field of frame header is always old > one (DWL-2000AP), NOT ap7-3's. > This means mac_pdata_update() has no effect to flush IP's fastpath header. > > Thoughs? Sounds like a good bug to me. -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
