Cannot tracert external IP of my firewall.

I just installed a secondhand Watchguard Firebox SOHO 6tc and have been working to set it up.  At this time, I am comfortable with setting allowances/restrictions on incoming and outgoing traffic with one exception.  I cannot communicate with my external IP address.  For example, if I set up an FTP server in my network and make the appropriate allowances, people outside of my network can use my FTP server.  I, on the other hand, cannot.  For some reason, I can't communicate with my external IP address while others can.  They are only restricted by my incoming permissions where I can't figure out how to allow myself access to anything.  If I tracert my external IP, it starts timing out as soon as it gets to the point where it would be going through my firewall.  (My firewall never shows up in the tracert if I try my external IP)  If I tracert another IP (such as google), my firewall shows up right before the trace hits my ISP.  Any ideas?  
Petra_fan1Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
dpk_walConnect With a Mentor Commented:
Let me explain what is happening:

With most of the networking devices, ingress interface cannot be same as the egress interface.

Now when you use external IP or DNS name the packets go out of SOHO and would come back on the same interface which is not supported. Few vendors, like Cisco implement something called hairpin for such connections; however, WG does not implement hairpin.

So, the solution is to have the internal machines do not send request out but rather query the internal server; so you can modify the hosts file on the individual machines or if you have an internal DNS caching server you can have it redirect all the request for DNS name to the internal IP.
With external  IP of the website it would not work behind WG at all.

Please let know if you need more details.

Thank you.
0
 
bbaoIT ConsultantCommented:
> For some reason, I can't communicate with my external IP address while others can.

from external side or internal?
0
 
dpk_walCommented:
I am not sure about the tracert it should work, check with your ISP if they are blocking anything, for the FTP or any other server hosted behind WG SOHO6tc, I think the problem you have is, others can communicate with FTP using the public IP but you are not able to do so with the external or public IP; you would be needed to use internal or private IP instead.
If you have domain setup then you should either configure a setting in the hosts file [%windir%/system32/drivers/etc/hosts] which would translate your domain to the internal IP address or if you have a internal DNS Server configure it as caching server for domain which would redirect all internal request to the internal IP.

Please let know if I am able to answer your question.

Thank you,
0
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

 
Petra_fan1Author Commented:
Alright, for clarification:
From inside of my network, if I type my external IP address (or DNS name I registered to my public IP) into my browser, I get nothing.  The page times out.
From outside of my network, if I type my external IP address (or DNS name I registered to my public IP) into my browser, I get my website.
In both cases, if I ping my DNS name, it resolves to my external IP address, so I know its not an issue with DNS in my network.

Before using this Firebox, I had a router in the same position of the network, and everything worked fine.  With this said, I thought it might be something I'm blocking with my firewall configuration, but if it was, than I shouldn't be able to access other websites from inside of my network or my website from outside of my network, right?

Any thoughts?  Thanks for the help.
0
 
Petra_fan1Author Commented:
That is the answer I was looking for.  Unfortunately, its not the answer I wanted, but it makes perfect sense when put that way.  I have modified my internal DNS system accordingly but have been running into some difficulty due to port/name relations where a firewall/router can specify ports and then the internal device recognizes names...But I'm working towards a solution with a reverse transparent proxy that I am trying to implement.  If I am correct, that should give me a solution I'll be happier with.  Thank you for your time.
0
 
Petra_fan1Author Commented:
Thank you very much.  You explained that very well.
0
 
dpk_walCommented:
You are welcome. The proxy might help, but am not 100% sure; because if proxy would also query on the public IP then same thing would happen.

Thank you.
0
 
Petra_fan1Author Commented:
That's why my aim is to use that in conjunction with my internal DNS so all computers will be oblivious to the rerouting (which is why I am thinking of the transparent option).  Its kind of a hack idea, but I think it will work nicely when properly implemented.  It is a small enough network that it shouldn't be a problem (I hope.  LOL).  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.