Link to home
Start Free TrialLog in
Avatar of DTS-Tech
DTS-TechFlag for Australia

asked on

Watchguard Firebox X550e Allow Traffic Between Trusted Interfaces

Hi There,

I have a Watchguard Firebox X550e device.

I have added a second 'Trusted' Interface so that an additional network can be used for security cameras and their server.

eth0 External (Internet) Static Public IP Address
eth1 Trusted (Internal LAN) 172.29.199.253/25
eth2 Trusted (Internal Camera Network) 192.168.1.10/24

I have managed to allow access to the Security Camera Server (192.168.1.50/24) from an external source IP without any problems, but I am not able to allow traffic between the 2 Trusted Internal interfaces. I would like to be able to allow Any type of traffic via Any port between the 2 Trusted interfaces. I have created the following policy in an attempt to allow this:

Policy Type = Any
From = Any-Trusted
To = Any-Trusted

This will not allow the Security Camera Server (eth2) to access a device on the Internal LAN Network (eth1) which is what is required.

So... what exactly do I need to do in order to allow the 2 internal networks to communicate as if they were 1?

Any Help will be greatly appreciated! :-)

Many Thanks!
SOLUTION
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DTS-Tech

ASKER

Hi setasoujiro, thanks for your reply. What you suggestion had been tried previously but I have tried it once again with no luck. I am still unable to ping the Security Camera Server (192.168.1.50/24) from the Domain Controller (172.29.199.208/25) on the existing network, though I can ping the interface on eth2 (192.168.1.10/24).

Any assistance would be appreciated

Thanks in advance
Can you enable the rule as i said, and then look in the watchguard traffic monitor?
to see if there is anything blocked?
ASKER CERTIFIED SOLUTION
Avatar of dpk_wal
dpk_wal
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Apologies guys... we have been distracted with another issue at another client site.

We'll be testing the suggested resolutions today and shall report back on their effectiveness.

Thanks for all of your help. Talk soon. :-)
Be careful with the auto ordering.  If you are trying to ping, which is port specific, it will be placed higher in the list than the rule that allows any traffic. Then you would never get to your rule for trusted any to trusted any.