Hello Dvlacic, Here is the KB doc which might help you to understand Proxy-ID concept for IPSec VPN tunnel. Why is a Proxy-ID Required for VPNs between PAN and Firewalls that Support Policy Based VPNs? For example: admin@40-PA-4020> show vpn flow name test-tunnel tunnel test-tunnel id: 2 type: IPSec gateway id: 1 local ip: 10.66.24.40 peer ip: 1.1.1.1 inner interface: tunnel.101 outer interface: ethernet1/3 state: init session: 49166 tunnel mtu: 1448 lifetime remain: N/A monitor: off monitor packets seen: 0 monitor packets reply: 0 en/decap context: 5 local spi: 00000000 remote spi: 00000000 key type: auto key protocol: ESP auth algorithm: NOT ESTABLISHED enc algorithm: NOT ESTABLISHED proxy-id local ip: 0.0.0.0/0 >>>>>>>>>>>>>>>>>>>>>>>>>>>> Source subnet, where from you are expecting to initiate traffic proxy-id remote ip: 0.0.0.0/0 >>>>>>>>>>>>>>>>>>>>>>>>>>>> Destination private subnet proxy-id protocol: 0 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Protocol allowed through the tunnel proxy-id local port: 0 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source port proxy-id remote port: 0 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Destination For each proxy-ID, the firewall will create different SPI value (different IPsec tunnel) between source and destination. PAN and Juniper firewall's uses 0.0.0.0/0 as default proxy ID, but for CISCO devices, you have to define the proxy-ID ( access-list) in order to pass traffic through tunnel. Hope this helps. Thanks
... View more