UPDATE:Forum contributor jeff pointed me in the right direction with his explanation and as a result I finally ended up going through some more OpenWrt documentation. Therein I found the exact networking scenario I was seeking.
What I am trying to do here is known as a "Routed Client" using the Routed method rather than the Masquerade method.
This network scenario and how it is implemented is detailed on this document --
https://wiki.openwrt.org/doc/recipes/routedclient
So, while have as yet to get this scenario up and running, it is the solution I seek.
Thank you jeff.
(Old Post)
This an extension of and correction to "Pseudo Client Bridge No Can Do" wherein I did not properly state the task at hand. Pseudo Client Bridge No Can Do
What I want to do with OpenWrt on a WRT1900ACS V2 router is easy to implement using DD-WRT, but I can find no similar example using OpenWrt. I say special only because, evidently, it is not the usual thing folks do using OpenWrt although this implementation is SOP using DD-WRT.
.
.
NETWORK SCENARIO (easily implemented using DD-WRT)
There are two independent local area networks connected by radio -- 2NET and 1NET.
** 1NET has a connection to the internet.
** CB1 is the Client Bridge that connects 2NET to 1NET via radio.
** The wired side of CB1 is a LAN switch and is part of 2NET
** The radio of CB1 IS A DEDICATED POINT-TO-POINT RADIO CHANNEL to 1NET as a client
** No other wireless connections are possible to CB1.
** The only wireless connections available on 2NET are made via AP1 which is wired to CB1
NOTE: This is NOT the usual relay scenario. Perhaps to best understand this scenario see the ADDENDUM at the bottom of the page
.
.
2NET------------------------------------------------------------------------------------------------------------------1NET
Wireless Access Point AP1
192.168.2.11
|
|
(wired to)
|
|
Client Bridge CB1 LAN/WAN
192.168.2.1/192.168.1.2----------------which is a static IP wireless client of------------------192.168.1.1
.
.
Using DD-WRT, CB1 is thus configured (pertinent details only) --
CB1 WAN SIDE (wireless side)
WAN Connection Type---Static IP
WAN IP Address-----------192.168.1.2
Gateway-----------------------192.168.1.1
CB1 LAN SIDE (wired side)
Local IP Address-----------192.168.2.1
DHCP (local to 1NET) is turned on and serves a block starting at 192.168.51
The 5Ghz radio is disabled and the 2.4GHz radio is enabled as a Client of 1NET.
The radio side (WAN side) of 2NET is part of 1NET and so has the same SSID.
TO REITERATE: The CB1 radio is a dedicated point-to-point channel to 1NET. It does NOT serve as a 1NET relay. No other device can connect to the CB1 radio.
RESULT: The two LANs are COMPLETELY independent. The only thing shared is that 2NET is allowed access to the 1NET's Internet connection, and that is all.
This is what I want to do with OpenWrt -- make CB1. To repeat, it is very easy to do with DD-WRT but I cannot get is to work on OpenWrt. I do not believe it is impossible or even difficult. I must be missing something obvious.
Any recipes using LuCI to implement this CB1 scenario?
UNUSED CB1 WAN PORT
Since the wired Ethernet WAN port is unused on CB1 I would like to assign it to the LAN switch. This is easily done using DD-WRT by simply checking the Assign WAN Port to Switch check box. How would this be done on OpenWrt if it can be done?
I would rather not be forced to revert to DD-WRT as the only way to implement this netork scenario.
If I can pass this basic make-or-break hurdle, I'm all in for OpenWrt. If not, then, well, its back to DD-WRT.
.
.
ADDENDUM
Again, please note that this scenario is NOT the usual OpenWrt relay scenario.
Borrowing from the Wifi Extender or Repeater or Bridge Configuration Map --
https://openwrt.org/docs/guide-user/network/wifi/relay_configuration
Note the IP addresses of the two Client Hosts in the left hand cloud.
In the scenario I want to implement the WIRELESS side of the Client Bridge is DEDICATED TO THE 1NET CONNECTION, no wireless Client Host can connect to it. So just cross out the two Client Hosts in the left hand cloud.
The LAN port (on this map 192.169.2.1) is wired directly to the AP1 (192.168.2.2) access point which provides wireless connections on the 2NET side.