Bridge mode ARP replies not received

Kevin,

did you follow this kb?

https://community.sophos.com/kb/en-us/123098

Have a look at the logs to make sure no traffic is blocked. Create a lan to lan firewall rule where everything is enabled. Also enable Rouing checkbox on the bridge if traffic is layer 3.

Regards

I added a LAN to LAN rule and enabled routing on the bridge-pair. However, the gateway interface still shows as in the red. The other two firewall rules in place allow for all WAN to LAN traffic and all LAN to WAN traffic. It doesn't appear to matter whether or not the LAN to WAN rule is set to masquerade traffic or whether or not the WAN to LAN rule has a gateway set either. Any other ideas as to what else might need to be changed?

Kevin, check XG log viewer and make sure to enable ping on Administration > Device Access.

Regards

The log viewer doesn't really reflect anything that stands out in any of the logs. PING / PING6 is already enabled for the WAN zone. This is all being bench tested in VirtualBox. I'm going to try breaking the bridge to get the DHCP range for the NAT interface, rebuild the bridge and assign it a static IP in the VirtualBox NAT DHCP range to see if its the other Vm appliance that might be interfering with the ping. Although, I can sit another client OS directly behind the other appliance and it works like a champ.

Kevin,

did you enable the promiscous mode on Virtual Box?

Thanks

Not until now. However, that was what was needed. I set both interfaces associated with the XG VM to Allow All. It worked! :) Although, I don't understand why its needed. Shouldn't it be able to interact using standard L2/L3 protocols without needing to go promiscuous?

No. Promiscous mode is needed so the Firewall, VM, Appliance listen to traffic and are able to capture/analyze and so block traffic.

Regards

No. Promiscous mode is needed so the Firewall, VM, Appliance listen to traffic and are able to capture/analyze and so block traffic.

Regards