@Alexandr-Didenko You need kmod-macvlan loaded then you can configure multiple virtual devices with separate IPs.

@Lazar-Demin Per the textbook definition, distributed computational network.

Awesome @Lazar-Demin! I never thought to mess around with Firewall. I was trying to do everything through Network but this is awesome because the connection stays active but no traffic can pass through it. This means I can maintain a cellular connection but disallow traffic through it. This is perfect! Thanks so much for looking into this. I'll be sure to let you know how it works for me. Also I'll be putting together a python script to monitor internet connectivity through the interfaces and enable/disable them so I'll be sure to share that script for others.

So from what I can find it looks like the best way to do this is to set the disabled option property on the network interface. To switch to Cellular execute commands: uci set network.hologram.disabled=0 uci set wireless.radio0.disabled=1 To switch to WiFi execute commands: uci set network.hologram.disabled=1 uci set wireless.radio0.disabled=0 If there is a better way of doing this please let me know.

@Ian-Steele the boot time for an Omega is effected by a range of factors, number of modules loaded, services to be started, network connection etc., sd card read, file system check etc. My Pi3 is no faster. Adding a script to rc.local I would consider a bit of a hack, hotplug was designed for the task you asked about, but actually hotplug is deprecated in favor of udev but I haven't tried udev on Omega/OpenWrt.

@Lazar-Demin I tend to prefer to connect to the omegas through my router once they are connected to it, instead of through their own ap. In fact I just put up another thread asking what the correct way to disable the ap is because when I tried, the sta connection never would come back up once I disabled the ap one and Ihad to connect back via the ethernet expansion. I have a really good router but ended up buying little antennas to attach to the omegas. They have been working a lot better since then. The internal ones seem to be a bit lacking to me.

In your build system run: ./scripts/feeds update ./scripts/feeds install vnstat make menuconfig Select vnstat under the Network menu. Exit and save make Your vnstat can then be transferred to your device.

@Bartosz-Grabias there is a mention of that issue in a post in this thread by Lazar [4th post of thread] https://community.onion.io/topic/2809/new-os-release

@steve-burk I like Steve's suggestion for your own problem as it will absolutely work, but in the hope of making things needlessly complex, this is what I'd do: Create a shell script that is comprised of the commands you need to provision the route. In your installation script (you have one, don't you? ;^), check rc.local for a reference to the script. Insert a call to rc.local if it's not in there. Also in your install script, copy the route provisioning script to somewhere sensible, such as /usr/bin/. This directory is in the path and need not be "spelled out" in rc.local. Perhaps you could write a script that takes routes as a command line parameter. As such you could easily call the command multiple times from rc.local to configure multiple routes or perhaps better yet, pass along not a route but a config file path that contains the routes you desire. If the latter, you just mod the route config file and reboot - voila! If you're dabbling, this suggestion is overkill. If you're trending toward production, this is a bit more important and ought to be considered. Your mileage may vary. --Bill

Before going through the hassle of a factory reset and starting again there is another quick and simple way to get your wifi working: https://docs.onion.io/omega2-docs/first-time-setup-command-line.html Running the console after that is quite a bit faster

Finally found a solution: If you use your own custom webserver to setup the omega and want to display nearby Networks. <?php echo shell_exec("ubus call onion wifi-scan \"{'device':'ra0'}\""); ?> ^ This DOESN'T work! because: the php-interpreter doesn't have enaught ram to excute the command. It'll take a eternity. Solution: in /etc/php.ini set memory_limit form 8M to 32M memory_limit = 32M ; Maximum amount of memory a script may consume. now the scan only takes about 5sec.

Btw, why not just add procd service script (/etc/init.d/) script with START=99 and defined service_triggers() ?

Hi, You can use ssh to run command on another Omega. Example: sshpass -p "PASSWORD" root@REMOTE_IP COMMAND PASSWORD - default is onioneer REMOTE_IP - remote device address COMMAND - app/script etc. to run on remote device (you can use parameters to enable/disable relay)

Hi @Harold-Clements I have the same problem, but I have no answer that works see: https://community.onion.io/topic/1536/installing-samba-client-cifs https://community.onion.io/topic/105/anyone-was-able-to-install-samba-client-cifs

Strictly speaking, yes, you could probably throw small amounts of data at the unassociated access points, perhaps by abusing the joining protocol. Practically speaking, that will be useless, as they will ignore you or at best respond with errors - the data won't go anywhere useful. For things that are on the same access point you could use UDP broadcasts, but again, the other devices probably won't be paying attention to this traffic.