As I’m reading through the documentation for the mesh devices and testing the setup of an Argon with Ethernet Featherwing everything seems to default to the ethernet featherwing being used as the uplink without an option to do use wifi as the gateway. Does anyone know if this will change? I was looking forward to using the ethernet featherwing to allow specialized wired devices to access a wireless uplink even if all addressing and routing was static. I could also see use cases for cellular redundancy for a wired network, and cellular uplink of a local wifi network. All that would be required is control of the routing tables as far as I can see. Is this planned or am I missing something? Is it happening soon…?
When Particle release the HA Mesh capabilities you’ll be able to have a Xenon with Ethernet FeatherWing and a Boron both acting as gateways. If the hard wired Xenon lost connectivity then the Boron would take over via GSM.
That’s the planned HA structure for Mesh so I do not see redundancy been implemented at the device level. Use Xenons with Ethernet FeatherWings as they’ll be the most cost effective.
What about being able to use the Boron as a gateway for a wired ethernet device. For instance, could I attach a wired IP camera accessible via a cellular gateway in the future? This wouldn’t be fail-over, in this case it’s just control over the gateway routing. That’s the behaviour I’m interested in.
I believe you’re asking if the Boron could be used to connect a wired IP camera to the internet? You would have to use a GSM router for that. The GSM/WiFi on Particle devices is designed for the device itself to use (with the exception been other Mesh devices) and cannot be used by other Ethernet devices.
JumpMaster is correct. The Boron cannot be used a cellular to Ethernet gateway. Not only is it not supported, the cellular modem in the Boron doesn’t have the necessary capabilities to route IP traffic effectively. Also, it’s really slow, not well suited for a camera (limited to a few K bytes per second).