Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 2 subscribers
  • Views 58705 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Prevent WAN access on additional IP address.

spacemancw
To map a public address to an internal address in the UTM-9, my understanding is that under "Interfaces" > "Additional Addresses" > I add a new address and assign it to the Outside interface.

Then create a NAT that for instance maps ANY service coming from ANY source going to this Additional address gets translated to the internal address that I choose.

My problem is that now I can manage the firewall using the additional address.
For instance, if the WAN address of the UTM is 65.65.65.60 and the additional address is 65.65.65.70, I can now managed the UTM using:

https://65.65.65.60:4444/ and https://65.65.65.70:4444/


How do I prevent https://65.65.65.70:4444/ form working.

I tried firewall rules such as, traffic from ANY using service 4444,80,443 going to 65.65.65.70, drop or reject. But it doesn't change anything.

Any help would be appreciated.


This thread was automatically locked due to age.
Parents
  • 0
    I have two DNATs, one for 4444 and one for 443, both going to the Blackhole.
    I can see Firewall Log entries for the 443 DNAT, but I don't see any for the 4444 DNAT.
    Yes the blackhole address is on the internal network. I've also tried a blackhole IP address that wasn't part of any of the networks on the interfaces.
Reply
  • 0
    I have two DNATs, one for 4444 and one for 443, both going to the Blackhole.
    I can see Firewall Log entries for the 443 DNAT, but I don't see any for the 4444 DNAT.
    Yes the blackhole address is on the internal network. I've also tried a blackhole IP address that wasn't part of any of the networks on the interfaces.
Children
No Data