Gateway for WAN (VLAN) is offline

Hello abbahex ,

Thank you for reaching out to the community, On the CLI, select option 4. Device console.
execute the following command and see if you receive an unicast reply and the device comes up
console> system diagnostics utilities arp ping interface Port3.100 192.168.178.1

Hello abbahex ,

Thank you for reaching out to the community, On the CLI, select option 4. Device console.
execute the following command and see if you receive an unicast reply and the device comes up
console> system diagnostics utilities arp ping interface Port3.100 192.168.178.1

Thank you for your reply. I tested the command, but it fails.

Does anything have to be changed here because of VLAN?

I then tested the connection via another port without VLAN and here it works.

check the connectivity in the VLAN, see if the vlan id tagged is  correct and if there is a switch then check if trunking has been done ? 

There is a switch, but the dhcp from Sophos 192.168.40.0 for my VLAN 40 works and the client have a connection to 192.168.40.253

Hello abbahex , 
If you are tagging the VLAN 40 under the Port2 then why have you configured the VLAN under the Port3 ?

Hello Vivek,
you mean my test with port 2? This was a test without any VLAN only with the hardware port 2 directly connected to my router.
I wanted to check if it is intrinsically due to the configuration of the Sophos

But again in the topology you have mentioned that your tagging VLAN 40 on Port2

This is the tagging of my switch. The Sophos on Port 3 is connected with the port 2 of the switch

So while initiating the arp ping request from the FW, we do not receive any response from 192.168.178.1, so can you check on the upstream router if it is evening receiving the arp ping request ?

This is in the log of my router. So I think the router gets a request from the sophos