Cannot ping devices in the same local network

[amoeder]

Pinging www.google.com is what I'm doing to determine if I can surf.
So unless there's something else I'm missing, I cannot surf from the OpenWRT when using a static IP

[LilRedDog]

I see no reason for that in the cat calls. OpenWrt should not care if you are static. I mean you did set the device as static in Openwrt, right?

In the status page find your device and click on static. save, save and apply.

[amoeder]

Umm I'm not sure that's available on this 3rd party module.
I am doing this with UCI commands from the command line

[LilRedDog]

You showed a screenshot of LuCI.

Or did I misunderstand the screenshot?

[psherman]

@amoeder

        "model": "Onion Omega2+",
        "board_name": "omega2p",
        "release": {
                "distribution": "OpenWrt",
                "version": "18.06-SNAPSHOT",

It would make sense to upgrade your device. 18.06 is very old -- it's EOL and unsupported. And the snapshot you are running could potentially have some bugs. For sure, there are known security vulnerabilities on 18.06, so an upgrade would be the best action.

https://firmware-selector.openwrt.org/?version=23.05.2&target=ramips%2Fmt76x8&id=onion_omega2p

@amoeder

For illustration purposes,

In your diagram, you appear to be running OpenWrt as a wifi client (sta mode). Is that correct? Are you trying to connect other devices downstream of that OpenWrt device (i.e. to another wifi AP and/or ethernet on the OpenWrt system)?

[amoeder]

Yes that's correct.
I am not running anything downstream of the OpenWrt device

[psherman]

Ok... thanks.

So that I understand your overall goal -- what is the purpose of the OpenWrt device on your network?

[amoeder]

It's collecting sensor data and posting to an https server

[psherman]

Great. This should be relatively easy, then.

Before we go further, it would make sense for you to run the upgrade to the latest OpenWrt... this way everything will be current and secure.

[amoeder]

Agreed I appreciate the update link.
What downloaded was a binary file.
I'm trying to find installation instructions

[psherman]

@amoeder

What downloaded was a binary file.

You'll want the sysupgrade image.

@amoeder

I'm trying to find installation instructions

Typically, the upgrade is simply handled by the OpenWrt sysupgrade features -- this can be found in the LuCI web interface as well as the command line.

That said, you may need to make some intermediate upgrades. Do not keep settings across any of these upgrades -- we'll configure from scratch once the upgrades are complete.

IMPORTANT: make sure you are connecting via ethernet to the OpenWrt device -- wifi will be disabled by default.

I'd recommend going through this upgrade path (possibly more than required, but less likely to encounter issues):

18.06 (current) > 19.07 > 21.02 > 23.05

Basically it is all upgrades except for 22.03 which we can hopefully skip. When you upgrade, you will see a checkbox that says "keep settings" -- deselect that so that the device resets to defaults. Links below... let us know if you get any errors or scary warnings. Some are safe, others might be risky -- if in doubt, ask here before forcing any upgrades.

19.07
21.02
23.05

[amoeder]

I'm assuming this can be done as a clean install of the latest version rather than upgrading 3 times?
I just want to understand my options as this will be for a customer product and this module was purchased from a supplier just a few months ago

[psherman]

@amoeder

I'm assuming this can be done as a clean install of the latest version rather than upgrading 3 times?

Probably, yes. I haven't looked at the details of how to install OpenWrt on your device. If there is a tftp server/client or similar method, you can probably jump directly to the latest using the kernel image, then once there install the sysupgrade to make it persistent. However, IMO, the 3x upgrades are the safest route.

[amoeder]

Is the ethernet required as part of this upgrade process or can I just load the binaries from a removable media?

[psherman]

@amoeder

Is the ethernet required as part of this upgrade

Wifi is disabled by default on OpenWrt, so yes, ethernet is required or you will not be able to access the router.

@amoeder

I just load the binaries from a removable media?

This could work the first time, but after that (with the default images), you won't have USB access. It is easiest to download the files to your computer, then use either the web UI or scp to copy the files to the router for sysupgrade.

[amoeder]

Ok I did the first update.
But things are weird now.
Many of the commands I used before are not available.
Not sure how to get my external drives mounted again.
And I cannot get ethernet to work.

[psherman]

@amoeder

Many of the commands I used before are not available.

You probably had some non-default packages installed on your device. What commands in particular (and also for what purpose -- knowing the commands and the intent will help us recommend the right packages).

@amoeder

Not sure how to get my external drives mounted again.

https://openwrt.org/docs/guide-user/storage/usb-drives

@amoeder

And I cannot get ethernet to work.

I just looked at the device you're using, and it looks like it a little module that needs an external network interface, is that correct? How does that connect and/or what is the information about the interface?

With all of these things, it's only worth doing the minimum necessary to allow you to get upgraded to the latest version. Each time you upgrade, any packages you have installed will be erased (they wouldn't be compatible anyway, you'd reinstall the packages once you're up and running).

[amoeder]

I didn't install any of the packages. They came pre-installed from the manufacturer of the module.
I found their list of binaries here:
http://repo.onioniot.com/omega2/images/

I'm sorry but I'm not going to troubleshoot this module any more. It would be cheaper for me to throw it away and buy another. This upgrade is too problematic for a production process. If I can update a single binary and have all the drivers intact, I will do that.

[psherman]

@amoeder

I didn't install any of the packages. They came pre-installed from the manufacturer of the module

Ah... I don't think you ever mentioned that you were using a vendor's fork of OpenWrt and that you needed to stay with their build (as compared to using official OpenWrt).

@amoeder

I'm sorry but I'm not going to troubleshoot this module any more. It would be cheaper for me to throw it away and buy another.

There should be no reason to do this... you can theoretically flash their build onto your device and have the device up and running again (generally speaking).

A few thoughts:

• if you can find out what packages they pre-install, it is possible that the same ones exist in the official OpenWrt repos. From there, it is absolutely possible to build a single/monolithic firmware image that you install with everything preloaded.
• if you use the vendor's images, you'll still be behind and on a fork that is not supported here (more on that later)... but at least you will be on a more recent codebase (looks like they are currently using 22.03, you were previously on 18.06).
• With their firmware, might end up in the same situation that started this thread -- it's impossible to know exactly what they do in their builds. Hopefully they have support or a user forum for helping their users resolve issues.

Elaborating on the vendor images not being supported here -- this is our boilerplate message to describe why it is not supportable here on the official OpenWrt forums:

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

[ajmartinez]

I am running 23.05.03. and created a guest network, the Isolate Clients, is not checked, but I can't ping from my laptop wi-fi 2.4 Ghz network to my prone, but I am able to ping from my laptop on the 5 GHz different network to my prone on the 2.4 network.

Lapto IP on the 2.4 Ghz =
Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : lan
Link-local IPv6 Address . . . . . : fe80::ace8:5d69:99d5:6701%23
IPv4 Address. . . . . . . . . . . : 192.168.20.222
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.20.1

Iphone IP =
192.168.20.120

ping 192.168.20.120

Pinging 192.168.20.120 with 32 bytes of data:
Reply from 192.168.20.222: Destination host unreachable.
Reply from 192.168.20.222: Destination host unreachable.
Reply from 192.168.20.222: Destination host unreachable.
Reply from 192.168.20.222: Destination host unreachable.

Ping statistics for 192.168.20.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I will appreciate any help please.