Where is the official documentation (Debian package iproute-doc)?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












-1















Manpage of ss says:




FILTER := [ state TCP-STATE ] [ EXPRESSION ]


Please take a look at the official documentation (Debian package iproute-doc) for details regarding filters.




What does that mean? I can't find anything under /usr/share/doc/iproute2-doc/.



$ ls /usr/share/doc/iproute2-doc/ss.html
ls: cannot access '/usr/share/doc/iproute2-doc/ss.html': No such file or directory

$ ls /usr/share/doc/iproute2-doc/
actions changelog.Debian.gz copyright examples README README.decnet README.devel README.distribution.gz README.iproute2+tc README.lnstat


Is the document also online somewhere for browsing?



Thanks.










share|improve this question



















  • 2





    Do you have the corresponding package installed?

    – Jeff Schaller
    Feb 7 at 0:31






  • 1





    if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

    – Tim
    Feb 7 at 0:46











  • I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

    – steeldriver
    Feb 7 at 1:06
















-1















Manpage of ss says:




FILTER := [ state TCP-STATE ] [ EXPRESSION ]


Please take a look at the official documentation (Debian package iproute-doc) for details regarding filters.




What does that mean? I can't find anything under /usr/share/doc/iproute2-doc/.



$ ls /usr/share/doc/iproute2-doc/ss.html
ls: cannot access '/usr/share/doc/iproute2-doc/ss.html': No such file or directory

$ ls /usr/share/doc/iproute2-doc/
actions changelog.Debian.gz copyright examples README README.decnet README.devel README.distribution.gz README.iproute2+tc README.lnstat


Is the document also online somewhere for browsing?



Thanks.










share|improve this question



















  • 2





    Do you have the corresponding package installed?

    – Jeff Schaller
    Feb 7 at 0:31






  • 1





    if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

    – Tim
    Feb 7 at 0:46











  • I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

    – steeldriver
    Feb 7 at 1:06














-1












-1








-1








Manpage of ss says:




FILTER := [ state TCP-STATE ] [ EXPRESSION ]


Please take a look at the official documentation (Debian package iproute-doc) for details regarding filters.




What does that mean? I can't find anything under /usr/share/doc/iproute2-doc/.



$ ls /usr/share/doc/iproute2-doc/ss.html
ls: cannot access '/usr/share/doc/iproute2-doc/ss.html': No such file or directory

$ ls /usr/share/doc/iproute2-doc/
actions changelog.Debian.gz copyright examples README README.decnet README.devel README.distribution.gz README.iproute2+tc README.lnstat


Is the document also online somewhere for browsing?



Thanks.










share|improve this question
















Manpage of ss says:




FILTER := [ state TCP-STATE ] [ EXPRESSION ]


Please take a look at the official documentation (Debian package iproute-doc) for details regarding filters.




What does that mean? I can't find anything under /usr/share/doc/iproute2-doc/.



$ ls /usr/share/doc/iproute2-doc/ss.html
ls: cannot access '/usr/share/doc/iproute2-doc/ss.html': No such file or directory

$ ls /usr/share/doc/iproute2-doc/
actions changelog.Debian.gz copyright examples README README.decnet README.devel README.distribution.gz README.iproute2+tc README.lnstat


Is the document also online somewhere for browsing?



Thanks.







debian documentation iproute






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 7 at 11:06









GAD3R

26.9k1756111




26.9k1756111










asked Feb 7 at 0:27









TimTim

27.4k78264474




27.4k78264474







  • 2





    Do you have the corresponding package installed?

    – Jeff Schaller
    Feb 7 at 0:31






  • 1





    if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

    – Tim
    Feb 7 at 0:46











  • I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

    – steeldriver
    Feb 7 at 1:06













  • 2





    Do you have the corresponding package installed?

    – Jeff Schaller
    Feb 7 at 0:31






  • 1





    if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

    – Tim
    Feb 7 at 0:46











  • I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

    – steeldriver
    Feb 7 at 1:06








2




2





Do you have the corresponding package installed?

– Jeff Schaller
Feb 7 at 0:31





Do you have the corresponding package installed?

– Jeff Schaller
Feb 7 at 0:31




1




1





if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

– Tim
Feb 7 at 0:46





if I haven't run sudo apt install iproute2-doc, would I have /usr/share/doc/iproute2-doc/?

– Tim
Feb 7 at 0:46













I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

– steeldriver
Feb 7 at 1:06






I notice that whereas man ss on my Ubuntu 16.04 box refers to "Debian package iproute-doc", that on 18.04 refers only to "the official documentation" - so I suspect the relevant documentation has been moved elsewhere

– steeldriver
Feb 7 at 1:06











2 Answers
2






active

oldest

votes


















2














The documentation is available in the Debian 9 package but was removed in later releases because it was outdated. The manpage is supposed to be the complete documentation now. (But it doesn’t have much to say about the details of filters.)






share|improve this answer























  • Thanks. Where can I learn about it?

    – Tim
    Feb 7 at 11:30






  • 1





    I get the impression the only remaining “documentation” is the Bison parser code.

    – Stephen Kitt
    Feb 7 at 15:02











  • Does that link use regex parser to parse command line arguments?

    – Tim
    Feb 7 at 15:08











  • No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

    – Stephen Kitt
    Feb 7 at 15:11











  • I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

    – Tim
    Feb 7 at 21:15


















1














 FILTER := [ state STATE-FILTER ] [ EXPRESSION ]
Please take a look at the official documentation for details regarding filters.

STATE-FILTER
STATE-FILTER allows to construct arbitrary set of states to match. Its syntax is sequence of keywords state and exclude fol‐
lowed by identifier of state.

Available identifiers are:

All standard TCP states: established, syn-sent, syn-recv, fin-wait-1, fin-wait-2, time-wait, closed, close-wait, last-
ack, listening and closing.

all - for all the states

connected - all the states except for listening and closed

synchronized - all the connected states except for syn-sent

bucket - states, which are maintained as minisockets, i.e. time-wait and syn-recv

big - opposite to bucket





share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f499190%2fwhere-is-the-official-documentation-debian-package-iproute-doc%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









    2














    The documentation is available in the Debian 9 package but was removed in later releases because it was outdated. The manpage is supposed to be the complete documentation now. (But it doesn’t have much to say about the details of filters.)






    share|improve this answer























    • Thanks. Where can I learn about it?

      – Tim
      Feb 7 at 11:30






    • 1





      I get the impression the only remaining “documentation” is the Bison parser code.

      – Stephen Kitt
      Feb 7 at 15:02











    • Does that link use regex parser to parse command line arguments?

      – Tim
      Feb 7 at 15:08











    • No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

      – Stephen Kitt
      Feb 7 at 15:11











    • I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

      – Tim
      Feb 7 at 21:15















    2














    The documentation is available in the Debian 9 package but was removed in later releases because it was outdated. The manpage is supposed to be the complete documentation now. (But it doesn’t have much to say about the details of filters.)






    share|improve this answer























    • Thanks. Where can I learn about it?

      – Tim
      Feb 7 at 11:30






    • 1





      I get the impression the only remaining “documentation” is the Bison parser code.

      – Stephen Kitt
      Feb 7 at 15:02











    • Does that link use regex parser to parse command line arguments?

      – Tim
      Feb 7 at 15:08











    • No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

      – Stephen Kitt
      Feb 7 at 15:11











    • I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

      – Tim
      Feb 7 at 21:15













    2












    2








    2







    The documentation is available in the Debian 9 package but was removed in later releases because it was outdated. The manpage is supposed to be the complete documentation now. (But it doesn’t have much to say about the details of filters.)






    share|improve this answer













    The documentation is available in the Debian 9 package but was removed in later releases because it was outdated. The manpage is supposed to be the complete documentation now. (But it doesn’t have much to say about the details of filters.)







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 7 at 6:24









    Stephen KittStephen Kitt

    174k24398473




    174k24398473












    • Thanks. Where can I learn about it?

      – Tim
      Feb 7 at 11:30






    • 1





      I get the impression the only remaining “documentation” is the Bison parser code.

      – Stephen Kitt
      Feb 7 at 15:02











    • Does that link use regex parser to parse command line arguments?

      – Tim
      Feb 7 at 15:08











    • No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

      – Stephen Kitt
      Feb 7 at 15:11











    • I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

      – Tim
      Feb 7 at 21:15

















    • Thanks. Where can I learn about it?

      – Tim
      Feb 7 at 11:30






    • 1





      I get the impression the only remaining “documentation” is the Bison parser code.

      – Stephen Kitt
      Feb 7 at 15:02











    • Does that link use regex parser to parse command line arguments?

      – Tim
      Feb 7 at 15:08











    • No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

      – Stephen Kitt
      Feb 7 at 15:11











    • I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

      – Tim
      Feb 7 at 21:15
















    Thanks. Where can I learn about it?

    – Tim
    Feb 7 at 11:30





    Thanks. Where can I learn about it?

    – Tim
    Feb 7 at 11:30




    1




    1





    I get the impression the only remaining “documentation” is the Bison parser code.

    – Stephen Kitt
    Feb 7 at 15:02





    I get the impression the only remaining “documentation” is the Bison parser code.

    – Stephen Kitt
    Feb 7 at 15:02













    Does that link use regex parser to parse command line arguments?

    – Tim
    Feb 7 at 15:08





    Does that link use regex parser to parse command line arguments?

    – Tim
    Feb 7 at 15:08













    No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

    – Stephen Kitt
    Feb 7 at 15:11





    No, it’s a Yacc parser description, and the build uses Bison to build a real parser for it.

    – Stephen Kitt
    Feb 7 at 15:11













    I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

    – Tim
    Feb 7 at 21:15





    I only know the getopts or getopt library to parse command line options. when to use Bison/Yacc and when to use getopts or getopt?

    – Tim
    Feb 7 at 21:15













    1














     FILTER := [ state STATE-FILTER ] [ EXPRESSION ]
    Please take a look at the official documentation for details regarding filters.

    STATE-FILTER
    STATE-FILTER allows to construct arbitrary set of states to match. Its syntax is sequence of keywords state and exclude fol‐
    lowed by identifier of state.

    Available identifiers are:

    All standard TCP states: established, syn-sent, syn-recv, fin-wait-1, fin-wait-2, time-wait, closed, close-wait, last-
    ack, listening and closing.

    all - for all the states

    connected - all the states except for listening and closed

    synchronized - all the connected states except for syn-sent

    bucket - states, which are maintained as minisockets, i.e. time-wait and syn-recv

    big - opposite to bucket





    share|improve this answer



























      1














       FILTER := [ state STATE-FILTER ] [ EXPRESSION ]
      Please take a look at the official documentation for details regarding filters.

      STATE-FILTER
      STATE-FILTER allows to construct arbitrary set of states to match. Its syntax is sequence of keywords state and exclude fol‐
      lowed by identifier of state.

      Available identifiers are:

      All standard TCP states: established, syn-sent, syn-recv, fin-wait-1, fin-wait-2, time-wait, closed, close-wait, last-
      ack, listening and closing.

      all - for all the states

      connected - all the states except for listening and closed

      synchronized - all the connected states except for syn-sent

      bucket - states, which are maintained as minisockets, i.e. time-wait and syn-recv

      big - opposite to bucket





      share|improve this answer

























        1












        1








        1







         FILTER := [ state STATE-FILTER ] [ EXPRESSION ]
        Please take a look at the official documentation for details regarding filters.

        STATE-FILTER
        STATE-FILTER allows to construct arbitrary set of states to match. Its syntax is sequence of keywords state and exclude fol‐
        lowed by identifier of state.

        Available identifiers are:

        All standard TCP states: established, syn-sent, syn-recv, fin-wait-1, fin-wait-2, time-wait, closed, close-wait, last-
        ack, listening and closing.

        all - for all the states

        connected - all the states except for listening and closed

        synchronized - all the connected states except for syn-sent

        bucket - states, which are maintained as minisockets, i.e. time-wait and syn-recv

        big - opposite to bucket





        share|improve this answer













         FILTER := [ state STATE-FILTER ] [ EXPRESSION ]
        Please take a look at the official documentation for details regarding filters.

        STATE-FILTER
        STATE-FILTER allows to construct arbitrary set of states to match. Its syntax is sequence of keywords state and exclude fol‐
        lowed by identifier of state.

        Available identifiers are:

        All standard TCP states: established, syn-sent, syn-recv, fin-wait-1, fin-wait-2, time-wait, closed, close-wait, last-
        ack, listening and closing.

        all - for all the states

        connected - all the states except for listening and closed

        synchronized - all the connected states except for syn-sent

        bucket - states, which are maintained as minisockets, i.e. time-wait and syn-recv

        big - opposite to bucket






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 7 at 3:22









        user1133275user1133275

        3,517723




        3,517723



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f499190%2fwhere-is-the-official-documentation-debian-package-iproute-doc%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

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay