7.1.1 Wireguard Question

I feel like I am missing something here -

  • I had a working configuration from my phone to my RB5009 that would allow my Wireguard subnet access to my LAN (and WAN).
    Original LAN: 192.168.1.0/24;
    Original WG subnet: 192.168.100.0/24.
  • I reconfigured my LAN address space, with everything remaining the same except the subnets:
    New LAN: 172.16.0.0/16
    New WG subnet: 172.17.0.0/24

After the change, I could connect to the WG tunnel from my phone, however I could only access addresses in the 172.16.0.0/24 address range - services in 172.16.1.0/24 were not accessible, even with a completely cleared out firewall. To work around it, I switched my WG subnet to 192.168.100.0/24 and everything works as it should.

Am I missing something really obvious about class B networks and class C network routing? Or is this a bug?

This may be related, but I am connecting to my ISP over PPPOE, which gives me a public IP, as well as a network address of 172.16.14.xxx. This is in my LAN subnet, but since it is through another interface, routing should be alright I thought. My route list looks like:
Screenshot 2022-02-03 170353.png
This is the route list that is working, but before the last entry was 172.17.0.0/24

Maybe if you shared some actual config, someone could tell you what’s wrong with it.

The 172.16.14.xxx/32 on PPPoE is just single address, it would conflict with same address in LAN, but not with anything else.

We need to see two things
Post your phone parameters
Post your config
/export hide-sensitive file=anynameyouwish

Just dont provide the actual keys LOL.