This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
fuss:openwrt [2019/03/01 18:35] – [Fixing Terminal Compatibility Issues with Cygwin] office | fuss:openwrt [2020/05/06 12:53] – [Getting Python Running Properly] office | ||
---|---|---|---|
Line 79: | Line 79: | ||
Seeing that the interfaces to listen on cannot be configured via LuCi, removing the '' | Seeing that the interfaces to listen on cannot be configured via LuCi, removing the '' | ||
+ | |||
+ | ====== Getting Python Running Properly ====== | ||
+ | |||
+ | Unfortunately for quite a few releases (LEDE), the python '' | ||
+ | < | ||
+ | pkg_resources.DistributionNotFound: | ||
+ | </ | ||
+ | |||
+ | The solution is to install '' | ||
+ | <code bash> | ||
+ | opkg install python-pip | ||
+ | </ | ||
+ | |||
+ | and then reinstall '' | ||
+ | <code bash> | ||
+ | pip install -U pip setuptools | ||
+ | </ | ||
+ | |||
+ | ====== Routing all Traffic through OpenVPN ====== | ||
+ | |||
+ | TL;DR: old trick, set a lower interface metric for the OpenVPN interface than the default gateway. | ||
+ | |||
+ | Since there does not seem to be an official straightforward answer to route all traffic through OpenVPN "the OpenWrt way" | ||
+ | |||
+ | * ensure that the OpenVPN server (or client configuration file) contains '' | ||
+ | * using the OpenWrt interface: '' | ||
+ | * using the OpenWrt interface: '' | ||
+ | |||
+ | OpenWrt does not do this automatically even if '' | ||
+ | |||
+ | |||
+ |