Jump to content

Double_J_038

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Double_J_038

  • Rank
    Newbie

Converted

  • Gender
    Male
  • Location
    New Hampshire

Recent Profile Visitors

138 profile views
  1. Hi Everyone, Thank you for the great information in this thread. I am adding a few more tweaks and notes below in order to run the native UNRAID Dynamics Wireguard simultaneously with the Linuxserver Wireguard Docker. I now have two working versions of Wireguard running on my machine with one specifically for use with whatever Dockers I decide to add to the new Wireguard VPN. When intially created, I named my new docker "wireguard4dockers" as shown below. When downloaded, you have to add a lot of the variables into the template, so this takes time, and if you have an error (like I did the first time), you might think you have lost the data after you click the "apply" button and the template disappears; but if you go to the CA "APPS" tab, you can reinstall the template and pick right back up where you left off. First off, since you are adding this as a new docker and probably have Wireguard set up on UNRAID already, when you begin to enter your specific information into the template, change the ListenPort so you don't have a conflicting port between this Wireguard docker and the built in Wireguard in UNRAID. By Default the UNRAID Wireguard listenport is 51820, which is also the standard listenport of the Linuxserver docker. Secondly, make sure that you set your config properly so the docker saves into your "appdata" folder using, Container Path: /config and Host Path to "your specific location". I initially did not set it up properly and couldn't figure out why my folder was blank, until I realized that I did not put the slash in front of "config". Also, don't forget to add the "config" folder inside your own "wireguard4docker" folder. I also changed my internal SUBNET to something completely different from the built-in Wireguard to avoid any conflicts. Not sure if this was necessary, but I thought it couldn't hurt. Also, take note that once you get the template created and it has saved as an operational Docker, if you import a pre-made config file into your config folder for this docker, you need to change the name of the file to "wg0" (that lower case w, g and a zero) or create your new template named as "wg0". This was noted on one of the many pages of posts in the links that danofun included above. Lastly, I had to include my specific Local LAN IP Address in the config file in the "PostUp" and "PostDown" lines ...part of another tip mentioned to be added to the config file in previous posts; in my file these two lines are: PostUp=ip route add 195.168.4.0/24 via $(ip route |awk '/default/ {print $3}') dev eth0 PostDown=ip route del 195.168.4.0/24 via $(ip route |awk '/default/ {print $3}') dev eth0 .....and going this route I did NOT need to add the following environmental variable into the docker template: "LAN_NETWORK ....populated with your LAN (i.e. 192.168.1.0/24)" noted to add in the above posts. Here are a few snippets of my "wireguard4docker" template. Please note, I also downloaded the Firefox docker to use to check out connectivity, following other posts on how to link other dockers to your vpn docker. Firefox Ports to add while you are setting up the "wireguard4docker" VPN created under the "advanced view": port 7814 will be your port to use to get into the firefox webgui. Using the posts in this thread, as well and the links provided by everyone, I was able to create a fully functioning secondary Wireguard Docker VPN running in less than an hour. Proving that we can in fact use an off the shelf existing Wireguard docker template to be used as a VPN for specific Docker Containers, while at the same time utilize the built in Wireguard Controls for your other VPN needs. Thus overcoming the bottleneck and limitation of not being able to have a "VPN tunneled access" running along with another tunnel instance within the built-in UNRAID Dynamics Wireguard Program. I hope this helps others. I really haven't done anything different other than compile a few critical pieces of information under the same thread. I spend a lot of time browsing the forum for information and am always amazed at what can be found here; but having run through this process this evening I thought this additional data might be helpful for other to have. Kudo's and a big thankyou to everyone prior who pave the way for amateur's like myself who are able to stumble through to make something work and confirm what others have accomplished does in fact work. Thanks,
  2. Hi Shane, I have been running Samsung SSD Drives for 4+ years as part of a cache pool and recently just added my fourth Samsung SSD to the pool without any issues. Prior to that I had used a single spinner for the cache drive. I also use a Samsung SSD Pro Drive through unassigned devices for my Plex transcodes and for VM's. Transcoding creates a lot of writes to a drive and can burn through a warranty & lifespan pretty quickly on the lower grade SSD models. Perhaps others have had issues with Samsung SSD's, but for myself I have not. I've had an Unraid server running for 8+/- years now and have always funneled everything through the cache drives before dumping onto the storage drives. As a result I feel I get a longer lifespan out of my drives because they don't have to spin up every time something is added ... a few of my old drives have 60,000+ hours and are still chugging along. I've been using the forum for years without posting to search and solve any dilemmas that I got myself in to, so this is the first time posting on the forum. I thought I would quickly give you a reply since I have a similar setup to what you are planning to do. Have fun setting up your new server!