From 27780f3199d17b38af2574f483498ec3ba52e807 Mon Sep 17 00:00:00 2001
From: JsBergbau <37013344+JsBergbau@users.noreply.github.com>
Date: Mon, 4 Oct 2021 09:34:15 +0200
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 618cefc..93bc95d 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,10 @@ Configuration and usage of bind to interface is very simple. Example of how to r
 Instead of specifying the parameters in the same line you could also export them like `export DNS_OVERRIDE_IP=8.8.8.8`. In this case interface ovpn is a VPN provider but configured via option `route-nopull`, 
 so your internet traffic still goes via your normal internet connection without VPN.
 
+### Specifying absolute path 
+
+Especially when using more complex scripts or programs, that use another working directory than the current one, you have to specify the absolute path to `bindToInterface.so`, otherwise an error message will be printed, that it couldn't be loaded. Example when bindToInterface.so is located at `/opt/bindToInterface/bindToInterface.so`: `BIND_INTERFACE=ovpn DNS_OVERRIDE_IP=8.8.8.8 LD_PRELOAD=/opt/bindToInterface/bindToInterface.so curl ifconfig.me`
+
 ### BIND_INTERFACE
 
 This is the essential part. If not specified program will warn you, however it will not refuse the connection.