Ubuntu IPv6 ping self gives unknown host











up vote
3
down vote

favorite
1












I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.



$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link


and



$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64


results in



unknown host


How do I troubleshoot?










share|improve this question









New contributor




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




















  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    2 days ago












  • superuser.com/questions/1005335/…
    – harrymc
    2 days ago










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    2 days ago















up vote
3
down vote

favorite
1












I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.



$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link


and



$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64


results in



unknown host


How do I troubleshoot?










share|improve this question









New contributor




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




















  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    2 days ago












  • superuser.com/questions/1005335/…
    – harrymc
    2 days ago










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    2 days ago













up vote
3
down vote

favorite
1









up vote
3
down vote

favorite
1






1





I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.



$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link


and



$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64


results in



unknown host


How do I troubleshoot?










share|improve this question









New contributor




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











I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.



$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link


and



$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64


results in



unknown host


How do I troubleshoot?







ubuntu ipv6 localhost






share|improve this question









New contributor




jws 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 question









New contributor




jws 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 question




share|improve this question








edited 2 days ago









Peter Mortensen

8,301166184




8,301166184






New contributor




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









asked 2 days ago









jws

1956




1956




New contributor




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





New contributor





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






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












  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    2 days ago












  • superuser.com/questions/1005335/…
    – harrymc
    2 days ago










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    2 days ago


















  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    2 days ago












  • superuser.com/questions/1005335/…
    – harrymc
    2 days ago










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    2 days ago
















Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
2 days ago






Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
2 days ago














superuser.com/questions/1005335/…
– harrymc
2 days ago




superuser.com/questions/1005335/…
– harrymc
2 days ago












FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
– Bakuriu
2 days ago




FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
– Bakuriu
2 days ago










2 Answers
2






active

oldest

votes

















up vote
8
down vote













Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.



$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms


The local interface argument -I can be specified in the address instead by appending % and the interface name:



$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...


These combinations don't work:



$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host


or



$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument





share|improve this answer










New contributor




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














  • 1




    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    2 days ago








  • 1




    @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
    – eckes
    2 days ago










  • @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
    – kasperd
    yesterday


















up vote
8
down vote













You should not use the /64 on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.






share|improve this answer























    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',
    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
    });


    }
    });






    jws is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376287%2fubuntu-ipv6-ping-self-gives-unknown-host%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








    up vote
    8
    down vote













    Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
    PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms


    The local interface argument -I can be specified in the address instead by appending % and the interface name:



    $ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
    PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
    ...


    These combinations don't work:



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
    unknown host


    or



    $ ping6 fe80::ba94:3d5e:9929:4c6e
    connect: Invalid argument





    share|improve this answer










    New contributor




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














    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      2 days ago








    • 1




      @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
      – eckes
      2 days ago










    • @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
      – kasperd
      yesterday















    up vote
    8
    down vote













    Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
    PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms


    The local interface argument -I can be specified in the address instead by appending % and the interface name:



    $ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
    PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
    ...


    These combinations don't work:



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
    unknown host


    or



    $ ping6 fe80::ba94:3d5e:9929:4c6e
    connect: Invalid argument





    share|improve this answer










    New contributor




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














    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      2 days ago








    • 1




      @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
      – eckes
      2 days ago










    • @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
      – kasperd
      yesterday













    up vote
    8
    down vote










    up vote
    8
    down vote









    Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
    PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms


    The local interface argument -I can be specified in the address instead by appending % and the interface name:



    $ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
    PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
    ...


    These combinations don't work:



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
    unknown host


    or



    $ ping6 fe80::ba94:3d5e:9929:4c6e
    connect: Invalid argument





    share|improve this answer










    New contributor




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









    Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
    PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms


    The local interface argument -I can be specified in the address instead by appending % and the interface name:



    $ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
    PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
    64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
    ...


    These combinations don't work:



    $ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
    unknown host


    or



    $ ping6 fe80::ba94:3d5e:9929:4c6e
    connect: Invalid argument






    share|improve this answer










    New contributor




    jws 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








    edited 2 days ago





















    New contributor




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









    answered 2 days ago









    jws

    1956




    1956




    New contributor




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





    New contributor





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






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








    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      2 days ago








    • 1




      @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
      – eckes
      2 days ago










    • @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
      – kasperd
      yesterday














    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      2 days ago








    • 1




      @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
      – eckes
      2 days ago










    • @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
      – kasperd
      yesterday








    1




    1




    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    2 days ago






    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    2 days ago






    1




    1




    @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
    – eckes
    2 days ago




    @PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
    – eckes
    2 days ago












    @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
    – kasperd
    yesterday




    @PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
    – kasperd
    yesterday












    up vote
    8
    down vote













    You should not use the /64 on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.






    share|improve this answer



























      up vote
      8
      down vote













      You should not use the /64 on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.






      share|improve this answer

























        up vote
        8
        down vote










        up vote
        8
        down vote









        You should not use the /64 on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.






        share|improve this answer














        You should not use the /64 on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 2 days ago









        Twisty Impersonator

        16.6k126090




        16.6k126090










        answered 2 days ago









        Ron Maupin

        3,01511020




        3,01511020






















            jws is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            jws is a new contributor. Be nice, and check out our Code of Conduct.













            jws is a new contributor. Be nice, and check out our Code of Conduct.












            jws is a new contributor. Be nice, and check out our Code of Conduct.















             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376287%2fubuntu-ipv6-ping-self-gives-unknown-host%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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕