Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
fuss:openwrt [2019/03/01 17:11] – [Create TAP Interface on Boot] office | fuss:openwrt [2020/05/06 12:53] – [Getting Python Running Properly] office |
---|
| |
To resolve the issue, the ''cygwin'' terminal information from ''C:\cygwin64\usr\share\terminfo\63\cygwin'' (assuming the cygwin install root is at ''C:\cygwin64'') should be copied over to ''/usr/share/terminfo/c/cygwin''. Note that the ''terminfo'' OpenWrt package does not contain the ''c'' directory under ''/usr/share/terminfo'' such that it will have to be created before copying over the file. | To resolve the issue, the ''cygwin'' terminal information from ''C:\cygwin64\usr\share\terminfo\63\cygwin'' (assuming the cygwin install root is at ''C:\cygwin64'') should be copied over to ''/usr/share/terminfo/c/cygwin''. Note that the ''terminfo'' OpenWrt package does not contain the ''c'' directory under ''/usr/share/terminfo'' such that it will have to be created before copying over the file. |
| |
| ====== Making Samba Bind to Interfaces ====== |
| |
| On OpenWrt version ''18.06.1'', the Samba template files contains a variable that should be interpolated: |
| <code> |
| interfaces = |INTERFACES| |
| </code> |
| |
| unfortunately, the interfaces do not seem to be configurable via LuCi and even using ''uci'' to set the variable ''samba.@samba[0].interfaces'' to some value will only make OpenWrt interpolate an empty string instead of the configured value. |
| |
| Seeing that the interfaces to listen on cannot be configured via LuCi, removing the ''interfaces = |INTERFACES|'' line and hardcoding the interfaces to listen on seems to be the best option. |
| |
| ====== Getting Python Running Properly ====== |
| |
| Unfortunately for quite a few releases (LEDE), the python ''setuptools'' package seems to be broken such that running depending software may bomb out with: |
| <code> |
| pkg_resources.DistributionNotFound: The 'setuptools' distribution was not found and is required by |
| </code> |
| |
| The solution is to install ''pip'' via: |
| <code bash> |
| opkg install python-pip |
| </code> |
| |
| and then reinstall ''pip'' and ''setuptools'': |
| <code bash> |
| pip install -U pip setuptools |
| </code> |
| |
| ====== 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"™ the following should be easy to accomplish via the interface: |
| |
| * ensure that the OpenVPN server (or client configuration file) contains ''redirect-gateway def1'', |
| * using the OpenWrt interface: ''Network'' -> ''Interfaces'' and for each WAN interface, click ''Edit'' and then go to ''Advanced Settings'' and set the ''Interface Metric'' to a given value (ie: ''10''), |
| * using the OpenWrt interface: ''Network'' -> ''Interfaces'' open up the OpenVPN interface, go to ''Advanced Settings'' and set the ''Interface Metric'' to a value lower than all WAN interfaces from the previous step (ie: ''1''). |
| |
| OpenWrt does not do this automatically even if ''redirect-gateway def1'' is pushed by the server. |
| |
| |
| |