@Enrico-Bermudez I had a similar problem after installing a cross-compiled image.
The way I got my Omega back to the standard image was as follows:
Downloaded the file omega-v0.0.5-b259.bin from http://repo.onion.io/omega/images/
Copied omega-v0.0.5-b259.bin to /tmp directory on my Omega
On the Omega, cd to /tmp
Run the command: sysupgrade omega-v0.0.5-b259.bin
This should have you back to a standard 0.0.5-b259 version of the Omega code image.
@Onion-Rings The firewall is currently configured to route traffic back and forth between the AP and the home wifi. To allow forwarding of packets between ethernet and AP, you first need to create a new network under /etc/config/network by adding the following block:
config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option hostname 'OnionOmega'
Then, you will need to go into /etc/config/firewall and add the wan interface (which you have just created) into a firewall zone named wan.
Simplying add `list network 'wan' to the following block:
option name wan
list network 'wwan'
#list network 'wan6'
option input ACCEPT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
Finally, you need to restart your network and your firewall with the following commands:
Then your router should be able to route packets between eth0 and AP.
The way you disable AP through commandline is by using the following command (assuming your AP network is interface number 0):
uci set wireless.@wifi-iface.disabled=1 ; uci commit ; wifi
And to enable it again, you run:
uci set wireless.@wifi-iface.disabled=0 ; uci commit ; wifi
Hi Harshad, your BLE as part of your Kickstarter reward should have been shipped out already. Please open a support ticket here and we will look into this further: https://onion.freshdesk.com
@Boken-Lin Thanks - that information clarifies things. Thanks
Look forward to future developments in relation to generating Omega specific images - it would be a good thing - mainly to make life simpler.
however, i am now successfully building packages for the Omega which I can install using opkg so am currently happy with what we have
Hi @Josh-Rosenthal, you can actually change the IP address of your Omega to something else to avoid conflict with your router. Just edit /etc/config/network, you should be able to find a block that looks like this:
config interface 'wlan'
option proto 'static'
option ipaddr '192.168.3.1'
option netmask '255.255.255.0'
And all you need to do is to change where it says 192.168.3.1 to something else that plays a bit better with your router.
Please let me know if this works!
Sorry - the list of usable pins was supposed to read "0, 1, 6, 7, 13, 14, 18, 19, 23, 26". These are also the only pins clickable in the Console's GPIO Tool, along with pins 8 and 9, which while clickable they resort to Direction: Output and - respectively - Value: 1 and Value 0. Are schematics for these modules available anywhere for the community? These would help immensely!
Thanks for the reply. The device must indeed have been running some processor-intensive stuff, though I don't know what! I have not yet figured out how to run anything yet, and the device was well past boot-up. Since the thing only acted weird that one time, I'll consider it a fluke.
Apologies for the delay, we're still a fairly small team so depending on support ticket volume or spikes in requests, we can be swamped at times. Rest assured, if it's in the queue, we will get to it asap.