From 557cdbebb6c956df57dee51a195eabac43b0d71c Mon Sep 17 00:00:00 2001
From: Leonid Bugaev <leonsbox@gmail.com>
Date: Sat, 4 Jul 2015 22:05:23 +0500
Subject: [PATCH] Update README.md

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 0b3baea..4428d9d 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,8 @@ sudo gor --input-raw :80 --output-tcp replay.local:28020
 gor --input-tcp replay.local:28020 --output-http http://staging.com
 ```
 
+Since Gor use raw sockets to capture traffic it require `sudo` access. Alternatively you can allow access to raw sockets like this: `sudo setcap CAP_NET_RAW=ep gor`
+
 ### Using 1 Gor instance for both listening and replaying
 It's recommended to use separate server for replaying traffic, but if you have enough CPU resources you can use single Gor instance.