I have two Pi-3s.
The elder is running Linux rbpi3 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux.
The newer is running Linux porta-pi 4.4.22-v7+ #912 SMP Mon Sep 26 19:04:59 BST 2016 armv7l GNU/Linux.
My home network is a bit of a kludge. My router is provided by my ISP and I am using an older retired actiontec router sans WAN is connected via ethernet to provided wifi access at opposite sides of my home. Wifi is configured to use MAC filtering on both routers. I use DHCP reservations to give each device that is allowed to connect a fixed ip4 address, allowing me to use hosts files to address devices by name when needed. The DHCP server runs on the WAN router that serves as my gateway to the internet. The other router effectively acts as a bridge to the gateway via the ethernet cable that connects them.
This arrangement has worked well for me for some time now. The elder pi-3 is able to log in and obtain it's ip address from either router. The newer pi-3 is able to obtain it's ip address only from the gateway but fails to get an ip when it connects to the bridge router.
The wpa_supplicant.conf files are effectively the same, except that the newer has and entry for the gateway router.
Anyway, I am at a loss as to how to resolve this. I really need to be able to connect to the bridge router and get an ip because of where I need to physically locate the pi.
I'm thinking this might have something to do with recent changes in pixel raspbian. Any help welcome