Hi,

What I want should be quite simple, yet I am unable to get the thing (Omega 2) working to my satisfaction.

I understand that OpenWRT is meant to be a router distribution, but I want to use the Omega2 in an IoT setting. So:

• I do not want dnsmasq in the way.
• I do not want a fancy firewall, best left to a router
• I want just 3 straightforward network interfaces
  • loopback (no problem here)
  • wifi connecting as a client to my SSID using the required password
    and configured via dhcp (including dns, ntp, routes and whatever
    option is set by the dhcp server
  • ethernet in a config similar to that of wifi

The wifi and ethernet should use SLAAC for IPv6 configuration.

This really should be a easy thing, and I have done it countless times on Linux boxes, yet I have not succeeded so far on the Omega 2. I've tried modifying the files in /etc/config, I looked at board.js (Why define the proto there???) ... but to no avail. I did not understand where apcli0 was defined even when there was no mention of that interface in the config files. I also got it to not appear when it was defined.

In a word, I am stymied! Help please.

Hi,

here is what I did.

I put my Omega2+ on an expansion board.
Connected through serial
Booted
On a USB drive copied omega2p-v0.1.9-b159.bin
Copied the file to /tmp
Ran sysupgrade omega2p-v0.1.9-b159.bin

It all seemed to go well, I got the prompt back, so I decided to move the chip to a Power Dock. When
moving the chip, it did seem a bit hot.

Booted the omega2+ with power dock and I could ssh to it.

A couple of hours later, the chip was not responding. When I touched the chip it was burning hot, you
could not touch it more than a fraction of a second.

Moved it back to the expansion dock... still dead and getting to hot to touch.

The docks are working fine with other chips.

There are no obvious shorts on the chip, and it was working OK before the sysupgrade

Any idea what went wrong?

TIA

Did you use

   -o rw

when mounting?

Or specify the option rw in the fstab file.

May be I should add that I got to this point

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen ...
link/ether 40:a3:6b:b3:a7:0d brd ff:ff:ff:ff:ff:ff
inet6 fe80::42a3:6bff:feb3:a70d/64 scope link
valid_lft forever preferred_lft forever
3: ra0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen ...
link/ether 40:a3:6b:b3:a7:0e brd ff:ff:ff:ff:ff:ff
inet6 fe80::42a3:6bff:feb3:a70e/64 scope link
valid_lft forever preferred_lft forever
4: apcli0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN ...
link/ether 42:a3:6b:00:a7:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 brd 192.168.0.255 scope global apcli0
valid_lft forever preferred_lft forever
inet6 fe80::40a3:6bff:fe00:a70e/64 scope link
valid_lft forever preferred_lft forever

With resolv.conf being set correctly and routes too. But, no SLAAC, and the wifi is split over 2 interfaces. The SLAAC is by far the most important. Plus the state is "UNKNOWN" which is kind of weird

Hi,

What I want should be quite simple, yet I am unable to get the thing (Omega 2) working to my satisfaction.

I understand that OpenWRT is meant to be a router distribution, but I want to use the Omega2 in an IoT setting. So:

• I do not want dnsmasq in the way.
• I do not want a fancy firewall, best left to a router
• I want just 3 straightforward network interfaces
  • loopback (no problem here)
  • wifi connecting as a client to my SSID using the required password
    and configured via dhcp (including dns, ntp, routes and whatever
    option is set by the dhcp server
  • ethernet in a config similar to that of wifi

The wifi and ethernet should use SLAAC for IPv6 configuration.

This really should be a easy thing, and I have done it countless times on Linux boxes, yet I have not succeeded so far on the Omega 2. I've tried modifying the files in /etc/config, I looked at board.js (Why define the proto there???) ... but to no avail. I did not understand where apcli0 was defined even when there was no mention of that interface in the config files. I also got it to not appear when it was defined.

In a word, I am stymied! Help please.