I recently upgrade to the lastest 184.108.40.206.195, once the AP rebooted I suddenly could no longer login. The login screen would take the username and password, turn it to starts, and then just sit there and flicker. I had to factory reset to get back into the AP. SSH also would just timeout trying to login. Then I tried to re-setup AD login, and it would do the exact same thing. Then after ssh-ing in with local credentials I went to debug mode, and when I run "logs winbind 1" I get the following.
killall: winbindd: no process killed
sh: winbindd: not found
Was winbindd not put into this image?