Posts made by Johannes Zellner

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.

I've /etc/config/wireless included in /etc/sysupgrade.conf to preserve wireless settings across system upgrades.
Nevertheless, after an upgrade /etc/config/wireless is changed.
Interestingly, it still contains some of the settings, especially...

• if I turned off the wireless AP before the upgrade, it's still turned off after the upgrade (which is what I want)
• the key of the wireless network which should be connected is still correctly in /etc/config/wireless after an upgrade

But: the essid in the wireless settings is set to some default (the omega hostname I believe). As the essid is wrong, the omega won't connect to the wireless network after an upgrade (even though the omega still has the correct password).

Any ideas what to do to preserve all wireless settings, including the essid of the wireless network to which the omega should connect?

you can edit /etc/rc.local

For windows see https://code.google.com/p/win-sshfs/
or http://igikorn.com/sshfs-windows-8/

@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.

see https://community.onion.io/topic/130/debrick-with-serial/
and https://community.onion.io/topic/157/reflash-omega-without-ethernet/2

From a linux computer you can mount the omega via sshfs -- this needs openssh-sftp-server to be installed on the omega.
Then you can work with your preferred editor of your choice on the mounted files.

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,

seems that omega with dock is 30% off today.
Is this also valid for plain omega w/o dock?

@Boken-Lin sure — feel free to put it in the Wiki. I'd be glad if it it's helpful for others.

1. I'd configure the router to assign the same ip to the omega always. No need to change anything in the omega then

2. If you really want to do it in the omega, you can configure a static ip instead of using dhcp. Have a look in /etc/config/network and /etc/config/wireless. You probably have to change the wwan entry in /etc/config/network to use option proto 'static' instead of option proto 'dhcp' — see the examples in /etc/config/network (just a guess, I didn't check this).