If you want to create a LAN-to-LAN connection, that means that R1 must be on the the same subnet (192.168.2.0/24) as your OpenWrt router.
I understand the physical goal of your network configuration, but can you explain why you want to do this? Why do you want to have R1 in the system (what functionality does it provide)?
As @psherman said, if you want them LAN to LAN then they should be on the same subnet (I world stick to the default of 192.168.1.1 for OpenWrt though, and make R1 192.168.1.2, but this is only a personal preference). You would also want to disable DHCP server on one of them, usually the second one but doesn't have to be it. In LAN to LAN setup you have access or of the box unless you changed something with VLANs etc.
If you meant LAN to WAN, as your IP suggests then you would need to handle that on R1, as its firewall works typically block access from the WAN side unless you allow it.
A side note: it appears that you misplaced the PPPoE text on the OpenWrt router.
R1 features a special tool for PS4/XBOX matchmaking (Geofilter) that filters a region for the possible clients.
My goal is to combine OpenWRT's QOS with this tool.
Furthermore 192.168.88.x is locked and cannot be changed. @Hegabo PPoE is on the OpenWRT router the pic is accurate.
You could create a VLAN on your OpenWrt box. Give that VLAN a static IP (such as 192.168.88.2, assuming that is not taken and not part of the DHCP range for that network). Make sure you do not enable a DHCP server on that network. Create a new firewall zone for it, and then allow forwarding from the LAN firewall zone to the the new zone.
EDIT: Should have mentioned that you'll want to assign one port of the switch to be untagged for the new VLAN (and off for the others), and then use that port for connecting LAN - LAN between the routers.
What keeps you from just entering http://192.168.88.1 from your browser as is?
Also, people often get confused about this. An IP address doesn't belong to a machine, it belongs to a network interface. Any router must (by definition of the fact that it's a router) have at least 2 network interfaces and at least 2 IP addresses (one for each network it's routing between).
It could be useful to put all the IP addresses associated with each machine on your diagram, in which case it will become more obvious what to do I think.
From the diagram, I am pretty sure that the Playstation is double NAT'd. The issue is that the 192.168.88.0/24 network is the LAN of R1, but the WAN of that device is connected to the 192.168.2.0/24 network The PC sits on the .2.0/24 network as well, and the firewall of R1 prevents access to the router admin page.
But, with that said, it may be possible to set R1 to allow remote administration via the WAN. Normally this would be a bad idea, but since R1's WAN is actually part of the OpenWrt network, there is no security issue there.
@Sgt_Greco - check the admin page of R1 to see if there is a remote admin option, or if you can adjust firewall rules such that you can enable access from the WAN. Then you would just type in the address of R1 as it appears on the 192.168.2.0 subnet.
In almost every circumstance, I would agree about this. However, according to the OP, it appears that the router performs some functions that affect geofiltering (bypassing geofilters? Maybe it is a VPN or some other tunneling technique; I don't really know since I don't have any interest in video games). But regardless, I think that the traffic must be routed through R1, so I think that the NAT is important here (strictly speaking, a router can still route without NAT, but practically speaking turning off NAT turns the device into as switch).
I am not sure what the purpose is either but I suspect it may do something like serve special DNS records so that the game server with the smallest ping is always chosen by the PlayStation or it may firewall certain "bad" servers so the PlayStation gives up trying to connect to them and chooses a "good" one...
those kinds of functions don't require NAT. in fact routing without NAT is the norm, NAT is a hack. the R1 device doesn't become a switch, it still likely provides DHCP and DNS and possibly QoS to the gaming machine... turn off the NAT. Most likely the OpenWrt machine will need a static route so it can know where to send packets destined for 192.168.88.0/24
This is true on both accounts. But if you think of stock firmware for pretty much any consumer router, I don't think there is a way to disable NAT. We know that we can disable NAT via the masquerading option in OpenWrt, but there are many firmware releases that probably don't have an accessible switch to turn on/off masquerading. We don't know what firmware is on the R1 device and we don't know if NAT can be disabled directly on that firmware.
Yes. I also used to be confused but now I know better. I tried entering 192.168.88.1 but it didn't work the same work it did with my 192.168.0.1 modem (OP pic) . Don't know why. Maybe because Modem-OPENWRT
is WAN-LAN and I created a correct Interface and OpenWRT-R1 is LAN-LAN. Or maybe because R1 was blocking me. I'm on it.
Double NAT is at the back of my mind and it's a big problem indeed, but for now I'm just trying to access R1 via my PC. If it occurs I'll deal with it later.
I'm afraid there is no such option. Misc settings are as the picture I posted above.
WAN settings are as picture below.
Try undoing your vlan setting for the moment. Then enable the option for admin access from the wan. From there, figure out the wan address of the r1 unit (it will be in the 192.168.2.0/24 network - if you don’t know what it is, you can look at the openwrt dhcp lease page or maybe on a status page of the r1 device). That should do what you want.
I honestly don't know what you should do. DMZ may not really affect much unless the R1 router is opening ports (i.e. for inbound connections). My guess is that it shouldn't be necessary, based on the fact that you never said your gameplay was problematic. Your original request was just to have access to the admin page of the R1 device -- so enabling the remote admin feature should provide that capability.