That won't work. The wwan needs to be in WAN zone, so that it masquerade your internal network.
I am not sure about the relay bridge, as I have never used it. Could you post the output of the following commands to help us understand better the configuration, rather than posting screenshots? cat /etc/config/network; cat /etc/config/wireless; cat /etc/config/firewall; ip -4 addr; ip -4 ro; ip -4 ru
All the above in one line.
It seems to be done by the bridge, the command you've given me doesn't work ip doesn't know ls and ta.
But if I list all the routes:
root@OpenWrt:~# ip route show table all
192.168.2.56 dev br-lan table 16801 scope link
192.168.43.1 dev wlan0 table 16802 scope link
192.168.43.49 dev wlan0 table 16802 scope link
192.168.43.75 dev wlan0 table 16802 scope link
I was trying to do exactly the same before yesterday. wwan is in LAN zone as per the document. I got internet on client router as well as on some of it's AP client devices, but it appears that DHCP and/or DNS don't get relayed so I had to set them manually on the PC.
I am currently working on Achieving the same using trelay, but it's not well documented
I think that since the router itself is working and everything else not, it might be because the packets sourcing from the router use routing table 16800, while the others use different ones. But I need to see the contents of the routing table 16800 (the command I specified before, which doesn't work for you).
In your summary ip route show table all I don't see table 16800 at all, as well as no default gateway.
16800 seem to be the loopback device
The default is 16802
192.168.2.56 dev br-lan table 16801 scope link
default via 192.168.43.1 dev wlan0 table 16802
192.168.43.1 dev wlan0 table 16802 scope link
192.168.43.70 dev wlan0 table 16802 scope link
192.168.43.102 dev wlan0 table 16802 scope link
default via 192.168.43.1 dev wlan0 src 192.168.43.73
192.168.2.0/24 dev br-lan scope link src 192.168.2.1
192.168.43.0/24 dev wlan0 scope link src 192.168.43.73
broadcast 127.0.0.0 dev lo table local scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local scope host src 127.0.0.1
local 127.0.0.1 dev lo table local scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local scope link src 127.0.0.1
broadcast 192.168.2.0 dev br-lan table local scope link src 192.168.2.1
local 192.168.2.1 dev br-lan table local scope host src 192.168.2.1
broadcast 192.168.2.255 dev br-lan table local scope link src 192.168.2.1
broadcast 192.168.43.0 dev wlan0 table local scope link src 192.168.43.73
local 192.168.43.73 dev wlan0 table local scope host src 192.168.43.73
broadcast 192.168.43.255 dev wlan0 table local scope link src 192.168.43.73
fd44:77e3:6d6c::/64 dev br-lan metric 1024
unreachable fd44:77e3:6d6c::/48 dev lo metric 2147483647 error -148
fe80::/64 dev br-lan metric 256
fe80::/64 dev wlan0 metric 256
fe80::/64 dev wlan0-1 metric 256
unreachable default dev lo metric -1 error -128
local ::1 dev lo table local metric 0
local fd44:77e3:6d6c:: dev lo table local metric 0
local fd44:77e3:6d6c::1 dev lo table local metric 0
local fe80:: dev lo table local metric 0
local fe80:: dev lo table local metric 0
local fe80::418:d6ff:fead:9aa7 dev lo table local metric 0
local fe80::618:d6ff:feac:9aa7 dev lo table local metric 0
ff00::/8 dev br-lan table local metric 256
ff00::/8 dev wlan0 table local metric 256
ff00::/8 dev wlan0-1 table local metric 256
unreachable default dev lo metric -1 error -128
I am not sure if this guide is still relevant but I have always run the relayd setup this way in the past and it works pretty much fine without a problem. At least it was working on 17.01.
The device that connects on the WLAN of the relay, does it get DHCP settings or not?
Can you try to manually assign IP/Mask/Gw/NS and test again if it works?
I deleted all the interfaces and followed your guide and it works!!
I think that the issue was with the dhcp config because I only edited it at first and then when I replaced it completely it worked.
If your problem is solved, feel free to mark the relevant post as the solution; and edit the title to add "[SOLVED]" to the beginning (click the pencil behind the topic).