Thanks for the reply @alzhao.
Nope. That’s not what I meant, sorry. Oh and no, this is the stock, “out-of-the-box” domino, as received in the post, from the Kickstarter campaign.
I have the WiFi set up in CLIENT mode. It connects to my local access point, no problem. Works fine.
The problem is that the WiFi completely shuts down if I unplug the Ethernet (eth1) cable. My expectation is that the WiFi client would remain connected to my AP, thus allowing access to the Domino solely over WiFi – with no Ethernet cable involved.
But as I said, the WiFi shuts down (disconnects, vanishes completely from all external perspectives) when the Ethernet cable is disconnected! Weird. When I reconnect the Ethernet cable (on eth1), the wlan interface fires up again, sends a DHCP request, gets an IP and comes back online just as it was before the eth1 cable was unplugged. Bizarre.
So – the wlan interface only works at all (in client mode) if eth1 has an active connection present.
Now, if the two interfaces were bridged, that might make sense. But they are not. Incidentally, that the only thing I have changed, using LuCI. The WiFi wlan interface is on wan0 (on its own) and eth1 is on lan (on its own +/- IPv6)
So in summary, it appears that wlan and eth1 are inexplicably “one way bridged” at some level. I should note that eth1 still works fine if the WiFi is disconnected, not configured or whatever.
I am assuming that if I had wlan configured as an access point, this would all go away. But that simply doesn’t suit my needs – far as I can figure, anyway.
Thanks for your time.