- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
02-07-2020 01:14 AM
HI Team
I have created S2S VPN tunnel between palo alto and cyberoam firewall.
Tunnel is up but the traffic is not flow.
Under Cyberoam firewall there is one server with public IP 144.21.X.X.
From palo alto we need to reach the peer end public IP 144.21.X.X via the vpn tunnel.
but whenever I tried to reach the peer end public IP 144.21.X.X its going via the internet rule instead of vpn rule.
Our requirement is that traffic should go via the vpn tunnel to reach the IP 144.21.X.X
I have configured the PBF policy but its not work.. Please help on this
Regards
Mohammed Asik
02-07-2020 01:43 AM
Hey,
This is expected.
Your PEER IP communication will happen over internet only. The proxy IDs configured will only pass through tunnel.
- Mayur
02-07-2020 04:05 AM
HI Mayur
I have configured proxy ID s also. but its not working
regards
Mohammed Asik
02-07-2020 04:28 AM
Hi @MohammedAsik Check if routes are pointed towards proper tunnel interface.
Verify traffic logs once if matching correct security policy and sending traffic to correct tunnel interface.
-Mayur
02-07-2020 05:25 AM
Please find the below routing and security policy details
144.250.3.222/32 0.0.0.0 10 A S tunnel.10
{
from inside;
source 172.31.62.0/24;
source-region none;
to vpn;
destination 144.250.3.222;
destination-region none;
user any;
category any;
application/service 0:any/any/any/any;
action allow;
icmp-unreachable: no
terminal yes;
}
Regards
Mohammed Asik
02-07-2020 05:55 AM - edited 02-07-2020 05:56 AM
Hi @MohammedAsik What is 0.0.0.0 in the route? is it next hop?
What you found in traffic logs?? Is firewall passing it to same tunnel interface?
-Mayur
02-07-2020 06:25 AM
Mayur
its a tunnel interface. thats why its showing next hop as 0.0.0.0.
In traffic logs its taking the internet rule and its not pass through tunnel interface. its passing through internet interface Ethernet 1/1.
Mohammed Asik
02-07-2020 06:47 AM
Can you please check once if tunnel interface belongs to VPN zone?
Mayur
02-07-2020 07:34 AM
Please find the below ss tunnel.10 interface
02-07-2020 10:49 AM - edited 02-07-2020 03:16 PM
Something is mis configured . Check any pbf which is sending traffic on external interface or traffic getting NAT?
please share traffic log snap?
Mayur
02-07-2020 01:53 PM - edited 02-07-2020 01:54 PM
Hi Mohammed,
Have you checked your NAT rules?
Since 144.21.X.X is a public IP, you might be hitting a NAT rule for the Internet depending on which zone your tunnel interface is located.
Also, I see that your Tunnel interface is part of the VPN zone. Is the source traffic is coming from the Inside zone? If so, do you have a security rule on your FW allowing communication between the Inside and VPN zone?
02-07-2020 10:09 PM
Hi Svelez
Yes I have security rule to allow from inside to vpn zone. Please find the below security rule and static route for respective tunnel traffic
144.250.3.222/32 0.0.0.0 10 A S tunnel.10
{
from inside;
source 172.31.62.0/24;
source-region none;
to vpn;
destination 144.250.3.222;
destination-region none;
user any;
category any;
application/service 0:any/any/any/any;
action allow;
icmp-unreachable: no
terminal yes;
}
02-10-2020 12:03 AM
@MohammedAsik hey, are you still facing issues?
- Mayur
02-11-2020 12:35 AM
Hi Mayur
Yes, still I am facing this issue
02-11-2020 06:59 PM
We can check it once over zoom or webex if you want.
- Mayur
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!