Hi @Luis-Johannes-Schubert, we haven't tried connecting USB WiFi adaptors to the Omega because we haven't found any need to do it yet. If you want to connect it, just keep in mind that you will need to compile the kernel-drivers into the firmware. We have removed all the drivers for additional wireless cards in the firmware to save space (assuming that the on-board WiFi would be enough for most applications).

Hi @Enrico-Bermudez, yup, you will be downloading the .bin file you created from step 6. Usually, if you have python installed on your computer (that's doing the cross compilation), you can run the following command to start a simple HTTP server to serve the files:

python -m SimpleHTTPServer 8080

You can also change the port to whatever you want. This command will serve your current directory to the public web, which will allow you to do wget on the Omega to download the firmware image.

Took me a while to get it to work.
Since I created my cross compile environment on Ubuntu Linux VM on my MacBook Pro (using VMware Fusion), how the VM is networked can affect how python's SimpleHTTPServer will behave.

I kept getting a "Connection refused" when I tried to access the SimpleHTTPServer from the omega.

How I fixed it: Changed the VM's network setup from NAT to Bridged. I did this by going to the VMware Fusion's dropdown menu: Virtual Machine --> Network Adapter --> Bridged (Autodetect)

By putting the VM on a Bridged setup, it picks up a separate IP address from the local wireless router.

Then in my omega, I used that IP address to wget the file I needed from the cross compile environment.

Thanks, @Boken-Lin ! I learned a lot from that.
Now off to flashing my omega!

@Boken-Lin I'm having a problem downloading because I still need to setup my omega's wifi connection. Tried many online tips, but no luck.
Can you tell me what my /etc/config/wireless should look like?

I finally figured it out. So flashing the omega with the .bin file from the cross compile environment led me to a situation where I didn't have any wifi connection. So it was impossible for me to wget the official onion omega image. And doing the factory reset doesn't bring it back either.

So starting from the cross compiled image on the omega, here's how I setup the wifi connection... which is the first step to bring back the onion omega standard image.

Then I added these lines in /etc/config/network to setup the wwan interface:

config interface wwan
option proto 'dhcp'
option ifname 'wlan0'

The final step is the key. Run this command to get a specific IP address (edited 12/29/2015):

ip addr add 192.168.1.147/24 brd 192.168.1.255 dev wlan0

After going through the steps described above, I was able to ping local devices. Then I was able to wget the .bin file.

wget http://repo.onion.io/omega/images/omega-v0.0.5-b258.bin

Then flashed the omega with the .bin file.

sysupgrade omega-v0.0.5-b258.bin

Now the problem is that there are still missing components such as the wifisetup and the oupgrade commands or scripts that originally came with the omega.
I'm going to start a new forum discussion since this is outside the current thread's subject.

Hi @Enrico-Bermudez, that's very strange. If you are flashing on a default factory image, it should contain all the commands such as wifisetup and oupgrade. Are you accessing the terminal using the Console app or through SSH or through the serial terminal?

root@OpenWrt:/# wifisetup
/bin/ash: wifisetup: not found
root@OpenWrt:/# oupgrade
/bin/ash: oupgrade: not found

It seems that when I factory reset the omega, it just goes back to a clean version of the cross-compiled bare bones openwrt OS. Network and wireless are reset, and none of the omega packages installed.