Just want to see how much interest there is in allowing for small configuration changes via bluetooth and the mobile app in the event the WAN is down at a site. Such as changing the WAN IP on the Route10 and specifically to help address scenarios like those listed in the following topics:
I think internal Web interface for allowing small settings changes would be better that is accessible internally
I suppose that’s fair. I was trying to think of way to combine changing things locally with the controller still being where the router is expecting changes to come from.
This is not really feasible to the best of my knowledge, because your phone cannot run the controller software required to send configurations to devices.
What’s really needed is functionality to assign an interface as a craft/console/aux
This is a standard requirement for enterprise customers and on, if not, the product is dead in the water and an easy platform to disqualify.
If this ever were to become an option, it would certainly be optional, as physical/nearby access is obviously not sufficient basis to provide admin access to a device.
All Alta devices do enable a LL IPv6 address based on their MAC address by default, so even if it is having problems getting on the network, you can generally always get into them via ssh on the Link-Local (LL) IPv6 (provided you’ve set up an ssh key on the site). You can obtain that LL address by hovering over the IP address at the time the device is connected, and writing it down. You can derive the LL address from the MAC, which is more complicated, but does not require you to write down the address.
What about on new installs that occur within infrastructures that would have inter-lan only functionality?
You would need the switches to have the VLANs plumbed out, as expected, but as long as the switches are cognizant of the available VLANs, you can create VLAN interfaces on any Alta Labs device within Linux. You can use the vconfig command to create VLAN interfaces, and bring up the interface to then reach the LL address of the desired device. As long as you can ping6 the device, you should be able to log in to it.
In some cases, companies will deny WAN access to these aggregates which will live behind firewalls. So help me understand how one is to establish the correct VLAN configurations on your switches when your switches were designed by default to require connectivity to an orchestrator for issuing the commands? Are you positioning these products in tandem with your local containerized instance?
Yes, in this specific case, you would need to use a local controller to configure them.