1) Gryphon doesn't have anything to do with that. Teamviewer and other products detect corporate use by seeing if the PC they are installed on is on a corporate domain, with a AD, and secondary they check for the IP address (statics, etc).1. Teamviewer has been working great for me on Gryphon, but recently I'm getting booted off randomly after just a few minutes and Teamviewer doesn't seem to like the way the traffic is being handled and labeled it as corporate usage. Tried Anydesk as well and the same thing happened. Is anyone experiencing this?
2. I have to send a wifi signal to a remote part of my property about a quarter of a mile to a location I use for AirBNB. I was thinking about replacing my Asus routers at both locations with Gryphons at both locations to gain better control over the usage but setting this up, to begin with, was pretty difficult (for me at least). I was wondering if Gryphon would be able to handle this (love my Gryphon but some of the lack of advanced features can be a bit frustrating). The device I'm using to accomplish my wireless bridge is the "Bridge-in-a-Box" by Cambium Networks. (Amazon Product Link for Specs). Any advice here would be great!
2) No clue on this, but really, it shouldn't be a problem because you can backhaul the mesh. I don't see why it wouldn't work. Although Gryphon lacks some of the prosumer features (they are coming) at this time, it still should work fine in most setups. Things like pointing the DNS to a local DNS server and such aren't options (yet). Neither are manual RRP and other things. Hopefully soon!
This last major firmware update was absolutely fantastic, so I have some confidence they will get it where it needs to be. I've recently seen Gryphon on the top 20 Home IoT stuff on Amazon so it looks like it's picking up steam. Also the reviews on it at third party tech sites have been really good.