Network behind green: works fine, but only one way pinging

[Guest]

[jaaptr]

Hello,

I am using Endian firewall for a while now and I am very satisfied with it. However, I see some behaviour which I can't explain.

In my setup the Endian is the default gateway with IP 172.16.10.254 on the LAN. The mainoffice is connected to it's stores with an EPN. Accessing this EPN is handled by a second router on the LAN with IP 172.16.10.253.
I have added the needed routes to the Network -> Routing -> Static routing list.

I am able to ping from the LAN to a device on the EPN. Traffic (FTP / videosurveillance / etc...) from the LAN to the EPN is also working fine.
Traffic from the EPN (RDP / webservices on port 5000) to the LAN is also working fine. However, if I try to ping a device on the LAN from an EPN device, the ping requests do result in a time-out.

Using the Microsoft Network Monitor I can see that the 'ECHO request message' from the EPN device is received on the LAN device and answerd with a 'ECHO reply message'. This reply message is send to this LAN device it's default gateway, the Endian firewall. It's look like that the firewall is not routing this message to the EPN router on the LAN. If look in the firewall or live logs, I can't find the 'traffic'.

If I manually add the EPN routes to the Windows machine on the LAN, a ping request from the EPN is replied succesfull. But that's of course not a solution...

Can someone explain this behaviour and provide a solution?

Thanks in advance!

[mrkroket]

What is an EPN?
Routing must be done forward and backwards.

I mean, sending traffic from A to B doesn't implies that B can send traffic to A.
You must recheck your routing tables on both directions.

Make a tracert on both ways, it should do the same but in reverse order. If not, recheck where the traffic get lost.