• [6.12] SSH fails to start when "normal" interfaces only have IPv4 but "extra" interfaces have IPv6


    EDACerton
    • Minor

    Posting this on behalf of multiple Tailscale plugin users.

    Related Discussions

    https://forums.unraid.net/topic/136889-plugin-tailscale/page/7/#comment-1272479 (contains diagnostics)

    https://github.com/dkaser/unraid-tailscale/issues/57 (further discussion, includes the relevant configuration file)

    Symptoms

    SSH will fail to start when:

    • Normal/Wireguard interfaces only have IPv4 addresses, and
    • Extra (e.g., tailscale) interfaces have IPv4 + IPv6 addresses.

     

    In this configuration, the sshd_config file is created with the following information:

     

    Port 22
    AddressFamily inet
    ListenAddress 192.168.1.66
    ListenAddress 100.69.69.16
    ListenAddress fd7a:115c:a1e0:ab12:4843:cd96:6245:4510

     

    This is an invalid configuration, since "AddressFamily inet" forces sshd to only accept IPv4 addresses. As a result, the service fails to start.

    Fix

    The check() function in /etc/rc.d/rc.library.source does not consider "extra" interfaces when setting the values of $ipv4 and $ipv6. It then uses these variables to determine if AddressFamily should be set to inet, inet6, or any.

     

    /etc/rc.d/rc.library.source should either consider extra interfaces when setting the sshd family, or AddressFamily should always be set to any.

    • Upvote 2



    User Feedback

    Recommended Comments



    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.