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?






ubuntu ipv6 localhost







share|improve this question
























  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    Nov 17 at 18:55












  • superuser.com/questions/1005335/…
    – harrymc
    Nov 17 at 19:26










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    Nov 17 at 23:08















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?






ubuntu ipv6 localhost







share|improve this question
























  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    Nov 17 at 18:55












  • superuser.com/questions/1005335/…
    – harrymc
    Nov 17 at 19:26










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    Nov 17 at 23:08













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?






ubuntu ipv6 localhost







share|improve this question















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




ubuntu ipv6 localhost






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 18 at 0:32









Peter Mortensen

8,301166184




8,301166184










asked Nov 17 at 18:50









jws

1956




1956












  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    Nov 17 at 18:55












  • superuser.com/questions/1005335/…
    – harrymc
    Nov 17 at 19:26










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    Nov 17 at 23:08


















  • Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
    – jws
    Nov 17 at 18:55












  • superuser.com/questions/1005335/…
    – harrymc
    Nov 17 at 19:26










  • FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
    – Bakuriu
    Nov 17 at 23:08
















Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55






Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55














superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26




superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26












FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
– Bakuriu
Nov 17 at 23:08




FYI: ifconfig is deprecated. You want to use ip address or ip a instead.
– Bakuriu
Nov 17 at 23:08










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



















  • 1




    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    Nov 18 at 0:33








  • 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
    Nov 18 at 0:42










  • @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
    Nov 18 at 9:31


















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


    }
    });














    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



















    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      Nov 18 at 0:33








    • 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
      Nov 18 at 0:42










    • @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
      Nov 18 at 9:31















    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



















    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      Nov 18 at 0:33








    • 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
      Nov 18 at 0:42










    • @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
      Nov 18 at 9:31













    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














    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














    share|improve this answer



    share|improve this answer








    edited Nov 17 at 21:31

























    answered Nov 17 at 19:24









    jws

    1956




    1956








    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      Nov 18 at 0:33








    • 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
      Nov 18 at 0:42










    • @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
      Nov 18 at 9:31














    • 1




      Is that an answer or a follow-up? This site is not a forum. It is a think tank.
      – Peter Mortensen
      Nov 18 at 0:33








    • 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
      Nov 18 at 0:42










    • @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
      Nov 18 at 9:31








    1




    1




    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    Nov 18 at 0:33






    Is that an answer or a follow-up? This site is not a forum. It is a think tank.
    – Peter Mortensen
    Nov 18 at 0:33






    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
    Nov 18 at 0:42




    @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
    Nov 18 at 0:42












    @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
    Nov 18 at 9:31




    @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
    Nov 18 at 9:31












    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 Nov 18 at 1:43









        Twisty Impersonator

        17.2k126293




        17.2k126293










        answered Nov 17 at 19:33









        Ron Maupin

        3,04011021




        3,04011021






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%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

            AnyDesk - Fatal Program Failure

            Image
            up vote 0 down vote favorite Good day all. I have a window that pops up saying Fatal Program Failure (AnyDesk). This is what I have done so far: Uninstalled AnyDesk and reinstalled it. ( The window still appeared ) I disabled AnyDesk start up in Msconfig and the window seems to have disapeared. Lastly I made sure that AnyDesk worked by remoting into it, and it worked. Today the same window appeared. How do I get rid of this window? remote-desktop share | improve this question edited 10 hours ago Tomasz Jakub Rup 552 3 13 ...
            Read more

            How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

            Image
            up vote 0 down vote favorite I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7. The problem consists of a number of factors, please find the details below: The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format. The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen. The employees using this solution is not supposed to see nor have access to anything but the POS application. Our sales organization demands that touch is an available feature when going live with the new POS environment. Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen: We've simply change...
            Read more

            QoS: MAC-Priority for clients behind a repeater

            Image
            1 1 I've setup a wireless network using a Linksys-Router (DD-WRT) as an AP and a TP-Link repeater for range extension. To manage bandwith for specific users, I've setup QoS-Rules on the AP (DD-WRT) using MAC-Priority: However the AP shows only the Repeater's MAC and the MACs of users inside the AP-Range. The MAC addresses of users behind the Repeater are not listed : The purple MAC is not listed in the AP-Clientlist. Its related to a device connected via the TP-Link repeater. Q: How can I setup MAC-Priority for repeater-clients? Do I simply add the purple MAC in AP-MAC priority list although it's not listed as a client? I want to setup specific priority instead of giving one priority for all clients behind the repeater by adding the repeater's MAC in the MAC priority list in the AP as ...
            Read more