Buffering issue when looking at netcat output

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











up vote
0
down vote

favorite












I have problem I am trying to understand:



I am sending some UDP data to local host. It is a simple UDP packet with a counter. It counts up to 16 (0xF) and stops. When I grep the received data on the output, and grep only shows up to packet 11 (0xB) received. All the packets are actually received, but either grep or xxd is buffering. I have sent the data to a file to check if all is received, and the data is coming through.




[testuser %] netcat -l 127.0.0.1 -u -p 8777 | xxd -e -u | grep DEAD




00000000: 00000000 DEADBEEF FFFFFFFF DEADBEEF ................
00000400: 00000001 DEADBEEF FFFFFFFF DEADBEEF ................
00000800: 00000002 DEADBEEF FFFFFFFF DEADBEEF ................
00000c00: 00000003 DEADBEEF FFFFFFFF DEADBEEF ................
00001000: 00000004 DEADBEEF FFFFFFFF DEADBEEF ................
00001400: 00000005 DEADBEEF FFFFFFFF DEADBEEF ................
00001800: 00000006 DEADBEEF FFFFFFFF DEADBEEF ................
00001c00: 00000007 DEADBEEF FFFFFFFF DEADBEEF ................
00002000: 00000008 DEADBEEF FFFFFFFF DEADBEEF ................
00002400: 00000009 DEADBEEF FFFFFFFF DEADBEEF ................
00002800: 0000000A DEADBEEF FFFFFFFF DEADBEEF ................
00002c00: 0000000B DEADBEEF FFFFFFFF DEADBEEF ................


I suspect this is a buffering problem ... I used od (Octal dump) and I could see the full sequence, but I like the xxd output better and would like it to work.










share|improve this question



























    up vote
    0
    down vote

    favorite












    I have problem I am trying to understand:



    I am sending some UDP data to local host. It is a simple UDP packet with a counter. It counts up to 16 (0xF) and stops. When I grep the received data on the output, and grep only shows up to packet 11 (0xB) received. All the packets are actually received, but either grep or xxd is buffering. I have sent the data to a file to check if all is received, and the data is coming through.




    [testuser %] netcat -l 127.0.0.1 -u -p 8777 | xxd -e -u | grep DEAD




    00000000: 00000000 DEADBEEF FFFFFFFF DEADBEEF ................
    00000400: 00000001 DEADBEEF FFFFFFFF DEADBEEF ................
    00000800: 00000002 DEADBEEF FFFFFFFF DEADBEEF ................
    00000c00: 00000003 DEADBEEF FFFFFFFF DEADBEEF ................
    00001000: 00000004 DEADBEEF FFFFFFFF DEADBEEF ................
    00001400: 00000005 DEADBEEF FFFFFFFF DEADBEEF ................
    00001800: 00000006 DEADBEEF FFFFFFFF DEADBEEF ................
    00001c00: 00000007 DEADBEEF FFFFFFFF DEADBEEF ................
    00002000: 00000008 DEADBEEF FFFFFFFF DEADBEEF ................
    00002400: 00000009 DEADBEEF FFFFFFFF DEADBEEF ................
    00002800: 0000000A DEADBEEF FFFFFFFF DEADBEEF ................
    00002c00: 0000000B DEADBEEF FFFFFFFF DEADBEEF ................


    I suspect this is a buffering problem ... I used od (Octal dump) and I could see the full sequence, but I like the xxd output better and would like it to work.










    share|improve this question

























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have problem I am trying to understand:



      I am sending some UDP data to local host. It is a simple UDP packet with a counter. It counts up to 16 (0xF) and stops. When I grep the received data on the output, and grep only shows up to packet 11 (0xB) received. All the packets are actually received, but either grep or xxd is buffering. I have sent the data to a file to check if all is received, and the data is coming through.




      [testuser %] netcat -l 127.0.0.1 -u -p 8777 | xxd -e -u | grep DEAD




      00000000: 00000000 DEADBEEF FFFFFFFF DEADBEEF ................
      00000400: 00000001 DEADBEEF FFFFFFFF DEADBEEF ................
      00000800: 00000002 DEADBEEF FFFFFFFF DEADBEEF ................
      00000c00: 00000003 DEADBEEF FFFFFFFF DEADBEEF ................
      00001000: 00000004 DEADBEEF FFFFFFFF DEADBEEF ................
      00001400: 00000005 DEADBEEF FFFFFFFF DEADBEEF ................
      00001800: 00000006 DEADBEEF FFFFFFFF DEADBEEF ................
      00001c00: 00000007 DEADBEEF FFFFFFFF DEADBEEF ................
      00002000: 00000008 DEADBEEF FFFFFFFF DEADBEEF ................
      00002400: 00000009 DEADBEEF FFFFFFFF DEADBEEF ................
      00002800: 0000000A DEADBEEF FFFFFFFF DEADBEEF ................
      00002c00: 0000000B DEADBEEF FFFFFFFF DEADBEEF ................


      I suspect this is a buffering problem ... I used od (Octal dump) and I could see the full sequence, but I like the xxd output better and would like it to work.










      share|improve this question















      I have problem I am trying to understand:



      I am sending some UDP data to local host. It is a simple UDP packet with a counter. It counts up to 16 (0xF) and stops. When I grep the received data on the output, and grep only shows up to packet 11 (0xB) received. All the packets are actually received, but either grep or xxd is buffering. I have sent the data to a file to check if all is received, and the data is coming through.




      [testuser %] netcat -l 127.0.0.1 -u -p 8777 | xxd -e -u | grep DEAD




      00000000: 00000000 DEADBEEF FFFFFFFF DEADBEEF ................
      00000400: 00000001 DEADBEEF FFFFFFFF DEADBEEF ................
      00000800: 00000002 DEADBEEF FFFFFFFF DEADBEEF ................
      00000c00: 00000003 DEADBEEF FFFFFFFF DEADBEEF ................
      00001000: 00000004 DEADBEEF FFFFFFFF DEADBEEF ................
      00001400: 00000005 DEADBEEF FFFFFFFF DEADBEEF ................
      00001800: 00000006 DEADBEEF FFFFFFFF DEADBEEF ................
      00001c00: 00000007 DEADBEEF FFFFFFFF DEADBEEF ................
      00002000: 00000008 DEADBEEF FFFFFFFF DEADBEEF ................
      00002400: 00000009 DEADBEEF FFFFFFFF DEADBEEF ................
      00002800: 0000000A DEADBEEF FFFFFFFF DEADBEEF ................
      00002c00: 0000000B DEADBEEF FFFFFFFF DEADBEEF ................


      I suspect this is a buffering problem ... I used od (Octal dump) and I could see the full sequence, but I like the xxd output better and would like it to work.







      grep pipe netcat buffer xxd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 8 at 3:49









      Jeff Schaller

      38k1053123




      38k1053123










      asked Dec 8 at 3:21









      Xofo

      2331313




      2331313

























          active

          oldest

          votes











          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',
          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%2f486709%2fbuffering-issue-when-looking-at-netcat-output%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          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.





          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%2funix.stackexchange.com%2fquestions%2f486709%2fbuffering-issue-when-looking-at-netcat-output%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?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?