On Mon, Jan 14 2019 16:41:13 +0200, Lauri Tirkkonen wrote: > > Indeed, my diff was bad as well. Thanks for spotting these issues. > > I hadn't run this diff yet cause I was still building a new snapshot > > to test it. Could you also test this new version please? > > I'm not currently physically near my AP, but the diff looks good and I > can test it later today.
I've had a chance to test your diff, and it seems to work well, but I have one behavior change I can't explain (haven't looked at packet captures at this point): without this diff applied, or with my own previous diff applied, I can run iperf3 -s on my Android phone and connect to it with UDP iperf3 -c from a wired host connected to the AP, and measure packet loss. With this diff applied I'm unable to connect to the phone's iperf server, and in fact am getting huge packet loss even pinging the phone (and it seems that the times that it responds to pings are correlated with times the phone was actually transmitting, eg. when I hit refresh in the phone browser). Maybe it could be a good thing, perhaps related to aggressive power management on the phone, but I don't know what it is with your diff that could cause this behavior change. Maybe I need to do some packet captures later. -- Lauri Tirkkonen | lotheac @ IRCnet
