If it seems that your build system configuration isn't matching the firmware that we build, it might be because when ./scripts/feeds is run, it overwrites the .config file. To remedy this, you can just run git checkout .config (assuming you're using our github repo or docker image).
As for packages failing to build, we've seen this happen as well but only when running our Docker image on a windows machine. If the Docker image is running on Linux or Mac, there's no issues. (Haven't had the cycles to figure out why it doesn't play nice with Windows)
Basically, instead of connecting the Omerga2's Ethernet port to a Modem, it's connected directly to a Web Server with a static IP. See attached diagram.
I can connect my phone to the AP, but when I type in the web address (192.168.1.250) I get a message saying can't reach that page.
tor v0.2.9.10-1 This package contains the tor daemon.
tor-gencert Generate certs and keys for Tor directory authorities.
tor-geoip This package contains a GeoIP database mapping IP addresses to countries.
tor-resolve Resolve a hostname to an IP address via tor.
I have read this conversation before posting. At that time, I didn't catach the information.
Now, I read carefully again, it is clarified that "omeag 2 (openWRT) AP's client limitation is 253."
Thank you for your reminding.
Here is how I understand how is configured the Network Topology when the Omega(2) is used as a WiFi Access Point. Since a picture is worth a thousand words, here's a graph I picked up on the net, and commented using an example of possible IP addresses.
As can be seen, Internet can go back and forth through the Omega(2) to support the WiFi sub-network. If the Internet traffic requested by the WiFi sub-network is too much to bare, the Omega(2) will clearly become the bottleneck, thus limiting the number of WiFi users that can benefit from an acceptable Internet speed.
Looks like your connection to Community was lost, please wait while we try to reconnect.