> Still doesn't explain why it should work in 4.17 and not in 4.18, there > aren't a lot of wifi changes there at all. I just tested it with 4.15 and it didn't work. However, It works in 4.15 in other PC. At first these 2 PCs have the same packages with apparently the same version. The only thing I can highlight about the difference between them is that: (i) Ubuntu has been upgraded from 16.04 to 18.04 (it works fine up to 4.17) and (ii) Ubuntu 18.04 has been installed from scratch (it doesn't work at all - tested from 4.15). On Fri, Aug 30, 2019 at 5:22 AM Krishna Chaitanya <chaitanya.mgit@xxxxxxxxx> wrote: > > On Fri, Aug 30, 2019 at 1:02 PM Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > > > On Fri, 2019-08-30 at 00:35 +0530, Krishna Chaitanya wrote: > > > > > > Is this supposed to work at all? AFAICS, in hwsim channel matching > > > checks are only done in non-mediumd path (no_nl), and wmediumd also > > > doesn't have any checks? So, hostapd responds to all probe requests in all > > > channels. Am I missing something? > > > > Hmm. Interesting observation, I wasn't aware of that. > > > > That certainly explains the situation though - on 2.4 GHz we'd prefer > > using the DS Element, and thus not use the scan result, while on 5 GHz > > we assume that the reported RX frequency is correct (there's no channel > > overlap). > > > > Still doesn't explain why it should work in 4.17 and not in 4.18, there > > aren't a lot of wifi changes there at all. > Yes the git log also doesn't show any changes in this area. > > > > I guess we should fix that in hwsim, anyone esle want to? :-) > I can give it a try to move the channel matching logic to common > code for both nl and no_nl.
