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
    Thanks BAlfson. I tried to do what I think you suggest. Tho not quite sure how to blackhole.
    I created a DNAT that says traffic from ANY using 4444 Going to "Outside [SecondaryIP](Address)", change destination to "some other internal IP", service [blank].

    Did another one like this for https.

    Put these 2 in positions 1 and 2.
    but https://secondaryIP:4444 still works.

    I also have a rule in position 1 that says sources ANY, service 4444, HTTPS, destination "Outside [SecondaryIP](Address)", Reject or drop.

    No joy.
Reply
  • 0
    Thanks BAlfson. I tried to do what I think you suggest. Tho not quite sure how to blackhole.
    I created a DNAT that says traffic from ANY using 4444 Going to "Outside [SecondaryIP](Address)", change destination to "some other internal IP", service [blank].

    Did another one like this for https.

    Put these 2 in positions 1 and 2.
    but https://secondaryIP:4444 still works.

    I also have a rule in position 1 that says sources ANY, service 4444, HTTPS, destination "Outside [SecondaryIP](Address)", Reject or drop.

    No joy.
Children
No Data