I also ran into this problem with a remote connection to my Omega. You should write not "local", but the IP address of your Omega in the network.
For example, SSH root@omega-ABCD.192.168.3.1
UPDATE: I am now able to access the Onion's browser interface (I apparently had to go through the set up again .. only I skipped the Wifi configuration part this time). Also -- I am now able to access the SD card.
SIDE NOTE: I wish there was some indication that software is installing in the background when I choose to install the console during the setup wizard. The installation takes a while and it'd be nice if the LED on the onion would blink in a specific pattern or something so I know something is happening.
However .. these problems still remain:
I am only able to connect to the device via SSH when I am connected to the Onion's Wifi hotstpot.
I am only able to access the onion's browser interface when I'm connected to the Onion's Wifi hotstpot.
I use to be able to access the Onion's web interface using it's unique hostname (ie: http://omega-XXXX.local/) .. but I now no longer able to do that (regardless as to whether or not I'm connected to the Onion's Wifi hostpot). And yes .. I do have the Bonjour service installed and running (I'm on a Windows 10 PC).
Any idea as to why I'm no longer able to access the Onion while connected to my home's Wifi network? I've been trying to using both the hostname and the IP address and it never resolves.
Btw -- I've confirmed that my Arris Wifi Router is using the expected WPA2-PSK (AES) encryption.
Same issue as most people here with the ugpio/ugpio.h error. You a major problem in continuity with your documentation and is seems like it should be an easy fix. As others have expressed, this is very irritating. Please fix
I have figured that Onion will not talk to itself, no idea why. However it is not able to read anything from the /dev/ttyS1 even tho the attached Arduino sends text to the serial port which I can see with screen command. When I loop both the read and both the sending, I can see the sent string from arduino on the onion "screen" command, although with half the rate Im sending it, but still the Onion is unable to see it. I am slowly going mad above this, please help!
from the output of opkg --help you can see this information:
Use <dest_name> as the the root directory for package installation, removal, upgrading. <dest_name> should be a defined dest name from the configuration file, (but can also be a directory name in a pinch).
So, I edited my /etc/opkg.conf adding a dest name called opkg_test for /tmp folder; My etc/opkg.conf now is:
dest root /
dest ram /tmp
dest opkg_test /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
option check_signature 1
Then, I've copied a package (transmission-web_2.92+git-4_mipsel_24kc.ipk) in /tmp/ to make a test, and launched opkg this way:
I've found this topic from @Maximilian-Gerhardt (Thank you for your excellent guide), explaining how to build kernel module for Omega2. I've found this in his topic:
It conveniently compiled the hello-world.ko file and even created an ipk package.
Unfortunetly, trying to installing that package will give you a kernel mismatch error
because the kernel hashes differ (see this link). Loading the .ko file directly will still work though.
So, I'm able to compile the kernel modules I need (copying the .ko files in /lib/modules/4.4.74/, but the ipk still does not match.
Any suggestions to compile ipk kernel modules for official firmware?
@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.
Looks like your connection to Community was lost, please wait while we try to reconnect.