I believe, after talking to pfSense people, I need to set a static route from my Hassio install at 172.27.3.4 to my 172.27.2.x network:
ip route add 172.27.2.0/24 via 172.27.3.1 dev eth0
This should allow me to access Hassio from 172.27.2.x by bypassing the default gateway at 172.27.3.3, which does not route to 172.27.2.x normally.
But when I enter the above command through SSH on my RPI3B+ running Hassio 0.91.3, I get:
core-ssh:/etc/network# ip route
default via 172.30.32.1 dev eth0
172.30.32.0/23 dev eth0 scope link src 172.30.33.2
core-ssh:/etc/network# ip route add 172.27.2.0/24 via 172.27.3.1 dev eth0
ip: RTNETLINK answers: Operation not permitted
core-ssh:/etc/network#
And even stranger, my Hassio device is still at 172.27.3.4 as assigned by the DHCP server in pfSense, but ifconfig show a completely different ip address on eth0 (yes, it connected via Ethernet):
I have static routes to handle local addresses and I can ping and traceroute across networks, back and forth, without any problem. I can access devices on the 2.x network from the 3.x network (where Home Assistant is located), but I can’t go the other way: access devices on the 3.x network from the 2.x
So this is sort of a Hail Mary
Thanks for your help!
Well, it looks like this was the problem. I don’t know why it was in there. I don’t know what taking it out might break, but now I can get to 3.x devices from the 2.x network!
Didn’t need access to the HassOS afterall. It was this setting in RPI Gateway
Dear, I’m facing the same issue, could you please explain me better how you fixed it? I dind’t got very well the “-A POSTROUTING -o eth0 -j MASQUERADE” sentence. Where is supposed to be located this sentence? thank you very much
I Also want to add a static route to Home assistant OS 10.4. as I have multiple routers on my network.
So I opened “Terminal” in HA and tried NMCLI. But then it says “Command not found”