Mark

This scenario shows how to mark diverted packets in order to distinguish locally generated traffic from proxied traffic.

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

Test Traffic-Proxy With Mark

Description

This example demonstrates how to mark packets crafted by the traffic-proxy service. A traffic policy with a special traffic selector is attached to the WAN interface to match only marked packets or ICMP messages.

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 service traffic-proxy TRAFFIC_PROXY mark 1234
set traffic policy MARKED_POL rule 1 selector MARKED_SEL
set traffic selector MARKED_SEL rule 1 protocol icmp
set traffic selector MARKED_SEL rule 2 mark 1234
set interfaces eth1.100 traffic policy out MARKED_POL

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=0.703 ms

--- 10.0.0.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.703/0.703/0.703/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.714 ms

--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.714/0.714/0.714/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         13   1138
error                0      0

Step 8: Run command traffic policy MARKED_POL show at DUT0 and check if output matches the following regular expressions:

1\s+MARKED_SEL\s+[1-9]\d*\s+[1-9]\d*
Show output
Policy MARKED_POL -- ifc eth1.100 -- hook out prio very-high

-----------------------------------------------------------------
rule    selector   pkts match  pkts eval  bytes match  bytes eval
-----------------------------------------------------------------
1      MARKED_SEL          14         19         1497        1977
-----------------------------------------------------------------
Total                      14         19         1497        1977