Jump to content
  • [6.12.4] WireGuard different behavior depending on whether array is on or off


    Screamy
    • Solved Minor

    Hello,

     

    I have activated WireGuard via the VPN Manager. I use the default settings:
     

    Unraid IP: 192.168.1.199

    Tunnel

    • Local tunnel network pool: 10.253.0.0
    • Local tunnel address: 10.253.0.1
    • Local server uses NAT: Yes

    Peer 1

    • Remote access to LAN
    • 10.253.0.2

     

    Now I connected via Smartphone (Android) and WireGuard App.

     

    Scenario A: Array is stopped (off) => This is fine

    • I can access Unraid but not the Shares (Array is down!)
    • I can access other PCs in LAN like 192.168.1.117

     

    Scenario B: Array is started (on) => Here is a problem!

    • I can access Unraid and all Shares
    • I can access Docker Services like NextCloud
    • I can not access other PCs in LAN like 192.168.1.117

     

    Why is there a different behavior? What can I do to fix the problem?

    Scenario B should also be able to access the devices (e.g. 192.168.1.117) in the LAN.


    I hope someone can help me with my problem. Thank you very much.




    User Feedback

    Recommended Comments


    While this is specifically for tunnled access, the same would apply for lan access, depending on if you use ipvlan or macvlan you can do the following.
     


     

    • Like 1
    Link to comment

    Thanks for your help.

    I haven't really changed anything, but now it works for me in most cases.

     

    The main change was:
    Settings -> Docker -> Host access to custom networks: Enabled

     

    When I am connected to WireGuard, the following works:

    • Communication to all Docker with Bridge Mode
    • Communication to other Clients in LAN (e.g. FritzBox, PCs, Synology)

     

    What is not yet possible:

    • Communication to Docker in "Custom-br0 Mode" (e.g. AdGuard)

     

    At the moment, that's fine for me.

    Edited by Screamy
    Link to comment

    Now everything is working 🥳.

     

    I need to disable and enable docker. After this action the routing table changed and I get the shim-br0.

    grafik.thumb.png.59674646f06842152c22bf9d4d2dddcb.png

     

    Additionally I added static route to FritzBox:

    grafik.thumb.png.ebbdb1d9d39adec819712f86c658511d.png

     

    Summary:

    • Settings
      • Docker
        • Docker custom network type: macvlan
        • Host access to custom networks: Enabled
      • WireGuard
        • Local server uses NAT: Yes
        • Client1
          • Peer type of access: Remote access to LAN
      • FritzBox
        • Static IPv4 route
          • Network: 10.253.0.0
          • Subnetmask: 255.255.255.0
          • Gateway: 192.168.1.199
    • Result or what works now
      • Communication to all Docker with Bridge Mode

      • Communication to Docker in "Custom-br0 Mode" (e.g. AdGuard)
      • Communication to other Clients in LAN (e.g. FritzBox, PCs, Synology)
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...