Indeed, please make sure you have the gateway’s Traffic page in TTN Console open before making the node send its Join Request. It will not show traffic that was received before that page was opened in a browser.
Indeed; for future readers, this is one of those:
Above, the line saying “Received pkt from mote: D0025D52 (fcnt=46037)” is actually wrong, as the gateway assumes it’s a regular uplink and erroneously decodes the non-encrypted parts for its log. However, a Join Request is encoded differently (and includes neither a DevAddr nor a frame counter), so that first line can be ignored. The second indeed is a Join Request.
Even when the AppEUI, AppKey or DevEUI would not match whatever is registered in TTN Console, the gateway’s Traffic page would still show such Join Request, but no Join Accept. (The application’s or node’s Data page would not show it, if not matched.) The gateway’s Traffic page also shows packets that are for other providers, and are ignored. It should also show errors such as described in OTAA shows "Activation DevNonce not valid: already used".
As TTN does seem to accept the status messages, then if there’s really nothing in the gateway’s Traffic page, then I’d say that the gateway’s connection settings are fine. So, I’d say that indeed TTN is rejecting the gateway’s uplink messages for some other reason, like maybe the “nan”. (Nice find!)