Watchguard x750e Firewall - Routing between interfaces with different default gateways


I'm trying to put our wireless access point into our firewall using one of the spare interfaces so I can allow only a handful of required services through using the WiFi, rather than - as present - having it within our LAN range, with unadulterated access to everything.

I've managed to configure this absolutely fine, however I have a problem when I'm trying to access a machine within the LAN whose own default gateway is another router rather than the Watchguard.

For example, I set up an allow rule to allow only Terminal Services traffic over the interface used for the wireless. I can use the remote desktop client to access my own PC (my PC's default gateway is the Watchguard which has issued it a DHCP IP address), but not our terminal servers. The terminal servers can be accessed from my own PC directly as they are in the same IP range, and the same physical network.

Also, when the wireless access point is within the same LAN as the servers, it works fine. I don't think it's specifically a wireless or firewall issue but all help greatly appreciated!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You will need to add additional routes to your setup. You can either add a new persisitent static route to the machines you wish to access that directs all traffic intended for your wireless range should go to the alternate router.

eg.  route add mask -p

the above states that to access a machine on a 192.168.2.x range (your wireless subnet) go via the gateway at rather than the default gateway. the -p makes it persistent so that it remains after a reboot.

Or you could add a new route on the original router/gateway that does the same thing.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
advfinanceAuthor Commented:
Thanks very much - Working nicely!!! Would not have thought of that at all!!!
Red-KingIT ManagerCommented:

I think what you need to do here is to add a route on the other router to tell it where to send the traffic to.
This route needs to tell the router that to access devices on the Wifi network it needs to go to the Watchguard Firebox first.

If that's not it then maybe you need to add the IP of the other router into the 'From' section of the Allow Terminal Services policy on the Firebox.

By the sounds of it you have the Firebox configured correctly.
It would be worth doing a traceroute from one of the terminal servers to a device on the Wifi Network and seeing how far the traffic gets. I'm guess it will get as far as the other router and then time out.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.