Skip to main content
R1chou
R1chou
New Member
November 17, 2020
Solved

Allowing ping

  • November 17, 2020
  • 1 reply
  • 13371 views

Hello,

 

I have an internal IIS server with one site configured with the following address (for example) : https://toto.test.fr

The IP server is for example : 10.0.10.1

The public ip address is for example : 1.1.1.1

 

I created the following virtual IP

name : test external ip : 1.1.1.1

internal ip : 10.0.10.1

Port forwarding TCP : 443 to 443

 

Then I created my policy enabling all from external to access to test on service HTTPS.

 

It's working but I would like to know how to enable the ping to toto.test.fr because currently it's not working.

I tried to add a new virtual ip by selecting port forwarding ICMP and added ICMP+Ping  to my policy but it doesn't work.

 

Regards,

    Best answer by ede_pfau

    hi,

     

    and welcome to the forums.

     

    As ICMP / ping does not use ports, a port-forwarding VIP will not forward it. Make the VIP non-portforwarding, and limit the incoming services in the policy.

    1 reply

    ede_pfau
    SuperUser
    ede_pfauAnswer
    SuperUser
    November 17, 2020

    hi,

     

    and welcome to the forums.

     

    As ICMP / ping does not use ports, a port-forwarding VIP will not forward it. Make the VIP non-portforwarding, and limit the incoming services in the policy.

    R1chou
    R1chouAuthor
    New Member
    November 17, 2020

    Hi,

     

    Thank you, the public ip address used in my VIP "test" is already used by another VIP forwarding port 88 to another server. I suppose that I can't use your solution, correct ?

     

    Regards,

    Markus
    Markus
    New Member
    November 17, 2020

    Did you have only one IP? If so, you can allow ping on your wan interface...

    Terms & ConditionsAccessibility statement