@Zheng-Han : you're my hero! I just restored my bricked omega by connecting it via ethernet with a second omega. I built the network connection beween the two omegas just exactly as you suggested on a breadboard and it worked out of the box. Thanks a lot!

Here are the necessary steps after wiring the network connection:

• boot the good omega -- let's call it omega-good
• connect the bricked omega (omega-bricked) with an USB cable with a linux pc (expansion switch still off)
• connect to omega-bricked with screen /dev/ttyUSB0 115200
• power on the switch of the expansion board of omega-bricked and immediately hit enter in the screen session to get into uboot on omega-bricked
• printenv in uboot on omega-bricked shows that the ethernet ip is configured to be 192.168.1.1
• configure the ethernet connection of omega-good to use the static ip 192.168.1.100, either by modifying /etc/config/network and restarting the network or by something like ifconfig eth0 192.168.1.100 up
• from uboot in omega-bricked verify with ping 192.168.1.100 that the network connection to omega-good works
• from uboot in omega-bricked start httpd
• create ssh tunnel from the linux pc to omega-bricked via omega-good with ssh -L 8080:192.168.1.1:80 omega-good (ssh connection to omega-good is via wifi)
• open http://localhost:8080/ in a browser on the linux pc. The ssh tunnel redirects this to the httpd of omega-bricked → you see the uboot httpd upgrade page in your browser and can proceed to upload a bin image.

yeah, creating an ethernet connection does also work with one omega and half of the circuit diagram in https://community.onion.io/topic/130/debrick-with-serial

Hi,

it seems that I bricked my omega while upgrading.
Is there a way I can debrick with a serial connection?
I already managed to get into uboot with a serial terminal, but I don't know what do do next w/o ethernet expansion.

If it's not possible w/o ethernet expansion:
Can I just connect the four omega pins rx-, rx+, tx-, tx+ to the corresponding pins of an ethernet cable to get an ethernet connection?

@Lazar-Demin thanks, works nicely.

@Karan-Magdani this ssems to be a common problem unfortunatley. I also broke one.
You can still switch it with something sharp as a needle or a knife.
I left mine in the state on and power off and on by connecting and disconnecting from the power supply.

Hi,

I followed https://wiki.onion.io/Tutorials/Using-Omega-As-Wifi-Range-Extender to configure the omega as a wifi range extender.

But: apparently it works only if I configure the omega subnet to be different from the wifi network the omega connects to:

• omega wifi connects to 192.168.178.x which is my main network with access to the internet
• omega ap configured with 192.168.181.1

Any device which connects to the omega access point then gets an IP from the omega's ap subnet (192.168.181.x) by the omega's dhcp. Disadvantage: devices which connect to the omega's subnet can't reach the main subnet and vice versa.

My question: is it possible to give the omega access point an ip (and subnet) within the network it connects to? The dhcp server of the main network (192.168.178.x) should then serve the IP's for all devices and there would be no need for the omega to serve IP's by dhcp at all.

@Lazar-Demin thanks, works nicely.

@Lazar-Demin seems that tmux is still not present in the latest releases of the firmware.
I'd be really interested to get it back in.

removing it from the standard firmware but having a package for opkg would be perfectly ok for me.

Hi,

tmux seems to be missing in the latest 007 firmware.
Very inconvenient to me
Any hints how to get tmux back?

@Janus-Sanders oops, I'm very sorry about that. But...

1. I can't really believe that installing a package "crashes" the omega so that it needs a factory reset
2. openssh-sftp-server is the package you need for sshfs

I use sshfs with the omega since a few months w/o problems and with different versions of the operating system (currently b266).

did you

opkg install openssh-sftp-server

@Sawyer-McBride what happens if you ping from uboot to any other computer in your subnet?

@Sawyer-McBride in uboot, you can use setenv to use an ip address which is within your (private) subnet. You can also check in uboot with ping that another computer in your subnet is reachable.

@Boken-Lin thanks, I did that with /etc/config/wireless, but nevertheless, it get's overwritten.