I guess I should get proactive and create a secondary SSID /w WPA. Speaking of which-
How does the glowforge handle routing? i.e. If I am on VLAN A and the Glowforge is on VLAN B is the plug-in/web app going to throw a fit during the setup phase? From everything I’ve read, ALL traffic from the GF is WAN bound. (Client > Internet > “Cloud” > Internet > Glowforge)
Normally there would be a ‘Advanced Configuration’ dialog box so you can specify the IP- But in this case (Since the GF does not have a display) that’s not really possible. Since the device discovery process has not been discussed nor mentioned, I am going to assume that the Webapp/Plug-in scans the local subnet for a 'Forge or the 'Forge creates a ‘hotspot’ in which you connect to it, Then configure it in a adhoc scenario. If that’s the case then inter-VLAN operations should not be an issue.
So basically the question is do you need local discovery at first for the setup process? (i.e. MDNS or the likes?) Then afterwards it relies on the cloud for all operations? Or there is an adhoc tool you use to configure a blank 'Forge where it pairs to the SSID of choice then starts chatting with the GF Cloud?