Show page

Differences

This shows you the differences between two versions of the page.

--- ep:labs:061:contents:tasks:ex4 [2019/11/17 18:29]
andrei.crividenco [04. [10p] Time-based data when plotting in gnuplot]
+++ ep:labs:061:contents:tasks:ex4 [2025/04/08 13:02] (current)
cezar.craciunoiu [04. [10p] Bonus - Protocol Options]
@@ Line 1: / Line 1: @@
-==== 04. [10p] Time-based data when plotting in gnuplot ====
+==== 04. [10p] Bonus - Protocol Options ====
+<spoiler>
-Datafile: {{:ep:labs:time_data.txt|}}
+As you've probably already seen in the previous exercise, TCP uses protocol extensions (called options) in order to negotiate session parameters and improve overall performance. Note that this mechanism has existed since the very inception of the protocol approx. 30 years ago ([[https://datatracker.ietf.org/doc/html/rfc793#section-3.1|RFC793 - Transmission Control Protocol]]), with many being added post-factum.
-Using the code provided in “Tutorial 03. Time-based data when plotting in gnuplot”, use the histogram style, and format the xtic labels using strftime and timecolumn.
+While the same could be said for IP options ([[https://datatracker.ietf.org/doc/html/rfc791#section-3.1|RFC791 - Internet Protocol]]), there have always been... issues. In 2005 it was decided that [[https://www2.eecs.berkeley.edu/Pubs/TechRpts/2005/EECS-2005-24.pdf| IP Options are not an option]]. Middleboxes (i.e.: network equipment in the Internet -- routers, NATs, firewalls, etc.) would sometimes implement abridged versions of the protocol specifications. For IP options, this meant that the IHL field would be ignored and the header would always be considered to be 20 bytes in length. As a result, if a packet carried IP options, cheap network equipment would wrongly assume that the layer 4 header would start at a 20 byte offset and drop it due to erroneously perceived malformations.
+The authors of the 2005 report discovered that only a fraction (15%) of edge Autonomous Systems (AS -- huge, ISP-grade networks with a unified routing policy) were responsible for most packet drops. This made them optimistic towards a speedy resolution of this issue, but things haven't changed much in the past 15 or so years. Today IP options usually work just fine in local networks. As for the wider Internet, there are specific paths and networks where IP options can pass unthwarted, but only if the layer 4 protocol is ICMP. The logic may be that most IP options are used for path measurement anyway, so why use it in conjunction with anything other than ICMP (a pretty dumb argument, I admit... but it's not mine).
+Luckily, one of these compliant networks is RoEduNet. If you're not working from the university's network, then start a VM instance on [[https://cloud-controller.grid.pub.ro/dashboard/auth/login/?next=/dashboard/|OpenStack]]. ISPs like RDS tend to drop IP Options. As a target, we will use [[https://www.digitalocean.com/|DigitalOcean]]. Based on some personal tests, I can guarantee that they don't drop any options, regardless of region.
+{{ :ep:labs:04:contents:tasks:ip_recordroute.png?700 |}}
+<html>
+<center>
+<b>Figure 2:</b> Layout of a layer 3 (IP) header with options. Their presence is confirmed by an Internet Header Length (IHL) value strictly larger than 5. Most options are Type-Length-Value (TLV) encoded. When the length is constant or there is no information to be included (e.g.: No Operation, End of Options List), deviations from this format can be accepted for the purpose of saving space.
+</center>
+</html>
+**Overarching Goal**
+The first task is to modify outgoing traffic and include a Record Route option in an ICMP Echo Request. Check its description in [[https://datatracker.ietf.org/doc/html/rfc791|RFC791]] to understand what it does (and no, not "Loose/Strict Source and Record Route"... keep hitting that Find key). The packet structure will resemble that in the picture above. Don't worry; for this step, we'll give you a little help ;)
+Your second task will be to write a bash script that extracts the IP addresses from the ICMP Echo Response's Record Route option from a packet capture and perform an AS Lookup. In other words, you will determine the names of all the networks that the packet traverses on its way from the university to DigialOcean and back.
+But let's take it step-by-step.
+**Task A - Injecting IP Options**
+Remember talking about **iptables** extensions earlier? **Netfilter Queue** is one of them and will be relevant for this task. What it is, is an **iptables** target. What it does, it redirects each matched packet to a userspace process for evaluation and optionally, //modification//.
+The userspace process receives each packet by polling a [[https://www.man7.org/linux/man-pages/man7/netlink.7.html|Netlink Socket]]. After obtaining one, it can perform any type of analysis that it wants (e.g.: [[https://dl.acm.org/doi/pdf/10.1145/1151659.1159952|deep packet inspection]]) in order to reach a verdict. The verdict can be the already known built-ins (i.e.: //ACCEPT, DROP,// etc.) or it can redirect the packet to another queue, with another process listening. When setting the verdict, a modified packet can be provided to replace the original on its datapath through the kernel's network stack.
+Enter [[https://github.com/RaduMantu/ops-inject|ops-inject]]. This is a tool (that's still under development, mind you) that allows the annotation of matched packets with IP/TCP/UDP options. Why is this tool simple to use: all you have to do is provide a sequence of bytes representing the [[https://www.iana.org/assignments/ip-parameters/ip-parameters.xhtml|codepoints]] of the options that you want to append. This byte stream is passed to an internal decoder that //expands// each byte into a fully-fledged option, albeit in accordance to an arbitrary implementation. Once you clone the repo, you should look over two sources in particular:
+  * ''src/main.cpp'' : here, just understand what **libnetfilterqueue** library calls are made in order to set up the Unix socket, to receive the packet and to set its verdict.
+  * ''src/ops_ip.c'' : this is where all available IP Options are implemented; take a look at the **ip_decoders** vtable at the bottom to associate options and codepoints.
+First of all, let's fetch the tool and compile it.
+<code bash>
+$ git clone https://github.com/RaduMantu/ops-inject.git
+$ cd !$:t:r
+$ make -j $(nproc)
+</code>
+<note tip>
+//Pro tip #3//: [[https://www.gnu.org/software/bash/manual/html_node/Modifiers.html|Bash Modifiers]] and [[https://www.gnu.org/software/bash/manual/html_node/Word-Designators.html|Word Designators]]
+  * ''!$'' is substituted with the final argument of previously executed command
+  * '':t'' removes the leading pathname components, leaving //ops-inject.git//
+  * '':r'' removes exactly one trailing suffix, leaving //ops-inject//
+----
+Troubleshooting:
+  * **IPPROTO_ETHERNET error** : if your //netinet/in.h// is missing this definition, you can delete line 36 from //src/str_proto.c//.
+  * **libnetfilter-queue missing** : consider installing //libnetfilter-queue-dev// and //libnetfilter-queue1//.
+</note>
+Next, let's insert an **iptables** rule that matches all outgoing ICMP packets.
+Take note of ''%%--%%queue-num 0'' for when we'll need to tell the userspace process which Netfilter Queue to subscribe. Also, ''%%--%%queue-bypass'' tells the **iptables** module to disable enqueuing packets if there's no process listening. Otherwise, the queue's buffer will fill up and overflowing packets will be dropped by default until some space is created.
+<code bash>
+$ sudo iptables -I OUTPUT -p icmp -j NFQUEUE --queue-num 0 --queue-bypass
+</code>
+Finally, run **ops-inject** while telling it to append the Record Route option (0x07). Because the tool takes a file as input, and because we give it the PseudoTerminal Slave of a [[https://www.gnu.org/software/bash/manual/html_node/Command-Grouping.html|subshell]], things can get messy if we simply run it with **sudo**. As a result, it's easier to just switch to **root**. To get a feel of what the other options do, just run ''ops-inject %%--%%help'' once.
 <code>
-set timefmt "%H:%S"
+$ sudo su
-set style fill solid 0.6 border -1
+# ./bin/ops-inject -p ip -q 0 -w <(printf '\x07')
-set style data histogram
-set style histogram clustered gap 1 plot 'data.dat' using 2:xtic(strftime('%H', timecolumn(1))), \ '' using ($2*0.5), \ '' using ($2*0.7)
 </code>
+Having completed the setup, let's generate some traffic!
+<code bash>
+$ ping -c 3 $(dig +short digitalocean.com | head -n 1)
+    PING 104.16.182.15 (104.16.182.15) 56(84) bytes of data.
+bytes from 104.16.182.15: icmp_seq=1 ttl=57 time=46.7 ms
+    RR:     141.85.13.15
+.128.225.226
+.128.232.178
+.128.232.177
+.97.248.33
+.158.16.1
+.16.182.15
+.16.182.15
+.158.16.1
+bytes from 104.16.182.15: icmp_seq=2 ttl=57 time=14.2 ms     (same route)
+bytes from 104.16.182.15: icmp_seq=3 ttl=57 time=18.2 ms     (same route)
+</code>
+Normally, we would need **wireshark** or **tcpdump** to see the result but fortunately, **ping** is able to understand the Record Route option. The reason for this is that it can generate it itself (see ''-R'' option). Should it have wondered that it received a Record Route option in response to a normal ICMP Echo Request? Apparently not...
+<note important>
+If your ISP is blocking IP options, try **ping**-ing your //default gateway//.
+Normally, that should work, but there is really no guarantee. A TP-Link router usually runs Linux 2.6 (at least) and does its job well. A Tenda router, however, most likely runs some garbage proprietary firmware and won't even reply to an ICMP Echo Request with IP options.
+</note>
+From this point onward, it's all you! :)
+**Task B - Traffic capture**
+Run the same experiment with ICMP Echo Request again, but this time capture the traffic using **tcpdump** and write it to a //pcap capture file//.
+<note tip>
+Consider using the ''-U'' option in **tcpdump** to avoid buffering packets if you plan to suddenly stop it with //Ctrl^C//.
+</note>
+<note important>
+If you had reachability problems at task A and IP options just can't get through, use {{:ep:labs:04:contents:tasks:ip-ops.zip|this pcap}} starting with Task C. It contains pretty much what you were supposed to get.
+As for Task B, show us that you can capture traffic correctly by targeting the //default gateway// again.
+</note>
+<solution -hidden>
+<code bash>
+$ sudo tcpdump -Uw ip-ops.pcap 'icmp and host 104.16.181.15'
+</code>
+</solution>
+**Task C - Route extraction**
+Use **tshark** to extract the Record Route payload of ICMP Echo Replies from the created //pcap//. \\
+You only need the IPs of the intermediary hops; these will be further processed in your script at Task D.
+<note tip>
+  * Check out the ''-Y'' option in ''man tshark(1)''.
+  * Look for the appropriate [[https://www.wireshark.org/docs/dfref/i/ip.html|IPv4 Display Filter]].
+  * Test filter expressions in **wireshark** before applying them in **tshark**.
+</note>
+<solution -hidden>
+<code bash>
+$ tshark -r ip-ops.pcap -Tfields -e ip.rec_rt 'icmp.type == 0 && ip.rec_rt'
+</code>
+</solution>
+**Task D - AS lookup**
+Write a //bash script// starting from your **tshark** command. The script must perform an AS lookup and display information about each registered hop (e.g.: IP, AS name, etc.), for all packets in the //pcap//. Run the script. What do you notice?
+<html>
+    <details>
+        <summary>The output should look something like this ± a few info.</summary>
+        <center>
+            <img src="https://ocw.cs.pub.ro/courses/_media/ep/labs/04/contents/tasks/ip-rr_sample.png">
+            <br>
+            <b>Figure 3:</b> Packet sent from <i>104.16.181.15</i> to <i>172.19.7.205</i>. In green are enumerated middleboxes (e.g.: routers) that added the IP of their outgoing interface to the buffer of the RR option. Not all may do so, depending on the implementation of their networking stack! In blue we have part of the publicly available information regarding the Autonomous System that said IP addresses belong to.
+        </center>
+    </details>
+</html>
+<note tip>
+In order to get the required information, use the **whois** tool.
+<code bash>
+$ whois ${SOME_IP}
+$ whois -h whois.cymru.com -- -v ${SOME_IP}
+</code>
+Want to make your script's output look pretty? Remember that you have [[https://www.lihaoyi.com/post/BuildyourownCommandLinewithANSIescapecodes.html|ANSI color escape codes]] :)
+</note>
+<solution -hidden>
+<file bash analyze_rr.sh>
+#!/bin/bash
+# analize_rr.sh - perform AS lookup on IP RR content
+#   $1 : [required] path to a pcap file
+###############################################################################
+############################## ANSI ESCAPE CODES ##############################
+###############################################################################
+ANSI_RED='\033[31m'
+ANSI_GREEN='\033[32m'
+ANSI_YELLOW='\033[33m'
+ANSI_BLUE='\033[34m'
+ANSI_PURPLE='\033[35m'
+ANSI_CYAN='\033[36m'
+ANSI_BOLD='\033[1m'
+ANSI_UNBOLD='\033[2m'
+ANSI_CLEAR='\033[0m'
+###############################################################################
+################################# ENTRY POINT #################################
+###############################################################################
+# argument check
+if [[ $# -ne 1 || ! -f $1 ]]; then
+    echo 'Usage: ./analize_rr.sh PCAP_FILE'
+    exit 1
+fi
+# parse ICMP Echo Replies in pcap while extracting relevant fields
+while read -r SRC_IP DST_IP ROUTE; do
+    # print info about src and dst IP for current packet
+    printf '%b%b%15s%b ==> %b%b%-15s%b\n'                   \
+        ${ANSI_YELLOW} ${ANSI_BOLD} ${SRC_IP} ${ANSI_CLEAR} \
+        ${ANSI_YELLOW} ${ANSI_BOLD} ${DST_IP} ${ANSI_CLEAR}
+    # parse each hop in recorded route
+    while read -d , -r HOP_IP; do
+        # print recorded hop IP
+        printf '\t%b%bHop: %b%s%b\n'   \
+            ${ANSI_GREEN} ${ANSI_BOLD} \
+            ${ANSI_UNBOLD} ${HOP_IP} ${ANSI_CLEAR}
+        # get organization info
+        # NOTE: whois can access either RIPE or ARIN databases
+        #       account for different formats
+        printf '\t\t%b%b%-14s: %b%s%b\n' \
+            ${ANSI_BLUE} ${ANSI_BOLD}    \
+            'Net Name' ${ANSI_UNBOLD}    \
+            "$(whois ${HOP_IP}           \
+            | grep -i 'netname'          \
+            | tail -n 1                  \
+            | awk '{$1=""; print $0}'    \
+            | xargs)"                    \
+            ${ANSI_CLEAR}
+        printf '\t\t%b%b%-14s: %b%s%b\n' \
+            ${ANSI_BLUE} ${ANSI_BOLD}    \
+            'Org Name' ${ANSI_UNBOLD}    \
+            "$(whois ${HOP_IP}           \
+            | grep -i 'orgname'          \
+            | tail -n 1                  \
+            | awk '{$1=""; print $0}'    \
+            | xargs)"                    \
+            ${ANSI_CLEAR}
+        # fetch AS info in one request & print
+        IFS='|' read -r AS_NUM IP BGP_PREFIX COUNTRY REGISTRY DATE AS_NAME \
+            < <(whois -h whois.cymru.com -- -v ${HOP_IP}                   \
+              | tail -n 1                                                  \
+              | sed 's/[ ]*|[ ]*/|/g')
+        printf '\t\t%b%b%-14s: %b%s%b\n'              \
+            ${ANSI_BLUE} ${ANSI_BOLD} 'AS Num'        \
+            ${ANSI_UNBOLD} ${AS_NUM:-'NA'} ${ANSI_CLEAR}
+        printf '\t\t%b%b%-14s: %b%s%b\n'              \
+            ${ANSI_BLUE} ${ANSI_BOLD} 'BGP Prefix'    \
+            ${ANSI_UNBOLD} ${BGP_PREFIX:-'NA'} ${ANSI_CLEAR}
+        printf '\t\t%b%b%-14s: %b%s%b\n'              \
+            ${ANSI_BLUE} ${ANSI_BOLD} 'Country'       \
+            ${ANSI_UNBOLD} ${COUNTRY:-'NA'} ${ANSI_CLEAR}
+        printf '\t\t%b%b%-14s: %b%s%b\n'              \
+            ${ANSI_BLUE} ${ANSI_BOLD} 'Reg Authority' \
+            ${ANSI_UNBOLD} ${REGISTRY:-'NA'} ${ANSI_CLEAR}
+        printf '\t\t%b%b%-14s: %b%s%b\n'              \
+            ${ANSI_BLUE} ${ANSI_BOLD} 'Reg Date'      \
+            ${ANSI_UNBOLD} ${DATE:-'NA'} ${ANSI_CLEAR}
+    done <<<"${ROUTE},"
+done < <(tshark -r ${1}             `# input pcap file`        \
+                -Y 'icmp.type == 0' `# filter ICMP echo reply` \
+                -T fields           `# output format`          \
+                -e ip.src           `# print src IP`           \
+                -e ip.dst           `# print dst IP`           \
+                -e ip.rec_rt        `# print recorded route`   )
+</file>
+</solution>
+**Task E - AS lookup (part II)**
+As you might have noticed during the previous task, even DigitalOcean uses CloudFlare.
+{{:ep:labs:04:contents:tasks:docean-icmp.zip|This archive}} contains a //pcap// with ICMP Echo Request/Replies sent from the university to four VMs hosted on DigitalOcean. Run your script again, on this //pcap// and see if you can spot any interesting organization names. Then, look them up.
+Not really relevant, but here are the IP addresses of the VMs involved:
+<code>
+New York           134.122.28.219
+Frankfurt          46.101.222.105
+Singapore          178.128.213.179
+Toronto            165.22.239.70
+UPB (localhost)    10.5.0.1
+</code>
+</spoiler>

General Information

Lectures

Labs

Assignments

Archived Labs

ep/labs/061/contents/tasks/ex4.1574008157.txt.gz · Last modified: 2019/11/17 18:29 by andrei.crividenco

Show page Old revisions

Media Manager Back to top