Is this a good configuration?

    • OMV 2.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Is this a good configuration?

      So I want to put my OMV box behind a VPN (VyprVPN), but I know that in doing so, I will break Plex's remote play capabilities. The obvious solution is then to put my PlexMediaServer on a separate appliance and have that just connect to the media library on my OMV.

      What's the smartest way to go about doing that? Back up my /opt/plexmediaserver folder, transfer it to /opt/plexmediaserver on the new machine, set Plex to run in docker like I have now, and just mount the /media/TV and /media/Movies/ folders from my mergefs partition on my OMV machine? How should I mount the shared folders? Will the VPN on the OMV machine make that difficult? Or because they are both on the same LAN will that not be an issue?
    • You don't need to do that, you can if you want that would be the easy way. But on the internet there are plenty of tutorials on how to policy based routing. Not all traffic needs to go through the vpn tunnel, depending on the destination or ports used the ip Linux stack can balance in between the default gw and the vpn gw. A good start is the OpenVPN wiki.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • I looked into policy-based routing when I switched from a commercial router to a pfSense appliance + Unifi AP setup for the house, and determined I'm far too stupid to manage that.

      If this will work, I'll look into setting up a small Plex machine. Problem is my OMV box is running on a beefy i7 with lots of RAM, and I don't want to jump down to Celeron or something like that.

      Which means I may have to dick around with policy-based routing. Ech.

      As an aside, I think you responded to my question on Sonarr and seedboxes on the Sonarr forum, so thank you for constantly helping me out.
    • lh1983 wrote:

      and then just plug my OMV box straight into OPT1?

      Sounds confusing.....i mean once you have vyprvpn configured in pfsense as a client, is just a matter of creating rules in the LAN section and choose a gateway (default or VPN). For example transmission is a PITA to configure to use VPN because of the ports, so for making it easier what i do is assign a secondary ip address of the default lan segment (or you can use a VLAN) to the server nic, then configure transmission to bind to that secondary IP address. Then in pfsense set that that source ip in lan get's all traffic forwarded through the vpn gw.


      the alias there are just private torrent websites and irc announce servers.
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • So I have my VPN set up through pfSense correctly. It is now an additional interface under my interfaces.

      My OMV box is 192.168.1.5 in my LAN ip table. It looks like Deluge has an option called "Network Interface" where I can set it to bind to a specific IP address. How do I set that up?

      I guess what I am asking is, now that I have pfSense set up that way, what firewall rules do I need to add, and how do I set up the secondary IP address to add to the "network interface" section of Deluge?
    • You can assign a secondary ip to your interface using the omv method described here

      Customize /etc/network/interfaces the OMV way [>= 1.11]


      Shell-Script

      1. #!/bin/sh
      2. #
      3. # This file is part of OpenMediaVault.
      4. #
      5. # @license http://www.gnu.org/licenses/gpl.html GPL Version 3
      6. # @author Volker Theile <volker.theile@openmediavault.org>
      7. # @copyright Copyright (c) 2009-2015 Volker Theile
      8. #
      9. # OpenMediaVault is free software: you can redistribute it and/or mod
      10. ify
      11. # it under the terms of the GNU General Public License as published b
      12. y
      13. # the Free Software Foundation, either version 3 of the License, or
      14. # any later version.
      15. #
      16. # OpenMediaVault is distributed in the hope that it will be useful,
      17. # but WITHOUT ANY WARRANTY; without even the implied warranty of
      18. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
      19. # GNU General Public License for more details.
      20. #
      21. # You should have received a copy of the GNU General Public License
      22. # along with OpenMediaVault. If not, see <http://www.gnu.org/licenses
      23. />.
      24. set -e
      25. . /etc/default/openmediavault
      26. . /usr/share/openmediavault/scripts/helper-functions
      27. OMV_INTERFACES_CONFIG=${OMV_INTERFACES_CONFIG:-"/etc/network/interfac
      28. es"}
      29. cat <<EOF >> ${OMV_INTERFACES_CONFIG}
      30. ##IP address to bind transmission for using the vpn gateway
      31. iface eth0 inet static
      32. address 10.10.10.45
      33. netmask 255.255.255.0
      34. dns-nameservers 10.10.10.1 8.8.8.8
      35. dns-search lan
      36. EOF
      Display All
      This file I used some time ago for transmission. Adjust to your requirements of nic name and ip space. About deluge you'll need to consult about that in their docs
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • OK, here's my script:


      Source Code

      1. Shell-Script
      2. #!/bin/sh
      3. #
      4. # This file is part of OpenMediaVault.
      5. #
      6. # @license http://www.gnu.org/licenses/gpl.html GPL Version 3
      7. # @author Volker Theile <volker.theile@openmediavault.org>
      8. # @copyright Copyright (c) 2009-2015 Volker Theile
      9. #
      10. # OpenMediaVault is free software: you can redistribute it and/or mod
      11. ify
      12. # it under the terms of the GNU General Public License as published b
      13. y
      14. # the Free Software Foundation, either version 3 of the License, or
      15. # any later version.
      16. #
      17. # OpenMediaVault is distributed in the hope that it will be useful,
      18. # but WITHOUT ANY WARRANTY; without even the implied warranty of
      19. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
      20. # GNU General Public License for more details.
      21. #
      22. # You should have received a copy of the GNU General Public License
      23. # along with OpenMediaVault. If not, see <http://www.gnu.org/licenses
      24. />.
      25. set -e
      26. . /etc/default/openmediavault
      27. . /usr/share/openmediavault/scripts/helper-functions
      28. OMV_INTERFACES_CONFIG=${OMV_INTERFACES_CONFIG:-"/etc/network/interfac
      29. es"}
      30. cat <<EOF >> ${OMV_INTERFACES_CONFIG}
      31. ##IP address to bind deluge for using the vpn gateway
      32. iface eth0 inet static
      33. address 192.168.1.10
      34. netmask 255.255.255.0
      35. dns-nameservers 8.8.8.8
      36. dns-search lan
      37. EOF
      Display All
      but when I put "192.168.1.10" in my deluge "Network Interface" option field, deluge will no connect to torrents.

      Also I don't know how to set up my firewall rules.
    • OK, here's my script:


      Source Code

      1. Shell-Script
      2. #!/bin/sh
      3. #
      4. # This file is part of OpenMediaVault.
      5. #
      6. # @license http://www.gnu.org/licenses/gpl.html GPL Version 3
      7. # @author Volker Theile <volker.theile@openmediavault.org>
      8. # @copyright Copyright (c) 2009-2015 Volker Theile
      9. #
      10. # OpenMediaVault is free software: you can redistribute it and/or mod
      11. ify
      12. # it under the terms of the GNU General Public License as published b
      13. y
      14. # the Free Software Foundation, either version 3 of the License, or
      15. # any later version.
      16. #
      17. # OpenMediaVault is distributed in the hope that it will be useful,
      18. # but WITHOUT ANY WARRANTY; without even the implied warranty of
      19. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
      20. # GNU General Public License for more details.
      21. #
      22. # You should have received a copy of the GNU General Public License
      23. # along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>.
      24. set -e
      25. . /etc/default/openmediavault
      26. . /usr/share/openmediavault/scripts/helper-functions
      27. OMV_INTERFACES_CONFIG=${OMV_INTERFACES_CONFIG:-"/etc/network/interfac
      28. es"}
      29. cat <<EOF >> ${OMV_INTERFACES_CONFIG}
      30. ##IP address to bind deluge for using the vpn gateway
      31. iface eth0 inet static
      32. address 192.168.1.10
      33. netmask 255.255.255.0
      34. dns-nameservers 8.8.8.8
      35. dns-search lan
      36. EOF
      Display All
      But I still can't seem to get this to work.

      The post was edited 1 time, last by subzero79: correct incorrect line ().

    • Lots of errors there from copy-paste from my mobile, use this one


      Shell-Script

      1. #!/bin/sh
      2. set -e
      3. . /etc/default/openmediavault
      4. . /usr/share/openmediavault/scripts/helper-functions
      5. OMV_INTERFACES_CONFIG=${OMV_INTERFACES_CONFIG:-"/etc/network/interfaces"}
      6. cat <<EOF >> ${OMV_INTERFACES_CONFIG}
      7. ##IP address to bind transmission for using the vpn gateway
      8. iface eth0 inet static
      9. address 192.168.1.10
      10. netmask 255.255.255.0
      11. dns-nameservers 8.8.8.8
      12. dns-search lan
      13. EOF
      Display All
      After that make it executable

      chmod +x /usr/share/openmediavault/mkconf/interfaces.d/50nameofthefile

      run

      omv-mkconf interfaces

      Reboot and check you know have two ip addresses assigned to the interface

      ip addr show eth0

      The rule? just select the src ip address and tell it to use the vpn gateway in pfsense
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server

      The post was edited 1 time, last by subzero79: Edit shebang ().

    • Alright, that fixed it. I've now bound 192.168.1.6 to the OMV box as well. I changed the bind address in rtorrent (I switched from Deluge) and I can connect to it now via 192.168.1.6. I've created a rule in pfSense firewall that says:





      But a torrent that I add to rtorrent doesn't connect to anything and download. Is there anything else I need to add?