Solved

Firebox X Edge NAT issue

Posted on 2012-04-04
7
1,558 Views
Last Modified: 2012-04-15
Trying to confiure a NAT on a Watchguard Firebox X Edge v7.5.  We need to allow an external IP to see an internal/trusted IP to allow printing over a WiFi connection.  We have set the filter rule on the firewall, however the connection is notworking, nor can we telnet to the address from the wireless connection on port 9100.

Please see attachment for current setup

I guess we need to know if this device can even do what we are asking, if so, then what we are missing or doing wrong.  Thanks in advance.
firebox001.jpg
firebox002.jpg
0
Comment
Question by:rmj6969
  • 4
  • 3
7 Comments
 
LVL 32

Expert Comment

by:dpk_wal
ID: 37809443
You wish to allow incoming connection from internet, if yes, then modify the source From IP in firebox001.jpg. Remove the IP 10.5.17.48/16 and put the public IP instead.

If you have say optional and trusted network; with 10.5.17.48/16 being on optional then this should work.

Please give some details on the setup.

Thank you.
0
 

Author Comment

by:rmj6969
ID: 37810559
Ok, here is the setup.  We are on a hospital network (see attached image 004 for connection info).  We are also on there wireless network which is a different IP net.  The hospital IT dept. has setup the wireless NET to see the 10.5.17.* NET that we connect to.  So on our end we need to enable or allow the IP's they have given us for NAT'g to devices on out Trusted NET for the wireless devices (laptops, etc.) to be able to print, see the server, etc.

We were asked to NAT the following:

10.5.17.46/16 > 192.168.1.201(server) port 443
10.5.17.47/16 > 192.168.1.30(fax server) port 443
10.5.17.48/16 > 192.168.1.230(printer) port 9100

The wireless NET (10.50.57.*) needs to be able to see the addresses above.

The wireless NET does see the External address of 10.5.17.50/16, we can telnet this and connect, but not the above addresses.
firebox003.jpg
firebox004.jpg
firebox005.jpg
0
 

Author Comment

by:rmj6969
ID: 37811928
The Device is a Watchguard Firebox Edge 7.5
Build 19
Boot Rom - 7.2.1
Model X5
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 32

Expert Comment

by:dpk_wal
ID: 37814929
Please ensure that there is no blocked subnet 10.0.0.0/8 or 192.168.0.0/16 under Firewall->Blocked Sites.

Please note as you running 7.5 version of WG software you cannot use more than public IP address on the external interface.

You can only create incoming service to allow inbound traffic on IP of external interface: 10.5.17.50. WG would not listed to other IP addresses and would not NAT the traffic to internal hosts on other IP address.

>> We were asked to NAT the following:
>> 10.5.17.46/16 > 192.168.1.201(server) port 443
>> 10.5.17.47/16 > 192.168.1.30(fax server) port 443
>> 10.5.17.48/16 > 192.168.1.230(printer) port 9100

Instead you can use 10.5.17.50 IP and use different ports to forward traffic to 192.168.1.0/24 subnet.

You would create custom service. As per firebox001.jpg; change Allow from to either ANY or 10.5.0.0/16 or if you wish only specific machines then specify individual/range IPs of those hosts.

Please let know if you need more details.

Thank you.
0
 

Author Comment

by:rmj6969
ID: 37815080
Can you give me an example of what you mean below:



Instead you can use 10.5.17.50 IP and use different ports to forward traffic to 192.168.1.0/24 subnet.

You would create custom service. As per firebox001.jpg; change Allow from to either ANY or 10.5.0.0/16 or if you wish only specific machines then specify individual/range IPs of those hosts.
0
 
LVL 32

Accepted Solution

by:
dpk_wal earned 500 total points
ID: 37815372
What I mean is that on the IP 10.5.17.50; configure service to allow inbound traffic.

So,
10.5.17.50 -> 192.168.1.201(server) TCP/443
10.5.17.50 -> 192.168.1.30(fax server) TCP/444 [or any other port; you would need to configure fax server to listen on some other port]
10.5.17.50 -> 192.168.1.230(printer) TCP/9100

You would create three custom service; and for configure incoming as Allowed; from ANY; to internal-ip as above.

Further, from 10.5/16 subnet to access printer/fax server/server you would use IP 10.5.17.50.

All the hosts on 192.168.1.0/24 subnet would continue to use 192.168.1.x IP for the specific servers.

Please implement and update.

Thank you.
0
 

Author Comment

by:rmj6969
ID: 37848488
Hi,

So ever since I configured the router in the way you explained, all devices are able to be connected to, except now a PC that had a RDP cannot be connected to.  We cannot RDP to only one PC that does have a rule in the router for RDP, I also cannot telnet into it using port 3389.  I can however RDP into any other PC including the server.  This is all local area network.  I have checked the PC in question, firewall, etc. and nothing has changed.  It seems to a coincidence that this is happening, but I thought if you had any insight inb the matter.  The RDP rule on the router for this PC is:

Port used: 3389
Allow IP 192.168.1.10 from ANY(10.5.17.50)
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Do you have a windows based Checkpoint SmartCenter for centralized Checkpoint management?  Have you ever backed up the firewall policy residing on the SmartCenter?  If you have then you know the hassles of connecting to the server, doing an upgrade_…
The DROP (Spamhaus Don't Route Or Peer List) is a small list of IP address ranges that have been stolen or hijacked from their rightful owners. The DROP list is not a DNS based list.  It is designed to be downloaded as a file, with primary intention…
This video discusses moving either the default database or any database to a new volume.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now