Vrf Wan Lan Local

This scenario shows how to configure service traffic-proxy to intercept and proxy SSL traffic. Both WAN and LAN interfaces are bound to different VRFs and the service is bound to a local VRF.

../../../../_images/proxy.svg

Test Traffic-Proxy Interception With Multiple VRFs

Description

This example demonstrates how to configure the device to intercept and proxy SSL traffic. For this purpose, the service traffic-proxy is bound to the port 3128 and the VRF DUM. LAN and WAN interfaces are bound to different VRFs.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces eth0 traffic policy in TPROXY
set interfaces eth0 address 192.168.1.1/24
set interfaces eth0 tcp-mss 1400
set interfaces eth1.100 address 10.0.0.1/24
set interfaces eth1.100 tcp-mss 1400
set traffic policy TPROXY rule 5 selector TCP_TRAFFIC
set traffic policy TPROXY rule 5 action proxy tcp 3128
set traffic selector TCP_TRAFFIC rule 1 protocol tcp
set traffic selector TCP_TRAFFIC rule 1 destination port 80,443,8080,4430
set service traffic-proxy TRAFFIC_PROXY mode ssl
set service traffic-proxy TRAFFIC_PROXY port 3128
set service traffic-proxy TRAFFIC_PROXY x509 ca-cert running://test.crt
set service traffic-proxy TRAFFIC_PROXY x509 ca-key running://test.key
set interfaces eth0 vrf LAN
set interfaces eth1.100 vrf WAN
set interfaces dummy dum0 address 1.0.0.1/24
set interfaces dummy dum0 vrf DUM
set interfaces dummy dum0 traffic policy local-out SET_WAN
set traffic policy SET_WAN rule 1 set vrf WAN
set service traffic-proxy TRAFFIC_PROXY local-vrf DUM
set system vrf LAN
set system vrf WAN
set system vrf DUM
set protocols vrf DUM static route 0.0.0.0/0 interface dum0
set protocols vrf LAN static route 10.0.0.0/24 interface eth1.100
set protocols vrf WAN static route 192.168.1.0/24 interface eth0
set protocols vrf WAN static route 1.0.0.0/24 next-hop-vrf DUM

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 192.168.1.2/24
set protocols static route 0.0.0.0/0 next-hop 192.168.1.1

Step 3: Set the following configuration in DUT2:

set interfaces ethernet eth0 vif 100 address 10.0.0.2/24
set protocols static route 0.0.0.0/0 next-hop 10.0.0.1

Step 4: Ping IP address 10.0.0.2 from DUT1:

admin@DUT1$ ping 10.0.0.2 count 1 size 56 timeout 1
Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=63 time=2.12 ms

--- 10.0.0.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.124/2.124/2.124/0.000 ms

Step 5: Ping IP address 192.168.1.2 from DUT2:

admin@DUT2$ ping 192.168.1.2 count 1 size 56 timeout 1
Show output
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=63 time=0.623 ms

--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.623/0.623/0.623/0.000 ms

Step 6: Initiate a ssl connection from DUT1 to DUT2 and try to send some messages between both endpoints

admin@DUT2$ monitor test connection server 443 ssl cert running://test.crt key running://test.key
admin@DUT1$ monitor test connection client 10.0.0.2 443 ssl source-port 1234

Step 7: Run command service traffic-proxy TRAFFIC_PROXY show stats at DUT0 and check if output does not match the following regular expressions:

intercepted\s+0\s+0
Show output
Statistics for instance "TRAFFIC_PROXY":

-----------------------------
name           packets  bytes
-----------------------------
queue - reply        0      0
queue - orig         0      0
intercepted         12   1100
error                0      0