@Liverpool20 

Ok wow that's something to take in.  They take a known tcp port and reuse it for a custom application rather than choosing another non used port? How in the heck is that considered the normal way to do things?

Back to focus - I will note the title of that faq is asking why port 22 is testing as OPEN Which I would expect, I suppose, if they are using 22 as their communication port.  However on my router port 22 is showing as filtered when it should show open if it is indeed listening on that port for the application.  Seems like that's a misleading road to go down since it's the exact opposite of my ports being closed.

If it is in fact listening on 22, how would I change or disable that?  I didn't ask for an app that would disable (wow super pc here tplink I cant even say cri**le my network cause it's offensive?) my use of my network.

I suppose I could change the ssh listening port or do some sort of port triggering.  Tho why I should have to change an established protocol for a custom app is beyond me. Wow

Anyway to answer your last question 32400 is not open either

 So I'm not sure where this leads.  This seems like a pretty big implementation error.  I went with tplink as it seemed to have a good reputation in the linux community so it's hard to fathon they would take something so integrated into the *nix world is crazy

I may simply have to return the router and buy something more intelligent.