Can someone explain how supervised networking works?

I’m lost,

I’ve installed HA supervised on a PI and everything works fine, setup Cloudflare and all access works well for HA, however,

I cannot access the LAN on the PI. HA is connected with a IP of 192.168.1.2 with a gateway of 192.168.1.1, I have internet and connectivity as I am connecting remotely but I cannot PING or browse to the gateway 192.168.1.1 from the PI.

A tracroute to google.com shows traffic leaves via 192.168.1.1, as expected as its the only source of internet and I’m connected remotely, but I cannot at all access any other resources on the LAN from the PI, or even from HA CLI.

ifconfig shows eth0 sitting on 192.168.1.0/24. Everything was working fine until I changed the subnet (router, all LAN devices etc from the 192.168.2.0 network to 192.168.1.0).

cat /etc/network/interfaces shows an IP address of 192.168.1.2 for eth0 also. Is /etc/network/interfaces ignored with HA supervised?

What am I missing?

Thanks

If you have followed the requirements to the Supervised install, then I think one of them is that you have to use Network Manager.

try ip route and see what it shows.
I’m not familiar with Cloudflare, is it using a tunnel for you to gain access remotely to the Pi?

No, im actually using OpenVPN Cloud to get SSH access

Output of route print

default via 192.168.2.1 dev eth0 proto static metric 100
100.80.0.0/12 via 100.96.1.33 dev tun0
100.96.0.0/11 via 100.96.1.33 dev tun0
100.96.1.32/28 dev tun0 proto kernel scope link src 100.96.1.34
172.16.101.0/27 via 100.96.1.33 dev tun0
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
172.18.0.0/16 dev br-c345a24f4bb5 proto kernel scope link src 172.18.0.1
172.30.32.0/23 dev hassio proto kernel scope link src 172.30.32.1
192.168.2.0/24 via 100.96.1.33 dev tun0
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.2 metric 100

Cheers

Damn ok sorry false alarm I created a static route in OVPN cloud and forgot about it, deleted it and boom, all working now.