internal Network can't reach Public IP

Do you configure masquerading, so your private IP's not used at the internet.

Do you configure masquerading, so your private IP's not used at the internet.

Yes. Shoud I disable it?

no, you need masquerading to reach the internet while using private IP at the client.

seems your FW rule 19 isn't correct.

Must be:  internal LAN -> any -> Internet

Thanks for you replies

Here are my Interface and NAT Config

Ok so edit rule 19, make the source your internal network, the services any or whatever specific ports you want i.e. ports 80 & 443 for web browsing, them make the destination your wan.

You can do this by clicking on rule 19 edit, deleting the three you have set for source, services & destination.  Then click on the folder in the source part, and go to the search bard on the left, type LAN to find your internal LAN, you can drag and drop it into the source part.  Do the same for services with Any and the same for destination with WAN.

See pic

Also in order for us to see NAT you need to take another screen shot, it is under Network Protection --> NAT

It is right under the firewall menu option.

Hallo Elvis and welcome to the UTM Community!

I'm confused as to why you're trying to reach an IP on the External interface.  Maybe you need Accessing Internal or DMZ Webserver from Internal Network.

This feels like a routing problem, but let's confirm that by doing #1 in Rulz - was there anything in the Firewall log?

You will also want to read #3, #4 and #5 in Rulz.

Cheers - Bob

BAlfson said:

Hallo Elvis and welcome to the UTM Community!

I'm confused as to why you're trying to reach an IP on the External interface.  Maybe you need Accessing Internal or DMZ Webserver from Internal Network.

This feels like a routing problem, but let's confirm that by doing #1 in Rulz - was there anything in the Firewall log?

You will also want to read #3, #4 and #5 in Rulz.

Cheers - Bob

 

Hi Bob

Thanks for your reply. I will check the suggestions. Yes in the Log the Access is shown as allow. I also think this coud be a routing problem,coze if i try to access the external address from within the UTM it works (telnet from the shell direct on the FW)

Hi Bob and all

Thanks for Tipps the Article with the Internal DNS Server helped me. Will say i put a separate DNS Server for the Domains / Server (192.168.1.43) within the C-Class Network 192.168.1.0/24 and it works, means i can reach now the Servers behind the FW