How to specify IPv6 link-local bind address in smb.conf? Announcing the arrival of Valued...

Google .dev domain strangely redirects to https

Flight departed from the gate 5 min before scheduled departure time. Refund options

two integers one line calculator

If Windows 7 doesn't support WSL, then what is "Subsystem for UNIX-based Applications"?

Did any compiler fully use 80-bit floating point?

Test print coming out spongy

What initially awakened the Balrog?

Is CEO the "profession" with the most psychopaths?

Where is the Next Backup Size entry on iOS 12?

How does the math work when buying airline miles?

Is openssl rand command cryptographically secure?

What is the difference between a "ranged attack" and a "ranged weapon attack"?

Why complex landing gears are used instead of simple,reliability and light weight muscle wire or shape memory alloys?

Delete free apps from library

What adaptations would allow standard fantasy dwarves to survive in the desert?

Mounting TV on a weird wall that has some material between the drywall and stud

What would you call this weird metallic apparatus that allows you to lift people?

In musical terms, what properties are varied by the human voice to produce different words / syllables?

Printing attributes of selection in ArcPy?

Was Kant an Intuitionist about mathematical objects?

How to change the tick of the color bar legend to black

Positioning dot before text in math mode

Simple Http Server

Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?



How to specify IPv6 link-local bind address in smb.conf?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)ubuntu karmic 9.10 samba share problemSamba upgrade from 3.0 to 3.6 broke my ADS authenticationHow do I bind to a specific link local IPv6 address other than the default?Delete link local IPv6 address alone from my machineTomcat & Java not listening on IPv6IPv6 link-local multicast vs. IPv4 broadcastSpecify interface for IPv6 host on link-local connection inside an URLIpv6: Are Link-Local adresses static?Spontaneous IPv6 DNS server with link-local addressAutoconfigure link-local IPv6 address on GRE tunnel in Linux





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







5















Using samba 4.1.17-Debian I have tried the following smb.conf entries to bind samba to the link-local ipv6 addresses



interfaces = fe80::d270:36a5:ac03:37ea%br0 fe80::/10 ::1
bind interfaces only = yes


but checking with netstat only shows smbd listening on ::1



The manual states that besides interface names addresses or address+mask can be specified, so I would expect either approach to work.





Updated config:



# ip addr show dev br0 | grep -c fe80 
1

# smb.conf
bind interfaces only = yes
interfaces = 192.168.0.0/16 ::1 127.0.0.1 fe80::%br0/64

# smbd --version
Version 4.5.12-Debian

# netstat -lnp | grep smb
tcp 0 0 192.168.0.3:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 192.168.0.3:445 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 17048/smbd
tcp6 0 0 ::1:139 :::* LISTEN 17048/smbd
tcp6 0 0 ::1:445 :::* LISTEN 17048/smbd









share|improve this question

























  • Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

    – grawity
    Jan 21 '16 at 6:07













  • br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

    – the8472
    Jan 21 '16 at 6:21




















5















Using samba 4.1.17-Debian I have tried the following smb.conf entries to bind samba to the link-local ipv6 addresses



interfaces = fe80::d270:36a5:ac03:37ea%br0 fe80::/10 ::1
bind interfaces only = yes


but checking with netstat only shows smbd listening on ::1



The manual states that besides interface names addresses or address+mask can be specified, so I would expect either approach to work.





Updated config:



# ip addr show dev br0 | grep -c fe80 
1

# smb.conf
bind interfaces only = yes
interfaces = 192.168.0.0/16 ::1 127.0.0.1 fe80::%br0/64

# smbd --version
Version 4.5.12-Debian

# netstat -lnp | grep smb
tcp 0 0 192.168.0.3:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 192.168.0.3:445 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 17048/smbd
tcp6 0 0 ::1:139 :::* LISTEN 17048/smbd
tcp6 0 0 ::1:445 :::* LISTEN 17048/smbd









share|improve this question

























  • Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

    – grawity
    Jan 21 '16 at 6:07













  • br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

    – the8472
    Jan 21 '16 at 6:21
















5












5








5








Using samba 4.1.17-Debian I have tried the following smb.conf entries to bind samba to the link-local ipv6 addresses



interfaces = fe80::d270:36a5:ac03:37ea%br0 fe80::/10 ::1
bind interfaces only = yes


but checking with netstat only shows smbd listening on ::1



The manual states that besides interface names addresses or address+mask can be specified, so I would expect either approach to work.





Updated config:



# ip addr show dev br0 | grep -c fe80 
1

# smb.conf
bind interfaces only = yes
interfaces = 192.168.0.0/16 ::1 127.0.0.1 fe80::%br0/64

# smbd --version
Version 4.5.12-Debian

# netstat -lnp | grep smb
tcp 0 0 192.168.0.3:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 192.168.0.3:445 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 17048/smbd
tcp6 0 0 ::1:139 :::* LISTEN 17048/smbd
tcp6 0 0 ::1:445 :::* LISTEN 17048/smbd









share|improve this question
















Using samba 4.1.17-Debian I have tried the following smb.conf entries to bind samba to the link-local ipv6 addresses



interfaces = fe80::d270:36a5:ac03:37ea%br0 fe80::/10 ::1
bind interfaces only = yes


but checking with netstat only shows smbd listening on ::1



The manual states that besides interface names addresses or address+mask can be specified, so I would expect either approach to work.





Updated config:



# ip addr show dev br0 | grep -c fe80 
1

# smb.conf
bind interfaces only = yes
interfaces = 192.168.0.0/16 ::1 127.0.0.1 fe80::%br0/64

# smbd --version
Version 4.5.12-Debian

# netstat -lnp | grep smb
tcp 0 0 192.168.0.3:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 192.168.0.3:445 0.0.0.0:* LISTEN 17048/smbd
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 17048/smbd
tcp6 0 0 ::1:139 :::* LISTEN 17048/smbd
tcp6 0 0 ::1:445 :::* LISTEN 17048/smbd






samba ipv6






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 3 '18 at 19:47







the8472

















asked Jan 21 '16 at 5:37









the8472the8472

347113




347113













  • Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

    – grawity
    Jan 21 '16 at 6:07













  • br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

    – the8472
    Jan 21 '16 at 6:21





















  • Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

    – grawity
    Jan 21 '16 at 6:07













  • br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

    – the8472
    Jan 21 '16 at 6:21



















Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

– grawity
Jan 21 '16 at 6:07







Wouldn't it be enough to specify br0 in that case? Binding to a specific address sounds like it could cause problems.

– grawity
Jan 21 '16 at 6:07















br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

– the8472
Jan 21 '16 at 6:21







br0 also has other addresses on which I don't want to provide smb, among them global unicast v6

– the8472
Jan 21 '16 at 6:21












2 Answers
2






active

oldest

votes


















4














After hours of struggling, try, error and reading source code.



Everything works well but you have to specify correctly.
When using IPv6 LinkLocal addresses you have to specify the interface with the "%" notation AND the prefix length in the end.



Interfaces = {Full-IPv6-address}%{interface}/{prefix length}


smb.conf (SAMPLE):



interfaces = fe80::114%eth0/64





share|improve this answer


























  • I have tried that, it doesn't work for me. I'll update my question.

    – the8472
    Mar 3 '18 at 19:29











  • "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

    – Martha Gottsumpf
    Mar 4 '18 at 22:48













  • Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

    – the8472
    Mar 5 '18 at 20:25








  • 1





    @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

    – Martha Gottsumpf
    Mar 8 '18 at 9:10





















0














The best way to deal with IPv6 is not to use link local adresses but unique local instead.



Looks like "bind interfaces only" option makes IPv6 link local address not listened even if correctly written in smb.conf



I've tested successfully the use of IPv6 unique local address on debian linux and windows 10 to exchange files via samba from a linux server to a windows workstation.



In my configuration, the unique local address have been manualy configured in debian and windows so the SLAAC is still working to provide global IPv6 address. No need to use DHCPv6 to use this type of address.






share|improve this answer








New contributor




wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1029279%2fhow-to-specify-ipv6-link-local-bind-address-in-smb-conf%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    After hours of struggling, try, error and reading source code.



    Everything works well but you have to specify correctly.
    When using IPv6 LinkLocal addresses you have to specify the interface with the "%" notation AND the prefix length in the end.



    Interfaces = {Full-IPv6-address}%{interface}/{prefix length}


    smb.conf (SAMPLE):



    interfaces = fe80::114%eth0/64





    share|improve this answer


























    • I have tried that, it doesn't work for me. I'll update my question.

      – the8472
      Mar 3 '18 at 19:29











    • "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

      – Martha Gottsumpf
      Mar 4 '18 at 22:48













    • Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

      – the8472
      Mar 5 '18 at 20:25








    • 1





      @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

      – Martha Gottsumpf
      Mar 8 '18 at 9:10


















    4














    After hours of struggling, try, error and reading source code.



    Everything works well but you have to specify correctly.
    When using IPv6 LinkLocal addresses you have to specify the interface with the "%" notation AND the prefix length in the end.



    Interfaces = {Full-IPv6-address}%{interface}/{prefix length}


    smb.conf (SAMPLE):



    interfaces = fe80::114%eth0/64





    share|improve this answer


























    • I have tried that, it doesn't work for me. I'll update my question.

      – the8472
      Mar 3 '18 at 19:29











    • "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

      – Martha Gottsumpf
      Mar 4 '18 at 22:48













    • Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

      – the8472
      Mar 5 '18 at 20:25








    • 1





      @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

      – Martha Gottsumpf
      Mar 8 '18 at 9:10
















    4












    4








    4







    After hours of struggling, try, error and reading source code.



    Everything works well but you have to specify correctly.
    When using IPv6 LinkLocal addresses you have to specify the interface with the "%" notation AND the prefix length in the end.



    Interfaces = {Full-IPv6-address}%{interface}/{prefix length}


    smb.conf (SAMPLE):



    interfaces = fe80::114%eth0/64





    share|improve this answer















    After hours of struggling, try, error and reading source code.



    Everything works well but you have to specify correctly.
    When using IPv6 LinkLocal addresses you have to specify the interface with the "%" notation AND the prefix length in the end.



    Interfaces = {Full-IPv6-address}%{interface}/{prefix length}


    smb.conf (SAMPLE):



    interfaces = fe80::114%eth0/64






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 5 '18 at 8:03

























    answered Feb 24 '18 at 21:42









    Martha GottsumpfMartha Gottsumpf

    563




    563













    • I have tried that, it doesn't work for me. I'll update my question.

      – the8472
      Mar 3 '18 at 19:29











    • "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

      – Martha Gottsumpf
      Mar 4 '18 at 22:48













    • Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

      – the8472
      Mar 5 '18 at 20:25








    • 1





      @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

      – Martha Gottsumpf
      Mar 8 '18 at 9:10





















    • I have tried that, it doesn't work for me. I'll update my question.

      – the8472
      Mar 3 '18 at 19:29











    • "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

      – Martha Gottsumpf
      Mar 4 '18 at 22:48













    • Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

      – the8472
      Mar 5 '18 at 20:25








    • 1





      @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

      – Martha Gottsumpf
      Mar 8 '18 at 9:10



















    I have tried that, it doesn't work for me. I'll update my question.

    – the8472
    Mar 3 '18 at 19:29





    I have tried that, it doesn't work for me. I'll update my question.

    – the8472
    Mar 3 '18 at 19:29













    "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

    – Martha Gottsumpf
    Mar 4 '18 at 22:48







    "fe80::%br0/64" will not work --> you have to specify the whole link local address. For example: fe80::d270:36a5:ac03:37ea%br0/64

    – Martha Gottsumpf
    Mar 4 '18 at 22:48















    Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

    – the8472
    Mar 5 '18 at 20:25







    Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? It works for the v4 private addresses at least. But you're right, that works, so I'll accept that answer although I'd have preferred a more generic solution.

    – the8472
    Mar 5 '18 at 20:25






    1




    1





    @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

    – Martha Gottsumpf
    Mar 8 '18 at 9:10







    @the8472 Isn't the point of netmasks in the configuration that you can specify a mask and it will pick any address falling within that mask? I'm with you. I tried the same. Maybe we should ask the Samba team.

    – Martha Gottsumpf
    Mar 8 '18 at 9:10















    0














    The best way to deal with IPv6 is not to use link local adresses but unique local instead.



    Looks like "bind interfaces only" option makes IPv6 link local address not listened even if correctly written in smb.conf



    I've tested successfully the use of IPv6 unique local address on debian linux and windows 10 to exchange files via samba from a linux server to a windows workstation.



    In my configuration, the unique local address have been manualy configured in debian and windows so the SLAAC is still working to provide global IPv6 address. No need to use DHCPv6 to use this type of address.






    share|improve this answer








    New contributor




    wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      The best way to deal with IPv6 is not to use link local adresses but unique local instead.



      Looks like "bind interfaces only" option makes IPv6 link local address not listened even if correctly written in smb.conf



      I've tested successfully the use of IPv6 unique local address on debian linux and windows 10 to exchange files via samba from a linux server to a windows workstation.



      In my configuration, the unique local address have been manualy configured in debian and windows so the SLAAC is still working to provide global IPv6 address. No need to use DHCPv6 to use this type of address.






      share|improve this answer








      New contributor




      wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        The best way to deal with IPv6 is not to use link local adresses but unique local instead.



        Looks like "bind interfaces only" option makes IPv6 link local address not listened even if correctly written in smb.conf



        I've tested successfully the use of IPv6 unique local address on debian linux and windows 10 to exchange files via samba from a linux server to a windows workstation.



        In my configuration, the unique local address have been manualy configured in debian and windows so the SLAAC is still working to provide global IPv6 address. No need to use DHCPv6 to use this type of address.






        share|improve this answer








        New contributor




        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        The best way to deal with IPv6 is not to use link local adresses but unique local instead.



        Looks like "bind interfaces only" option makes IPv6 link local address not listened even if correctly written in smb.conf



        I've tested successfully the use of IPv6 unique local address on debian linux and windows 10 to exchange files via samba from a linux server to a windows workstation.



        In my configuration, the unique local address have been manualy configured in debian and windows so the SLAAC is still working to provide global IPv6 address. No need to use DHCPv6 to use this type of address.







        share|improve this answer








        New contributor




        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 6 hours ago









        wanouwanou

        1




        1




        New contributor




        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        wanou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1029279%2fhow-to-specify-ipv6-link-local-bind-address-in-smb-conf%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Cannot install PyQt5 The Next CEO of Stack OverflowCannot install tcpreplay 3.4.4cannot...

            Kapp-Putsch Acontecimentos | Outros artigos | Menu de navegação

            Why did early computer designers eschew integers? The Next CEO of Stack OverflowWhat register...