ryperx

Members
  • Posts

    43
  • Joined

  • Last visited

Recent Profile Visitors

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

ryperx's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Can confirm this problem. In the moment i use a network in firewall the tunnel cant be started. Do you have 2 network cards/links maybe?
  2. Thanks, you are right, i see now the changelog. When i wrote the comment the changelog was empty for me
  3. There is an Update for the Wireguard Plugin, anybody knows the Changelog? Cant find any Info.
  4. I dont think another software would help much because as it looks like your Mainboard or Ram Modules have a problem when all Slots/Moduls installed. Do you have latest BIOS Version installed?
  5. I really like the aproach from the Dynamics Temp Plugin which also shows the CPU Temp directly in the CPU Utilisation in Dashboard
  6. I found the problem, on the opponent side was the ping on the wan port disabled, so i think wireguard needs to ping the WAN IP from the other side and the choosen udp port to work.
  7. @ljm42 I have another little problem with the server <-> server connection. When the connection is established it works fine and from every server i can ping the opponent server from both sides. The problem, after some time one server cant ping the other server and the connection is lost and cant be established from this server. I need to press the ping button on the opponent server and the tunnel works again (ping from both servers work) Anybody has an idea?
  8. Ok i will learn more about Wireguard. This is the only part what isnt correct as i understand, the server <-> server config exports the same settings as the lan <-> lan settings. So in the server <-> server configuration should be only the IP adress of the opponent wireguard/unraid server for example 192.168.1.1/32 and not the opponent LAN 192.168.1.0/24
  9. Thanks for your response Ah ok, so it is a setting for the client on the server and of course this would help in that way. My biggest problem with the wireguard plugin and the configuration is that i dont understand the peer settings in general. Is it for the client where i export the configuration or is it for the client on the server? It is really confusing for example the server <-> server configuration i configure the client on the server for connecting another server. This had me confused the most because i didnt understand that i configure there something for the client on the server and the export feature is more or less useless, but still why is there my LAN ip adress in the exportet configuration when i use server <-> server configuration. Also what is confusing me is that i can type in a private shared key into the config on the peer in the server <-> configuration or generate one. It is necessary to type in the public key from the second server and i needed so much time to figure out that this peer configuration is setting the client on the server and is not needed for exporting. When i use for example another configuration "Remote access to LAN" the settings looks exactly the same and i configure the settings for the client (laptop example) which i can export, but there is the problem when i set another IP adresses in allowed peer IP adresses nothing get exportet, only the hardcoded addresses it would be cool if it works when i type in another allowed ip adresses and it get exportet. I think it would be much more understandable when there are 2 different peer configuration, one for creating for the client on the server and one for creating connections for the external clients that will connect. Or maybe i doesnt understand the concept^^ Do you have an idea why there is this "pinging" problem i described in my second post? Why my client needs a connection to the gateway of the first tunnel? To reproduce: Create 2 tunnels and specify on tunnel 2 a peer configuration and allow only allowed peer connections to the gateway of tunnel 2. The ping on the unraid server to client will not work, when i add the gateway from tunnel 1 to the configuration the ping is working?
  10. Slowly i begin to understand how it works but i see a little security problem if someone uses only the predefined peer types without setting the firewall settings. As i see when i set in the config "Allowed IPs" only the Server IP Adress it gets copied in the config. When the user now adds another IPs adresses from the local network, these also works. So this would mean i need to create for every user an additional tunnel (and set firewall rules for networks) when the user needs other wrigts in the network because the user could add additional routes every time? Edit: Dont know if i speak with myself here but ok^^ Found out the following, pinging from my unraid server to the Remote Connected Device dont work often or for example when only connections to my server would be allowed and so i tried to debug. Found out the following. At the moment I have 2 tunnels defined Tunnel wg0 Network: 10.253.0.1 Server: 10.253.0.5 (yes this is on purpose) Tunnel wg1 Network: 10.253.1.1 Server: 10.253.1.1 Client: 10.253.1.2 When i connect a client on tunnel wg1 and i try to ping the device after success connection it isnt working. Pinging from the client the server address (10.253.1.1) is working fine. In this moment it has in Peer allowed IPs only the Tunnel wg1 Gateway defined, what is correct as i understand. When i define in the config on my client AllowedIPs also the default IP Gateway Adress (10.253.0.1/32) from Tunnel wg0, then the Ping from my unraid server to client is working. I really dont understand how this can be possible?? I didnt defined this IP anywhere on my unraid server at the moment, is it possible that wireguard still use this IP in the background? Pinging the IP Adress from my server results only in losses. I really dont understand why this happens. As it looks the unraid server pings the IP adress of the client with the Adress from Tunnel wg0. I checked the defined routes on the unraid server but they are defined correctly as i see. Also found another Bug: As i see it doesnt matter what i type into Peer allowed IPs, it will be ignored when i export the config with the eye. Testet this with server <-> server and Remote access to Server. Its funny because the setting is mandatory but it doesnt matter what i type in there^^ Feature request What i would be searching for would be a setting custom, without anything set beforehand in the allowed IPs
  11. Another problem i got, i cant get the "Remote access to server" Configuration not working, when i choose "Remote Tunneled Server" it works without a problem and it connects instant. Cant anybody help? The only config connection that is working, is when i choose Remote Tunneled Server. The other connections doesnt work. What is the difference? I would prefer only to tunnel connections to the server through the vpn not everything Edit: I found out it isnt a problem that the tunnel is not working, the problem is that the ping from unraid to client doesnt work.
  12. Is it possible that the server <-> server setting is bugged? Problem with this setting it is also routing the local networks. It gets the exact same config with routing networks as lan <-> lan Its definitly an bug, in allowed IPs should only the IP adress of the server, but it also inserts the IP adress of the LAN network. (When you press the eye for the configuration) Also it is completly useless to set anything into "Peer allowed IPs" it ignores anything i type into this field.
  13. I repost my question in the correct thread:
  14. Thanks u 2, this feature i was looking for
  15. Sorry for reanimate this old thread, but was this feature implemented? I mean that mover starts copying files in the moment a certain amount of % are reached? As i know the maximum free space setting helps that the cache cant run completly full but wouldnt trigger the mover job or am i wrong?