Jump to content

hdlineage

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hdlineage

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for your help. We have very similar config except I have the unraid on the vlan as well. Turns out it was the two interfaces that's causing trouble. Somehow if unraid has an interface that is on the same subnet/vlan as docker, you can't access docker no matter what. For me it doesn't really matter where unraid is, but I do wonder if there is a way to for unraid to be on the same subnet as docker.
  2. Can you share your setup including how you configured the unraid VLAN? My unraid has two interfaces: br0 with subnet 192.168.1.0/24 (unraid host ip: 192.168.1.10) gateway(router) 192.168.1.1 br0.100 (vlan) with subnet 192.168.100.0/24 (unraid host ip: 192.168.100.10) gateway(router) 192.168.100.1 My VM and docker uses br0.100 with subnet 192.168.100.0/24 I configured wireguard to use the subnet 192.168.150.0/24 My router is configured with static route to all the subnets listed above. Whenever I'm connected via unraid wireguard I can access everything except docker (I can connect to VM on the same subnet) When routing Wireguard traffic back to unraid I could only use 192.168.100.10 but not 192.168.1.10 (this is weird since I could access unraid GUI through both IP which means the two interfaces were working normally, maybe wireguard pick one interface to listen on?) With this setup I could not access docker on the 192.168.100.0/24, but was able to access VM on the same subnet. However, when i connect to wireguard installed on the VM, there is no problem at all.
  3. After two days of trying the unraid implementation of wireguard, here is my summary of what works and what doesn't work: 1. Simple connection (if you dont have any vlan or vlan interfaces on unraid) between unraid sever and windows client works in "Lan mode" and "Tunnel mode" 2. Even when routed properly on router, if your docker is on a separate subnet (ie vlan), you will still be blocked, however, VM on a different vlan can be reached 3. Windows client currently only supports one connection/interface at a time, there is a workaround to add more interface but is not elegant. Not being able to reach docker on a different subnet was the deal breaker for me, so I stopped using unraid for wireguard. When wireguard is installed on a VM it works perfectly, you can reach everything including docker on a vlan. Edit: turns out it was vlan/docker setting issue, see below
  4. Multiple interfaces/connections on Windows client. Hello I have a question regarding connecting to multiple servers on Windows. The wireguard client on Windows only allows one connection at a time. Is there a way to establish two connections with two separate interfaces? I have two servers on two different subnets and I can't seem to find a way to connect them simultaneously. There is also very little documentation on the windows client.
  5. Hello I have a question regarding connecting to multiple servers on Windows. The wireguard client on Windows only allows one connection at a time. Is there a way to establish two connections with two separate interfaces? I have two servers on two different subnets and I can't seem to find a way to connect them simultaneously. There is also very little documentation on the windows client.