diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000000000000000000000000000000000000..997ca2f846554a247d3cc3f653e17dd1d5a15ffe
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+.vagrant
\ No newline at end of file
diff --git a/README.md b/README.md
index 27292921da7469d4a0c03eac1ff1061027facd31..db896e2a930b8d96566d87cf656ec290925c6fe3 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,119 @@
-# wireguard-attack
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.limos.fr/borlonjo/wireguard-attack.git
-git branch -M master
-git push -uf origin master
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.limos.fr/borlonjo/wireguard-attack/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+<p align="center">
+  <a href="" rel="noopener">
+ <img width=200px height=200px src="./resources/logo.png" alt="Project logo"></a>
+</p>
+
+<h3 align="center">Wireguard Attack</h3>
+
+<div align="center">
+
+[![Status](https://img.shields.io/badge/status-active-success.svg)]()
+[![Gitlab Issues](https://img.shields.io/github/issues/kylelobo/The-Documentation-Compendium.svg)](https://gitlab.limos.fr/borlonjo/wireguard-attack/-/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/kylelobo/The-Documentation-Compendium.svg)](https://gitlab.limos.fr/borlonjo/wireguard-attack/-/merge_requests)
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](/LICENSE)
+
+</div>
+
+---
+
+<p align="center"> This repository is a POC demonstrating the compromission of a Wireguard connection allowing to discover identity of a user.
+    <br> 
+</p>
+
+## 📝 Table of Contents
+
+- [About](#about)
+- [Getting Started](#getting_started)
+- [Deployment](#deployment)
+- [Usage](#usage)
+- [Built Using](#built_using)
+- [TODO](../TODO.md)
+- [Contributing](../CONTRIBUTING.md)
+- [Authors](#authors)
+- [Acknowledgments](#acknowledgement)
+
+## 🧐 About <a name = "about"></a>
+
+Write about 1-2 paragraphs describing the purpose of your project.
+
+## 🏁 Getting Started <a name = "getting_started"></a>
+
+These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See [deployment](#deployment) for notes on how to deploy the project on a live system.
+
+### Prerequisites
+
+You need to have VirtualBox installed on your machine along with Hashicorp Vagrant.
+
+```bash
+sudo apt install vagrant
+```
+
+### Installing
+
+A step by step series of examples that tell you how to get a development env running.
+
+Say what the step will be
+
+```bash
+git clone https://gitlab.limos.fr/borlonjo/wireguard-attack.git
+cd wireguard-attack
+```
+
+Now you can start VM using vagrant
+
+```bash
+vagrant up
+```
+
+End with an example of getting some data out of the system or using it for a little demo.
+
+<!-- ## 🔧 Running the tests <a name = "tests"></a>
+
+Explain how to run the automated tests for this system.
+
+### Break down into end to end tests
+
+Explain what these tests test and why
+
+```
+Give an example
+```
+
+### And coding style tests
+
+Explain what these tests test and why
+
+```
+Give an example
+``` -->
+
+## 🎈 Usage <a name="usage"></a>
+
+To connect to VM using ssh, you can issue :
+
+```bash
+vagrant ssh <vm_name>
+```
+
+<!-- ## 🚀 Deployment <a name = "deployment"></a>
+
+Add additional notes about how to deploy this on a live system.
+
+## ⛏️ Built Using <a name = "built_using"></a>
+
+- [MongoDB](https://www.mongodb.com/) - Database
+- [Express](https://expressjs.com/) - Server Framework
+- [VueJs](https://vuejs.org/) - Web Framework
+- [NodeJs](https://nodejs.org/en/) - Server Environment
+
+## ✍️ Authors <a name = "authors"></a>
+
+- [@kylelobo](https://github.com/kylelobo) - Idea & Initial work
+
+See also the list of [contributors](https://github.com/kylelobo/The-Documentation-Compendium/contributors) who participated in this project.
+
+## 🎉 Acknowledgements <a name = "acknowledgement"></a>
+
+- Hat tip to anyone whose code was used
+- Inspiration
+- References -->
diff --git a/Vagrantfile b/Vagrantfile
new file mode 100644
index 0000000000000000000000000000000000000000..23d25d2289b7869a9667cb159bc0aafbd918bdfb
--- /dev/null
+++ b/Vagrantfile
@@ -0,0 +1,118 @@
+Vagrant.configure("2") do |config|
+  # Using latest Debian amd64 image
+  config.vm.box = "debian/bookworm64"
+
+  # Define three virtual machines with specific names and IP addresses
+  vm_configurations = [
+    { name: "wireguard-server", ip: "10.13.37.10" },
+    { name: "wireguard-client", ip: "10.13.37.11" },
+    { name: "wireguard-attacker", ip: "10.13.37.12" }
+  ]
+
+  vm_configurations.each do |vm_config|
+    config.vm.define vm_config[:name] do |node|
+
+      # Naming VMs
+      node.vm.hostname = vm_config[:name]
+
+      # Configure a private network with a specific IP address
+      node.vm.network "private_network", ip: vm_config[:ip], virtualbox__intnet: true
+
+      # Customize VM system settings
+      node.vm.provider "virtualbox" do |vb|
+        vb.name = vm_config[:name]
+        vb.memory = "1024"
+        vb.cpus = 1
+      end
+
+      # Mount local directories on VMs
+      if vm_config[:name] == "wireguard-client"
+        node.vm.synced_folder "./wireguard-client", "/etc/wireguard"
+      end
+      if vm_config[:name] == "wireguard-server"
+        node.vm.synced_folder "./wireguard-server", "/srv/wireguard-server"
+      end
+      if vm_config[:name] == "wireguard-attacker"
+        node.vm.synced_folder "./wireguard-attacker", "/srv/wireguard-attacker"
+      end
+
+      # Allow Promiscuous Mode on attacker machine
+      if vm_config[:name] == "wireguard-attacker"
+        node.vm.provider "virtualbox" do |vb|
+          vb.customize ['modifyvm', :id, '--nicpromisc2', 'allow-all']
+        end
+      end
+
+      # Shell provisioning
+      if vm_config[:name] == "wireguard-server"
+        node.vm.provision "shell", inline: <<-SHELL
+          #!/bin/bash
+          echo "Hello from #{vm_config[:name]} with IP: #{vm_config[:ip]}!"
+
+          # Install docker if not already done
+          if ! docker ps > /dev/null; then
+            # Add Docker's official GPG key:
+            sudo apt-get -y update
+            sudo apt-get -y install ca-certificates curl gnupg
+            sudo install -m 0755 -d /etc/apt/keyrings
+            [[ -f /etc/apt/keyrings/docker.gpg ]] || curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --batch --dearmor -o /etc/apt/keyrings/docker.gpg
+            sudo chmod a+r /etc/apt/keyrings/docker.gpg
+
+            # Add the repository to Apt sources:
+            echo \
+              "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
+              $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
+              sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
+            sudo apt-get -y update
+
+            sudo apt-get -y install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+
+            # Add vagrant user to docker group
+            sudo adduser vagrant docker
+          else
+            echo "Docker already installed"
+          fi
+
+          # Some customizations
+          sudo apt-get -y install vim
+          sed -ri 's/^( *)#alias (.*)/\\1alias \\2/' /home/vagrant/.bashrc
+        SHELL
+      end
+
+      if vm_config[:name] == "wireguard-client"
+        node.vm.provision "shell", inline: <<-SHELL
+          #!/bin/bash
+          echo "Hello from #{vm_config[:name]} with IP: #{vm_config[:ip]}!"
+
+          # Install wireguard along with resolvconf
+          sudo apt-get -y install wireguard resolvconf
+
+          # Some customizations
+          sudo apt-get -y install vim
+          sed -ri 's/^( *)#alias (.*)/\\1alias \\2/' /home/vagrant/.bashrc
+        SHELL
+      end
+
+      if vm_config[:name] == "wireguard-attacker"
+        node.vm.provision "shell", inline: <<-SHELL
+          #!/bin/bash
+          echo "Hello from #{vm_config[:name]} with IP: #{vm_config[:ip]}!"
+
+          # Set interface on promiscuous mode at system level
+          sudo ip link set eth1 promisc on
+
+          # Install tshark (dumpcap)
+          echo "wireshark-common wireshark-common/install-setuid boolean true" | sudo debconf-set-selections
+          sudo apt-get -y install tshark
+
+          # Add vagrant user to wireshark group
+          sudo adduser vagrant wireshark
+
+          # Some customizations
+          sudo apt-get -y install vim
+          sed -ri 's/^( *)#alias (.*)/\\1alias \\2/' /home/vagrant/.bashrc
+        SHELL
+      end
+    end
+  end
+end
diff --git a/resources/logo.png b/resources/logo.png
new file mode 100644
index 0000000000000000000000000000000000000000..4c9acdb002671e70fab6afd095410685edd8c9a5
Binary files /dev/null and b/resources/logo.png differ
diff --git a/wireguard-attacker/.gitkeep b/wireguard-attacker/.gitkeep
new file mode 100644
index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
diff --git a/wireguard-client/wg0.conf b/wireguard-client/wg0.conf
new file mode 100644
index 0000000000000000000000000000000000000000..36eadc76f65fdceaf73a11b2a3b170733970df4b
--- /dev/null
+++ b/wireguard-client/wg0.conf
@@ -0,0 +1,11 @@
+[Interface]
+Address = 10.42.42.2
+PrivateKey = 4K7psRloW4i1aH+gSVYQ4fVfJPEx0z7etmGrWnfb73Y=
+ListenPort = 51820
+DNS = 10.42.42.1
+
+[Peer]
+PublicKey = +O7mAJK0m7Ts62WuP1Et1/RanAq5yFPAgDxuyR9TtD4=
+PresharedKey = XqxvhqBMhDyQKiMZfRHc73t/ra++yQU47hnXwl5KaOI=
+Endpoint = 10.13.37.10:51820
+AllowedIPs = 0.0.0.0/0
diff --git a/wireguard-server/compose.yml b/wireguard-server/compose.yml
new file mode 100644
index 0000000000000000000000000000000000000000..b9ea022dc9e8ff5230a4c5a7ca349dab228bc2b1
--- /dev/null
+++ b/wireguard-server/compose.yml
@@ -0,0 +1,29 @@
+---
+version: "2.1"
+services:
+  wireguard:
+    image: lscr.io/linuxserver/wireguard:latest
+    container_name: wireguard
+    cap_add:
+      - NET_ADMIN
+      - SYS_MODULE #optional
+    environment:
+      - PUID=1000
+      - PGID=1000
+      - TZ=Etc/UTC
+      - SERVERURL=10.13.37.10 #optional
+      - SERVERPORT=51820 #optional
+      - PEERS=1 #optional
+      - PEERDNS=auto #optional
+      - INTERNAL_SUBNET=10.42.42.0 #optional
+      - ALLOWEDIPS=0.0.0.0/0 #optional
+      - PERSISTENTKEEPALIVE_PEERS= #optional
+      - LOG_CONFS=true #optional
+    volumes:
+      - ./config:/config
+      - /lib/modules:/lib/modules #optional
+    ports:
+      - 51820:51820/udp
+    sysctls:
+      - net.ipv4.conf.all.src_valid_mark=1
+    restart: unless-stopped
diff --git a/wireguard-server/config/.donoteditthisfile b/wireguard-server/config/.donoteditthisfile
new file mode 100644
index 0000000000000000000000000000000000000000..d94fd43e258128955e9dd7086de5fe14ef8dec6f
--- /dev/null
+++ b/wireguard-server/config/.donoteditthisfile
@@ -0,0 +1,7 @@
+ORIG_SERVERURL="10.13.37.10"
+ORIG_SERVERPORT="51820"
+ORIG_PEERDNS="10.42.42.1"
+ORIG_PEERS="1"
+ORIG_INTERFACE="10.42.42"
+ORIG_ALLOWEDIPS="0.0.0.0/0"
+ORIG_PERSISTENTKEEPALIVE_PEERS=""
diff --git a/wireguard-server/config/coredns/Corefile b/wireguard-server/config/coredns/Corefile
new file mode 100644
index 0000000000000000000000000000000000000000..12da818704aeef139284d91422ab3d989aaf8677
--- /dev/null
+++ b/wireguard-server/config/coredns/Corefile
@@ -0,0 +1,5 @@
+. {
+    loop
+    health
+    forward . /etc/resolv.conf
+}
diff --git a/wireguard-server/config/peer1/peer1.conf b/wireguard-server/config/peer1/peer1.conf
new file mode 100644
index 0000000000000000000000000000000000000000..36eadc76f65fdceaf73a11b2a3b170733970df4b
--- /dev/null
+++ b/wireguard-server/config/peer1/peer1.conf
@@ -0,0 +1,11 @@
+[Interface]
+Address = 10.42.42.2
+PrivateKey = 4K7psRloW4i1aH+gSVYQ4fVfJPEx0z7etmGrWnfb73Y=
+ListenPort = 51820
+DNS = 10.42.42.1
+
+[Peer]
+PublicKey = +O7mAJK0m7Ts62WuP1Et1/RanAq5yFPAgDxuyR9TtD4=
+PresharedKey = XqxvhqBMhDyQKiMZfRHc73t/ra++yQU47hnXwl5KaOI=
+Endpoint = 10.13.37.10:51820
+AllowedIPs = 0.0.0.0/0
diff --git a/wireguard-server/config/peer1/peer1.png b/wireguard-server/config/peer1/peer1.png
new file mode 100644
index 0000000000000000000000000000000000000000..f08bca4e63f37afcb6d1abc2c5b51da35f7fe1bc
Binary files /dev/null and b/wireguard-server/config/peer1/peer1.png differ
diff --git a/wireguard-server/config/peer1/presharedkey-peer1 b/wireguard-server/config/peer1/presharedkey-peer1
new file mode 100644
index 0000000000000000000000000000000000000000..68b5a0918a42ba7cf7b5038a972045119e3d4719
--- /dev/null
+++ b/wireguard-server/config/peer1/presharedkey-peer1
@@ -0,0 +1 @@
+XqxvhqBMhDyQKiMZfRHc73t/ra++yQU47hnXwl5KaOI=
diff --git a/wireguard-server/config/peer1/privatekey-peer1 b/wireguard-server/config/peer1/privatekey-peer1
new file mode 100644
index 0000000000000000000000000000000000000000..a696fcda1f29708042fff068158eae7183eec71f
--- /dev/null
+++ b/wireguard-server/config/peer1/privatekey-peer1
@@ -0,0 +1 @@
+4K7psRloW4i1aH+gSVYQ4fVfJPEx0z7etmGrWnfb73Y=
diff --git a/wireguard-server/config/peer1/publickey-peer1 b/wireguard-server/config/peer1/publickey-peer1
new file mode 100644
index 0000000000000000000000000000000000000000..f1bed7c12653b8a85537dd6fcd24d534f573f9ac
--- /dev/null
+++ b/wireguard-server/config/peer1/publickey-peer1
@@ -0,0 +1 @@
+85Ey6fLDcFadWd+MRPHAuBEAHJ6MIUbl2jNsCZJXmRI=
diff --git a/wireguard-server/config/server/privatekey-server b/wireguard-server/config/server/privatekey-server
new file mode 100644
index 0000000000000000000000000000000000000000..fe27a5503f090cb7b5b0a663a526e701f421842c
--- /dev/null
+++ b/wireguard-server/config/server/privatekey-server
@@ -0,0 +1 @@
+WIg+gqSQk5nRwBMisXLlY49EqKkrvEjq7yPHdgMj9Ws=
diff --git a/wireguard-server/config/server/publickey-server b/wireguard-server/config/server/publickey-server
new file mode 100644
index 0000000000000000000000000000000000000000..f43e2468a44958413d14371facb21c5176b124a2
--- /dev/null
+++ b/wireguard-server/config/server/publickey-server
@@ -0,0 +1 @@
++O7mAJK0m7Ts62WuP1Et1/RanAq5yFPAgDxuyR9TtD4=
diff --git a/wireguard-server/config/templates/peer.conf b/wireguard-server/config/templates/peer.conf
new file mode 100644
index 0000000000000000000000000000000000000000..d987dba98b8594ed72c18f1877051acae11a858f
--- /dev/null
+++ b/wireguard-server/config/templates/peer.conf
@@ -0,0 +1,11 @@
+[Interface]
+Address = ${CLIENT_IP}
+PrivateKey = $(cat /config/${PEER_ID}/privatekey-${PEER_ID})
+ListenPort = 51820
+DNS = ${PEERDNS}
+
+[Peer]
+PublicKey = $(cat /config/server/publickey-server)
+PresharedKey = $(cat /config/${PEER_ID}/presharedkey-${PEER_ID})
+Endpoint = ${SERVERURL}:${SERVERPORT}
+AllowedIPs = ${ALLOWEDIPS}
diff --git a/wireguard-server/config/templates/server.conf b/wireguard-server/config/templates/server.conf
new file mode 100644
index 0000000000000000000000000000000000000000..757682d654d042d4f600e766321a65e7de4276d7
--- /dev/null
+++ b/wireguard-server/config/templates/server.conf
@@ -0,0 +1,6 @@
+[Interface]
+Address = ${INTERFACE}.1
+ListenPort = 51820
+PrivateKey = $(cat /config/server/privatekey-server)
+PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE
+PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth+ -j MASQUERADE
diff --git a/wireguard-server/config/wg_confs/wg0.conf b/wireguard-server/config/wg_confs/wg0.conf
new file mode 100644
index 0000000000000000000000000000000000000000..d64a9c8ddd68329a85163ed54c690fc5dcee8103
--- /dev/null
+++ b/wireguard-server/config/wg_confs/wg0.conf
@@ -0,0 +1,13 @@
+[Interface]
+Address = 10.42.42.1
+ListenPort = 51820
+PrivateKey = WIg+gqSQk5nRwBMisXLlY49EqKkrvEjq7yPHdgMj9Ws=
+PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE
+PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth+ -j MASQUERADE
+
+[Peer]
+# peer1
+PublicKey = 85Ey6fLDcFadWd+MRPHAuBEAHJ6MIUbl2jNsCZJXmRI=
+PresharedKey = XqxvhqBMhDyQKiMZfRHc73t/ra++yQU47hnXwl5KaOI=
+AllowedIPs = 10.42.42.2/32
+