Topic
3 replies Latest Post - ‏2013-08-19T13:43:40Z by swlinn
harish8115
harish8115
15 Posts
ACCEPTED ANSWER

Pinned topic Connectivity test (eth0, eth1, etc)

‏2013-08-17T14:11:38Z |

I want to test firewall rule connectivity eth1 (WebServices Port) to the target servers. My problem is that I can only test using the DataPower Admin GUI page from eth0. Is there a way I can run the connectivity test from the other interfaces?

Please advise.

  • swlinn
    swlinn
    1330 Posts
    ACCEPTED ANSWER

    Re: Connectivity test (eth0, eth1, etc)

    ‏2013-08-17T23:05:08Z  in response to harish8115

    You can always place a static route on your ethx for your firewall IPs/ports for testing.

    Regards,

    Steve

  • harish8115
    harish8115
    15 Posts
    ACCEPTED ANSWER

    Re: Connectivity test (eth0, eth1, etc)

    ‏2013-08-18T01:27:14Z  in response to harish8115

    I have two interfaces configured on DataPower. Eth0 and Eth1. I would like to test if I'm able to reach a certain server from Eth1. The troubleshooting option in WebGUI only allows me to test from Eth0. 

    Can  you please advise on how i can place a static route so that my connectivity test uses Eth1 instead of Eth0. Which menu option should I be looking at. My apologies if this request sounds naive. I'm still learning.

    • swlinn
      swlinn
      1330 Posts
      ACCEPTED ANSWER

      Re: Connectivity test (eth0, eth1, etc)

      ‏2013-08-19T13:43:40Z  in response to harish8115

      Send a test message simply uses a DNS name or IP as the host and the routing done by the appliance is based on the routing rules taken from your eth0 and eth1 configurations.  Apparently the IP you are using will default to eth0.  To test for eth1, you must add a static route for the eth1 configuration.  Static routes are on the 2nd tab of the configuration.  You would provide your backend IP and a gateway to be used for that IP and a metric on 1.  With the static route, the routing tables will match on your IP and eth1 will be used for this backend communications.

      Regards,
      Steve