non-WiFi access
Posted: Wed Nov 12, 2014 11:35 pm
I have several VoCores and I have sort of bricked one of them. I tried to connect it to my home WiFi network, without success. Unfortunately this left me unable to use the WiFi interface to fix the configuration. Even more unfortunately, I can't connect SSH or HTTP to the Ethernet interface to fix the configuration from there either, although the interface is up and has DHCP-ed itself an IP address. I guess the VoCore's firewall may be blocking the incoming traffic, but I'm not familiar enough with OpenWRT to be sure about that.
So this leaves me with a few questions:
How can I manage my 'broken' VoCore without using the WiFi AP?
If the answer is that I can't, is there any way to do a 'reset to factory defaults' on it or similar, to re-enable the WiFi AP mode after I have accidentally turned it off?
On a VoCore that I can manage via its web interface and SSH, via WiFi, how can I configure it so I can also manage it via the Ethernet interface? This would save me from making the same mistake with any other VoCores.
Really wishing I hadn't sawn off that branch ...
So this leaves me with a few questions:
How can I manage my 'broken' VoCore without using the WiFi AP?
If the answer is that I can't, is there any way to do a 'reset to factory defaults' on it or similar, to re-enable the WiFi AP mode after I have accidentally turned it off?
On a VoCore that I can manage via its web interface and SSH, via WiFi, how can I configure it so I can also manage it via the Ethernet interface? This would save me from making the same mistake with any other VoCores.
Really wishing I hadn't sawn off that branch ...