Firewall/routing question

Hi,

do you have a firewall rule allowing traffic between there LANs?

Ian

Hi Ian,

Yes. I have a firewall rule where the LAN source zones and destination zones can talk to "Any" devices and networks  - for testing purposes at this stage

Even with this in place the issue still remains

Is it at the top of your rule list?

Then check the logviewer refining your view to the source IP to see where it goes?

Ian

Hi Ian,

The firewall rule was already at the top of the list but thanks for the suggestion.

I can see that the firewall is allowing the device to ping the gateway (192.168.200.1) , but the device itself is not able to receive responses from 192.168.200.1

Not sure if I need to configure something on the gateway at 192.168.200.1

What does the Linux gateway do?
you would need a route on the Linux gateway pointing at the XG for the other network.

ian

The Linux server is the local gateway to the outside world. Yes, your suggestion sounds like it will provide a solution. I need to figure out what static route needs to be setup to make this work

What does the XG do and why isn’t your gateway?
ian

The Sophos XGS is a gateway to another (new) network. The intention is to "gradually" migrate from the 192.168.200.0/24 network to the 192.168.100.0/24 network and remove the linux gateway once the migration is finished.

I'm well aware I have to be careful I don't create any unintended network loops, correct ?

Hello John,

you need to define a route to the 192.168.100.0/24 network on the gateway 192.168.200.1.

If you finished migrating to the new net, you can remove this.

Thanks for that. I did in fact do something like 
ip route add 192.168.100.0/24 via 192.168.200.220 on the linux gateway machine, yesterday with some success

192.168.100.2 can ping most machines on 192.168.200.0/24 via the gateway at 192.168.200.220

I think this problem can be put to bed.